Date: Fri, 22 Feb 2019 08:01:08 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: =?utf-8?Q?T=C4=B3l?= Coosemans <tijl@freebsd.org> Cc: Diane Bruce <db@db.net>, "Russell L. Carter" <rcarter@pinyon.org>, Eugene Grosbein <eugen@grosbein.net>, FreeBSD Ports ML <freebsd-ports@freebsd.org> Subject: Re: FreeCAD 0.17 && /lib//libgcc_s.so.1 Message-ID: <20190222160108.GB32886@troutmask.apl.washington.edu> In-Reply-To: <20190222122841.6d48b473@kalimero.tijl.coosemans.org> References: <a2102b4e-7d7a-7d5b-2ba1-b9a14f8574f6@pinyon.org> <f6a45ec9-7ae4-d9ba-f71c-f2ef8c235039@grosbein.net> <416689e6-37f9-17ec-54d8-0d224c26f30f@pinyon.org> <20190217151604.GB68620@night.db.net> <20190221180515.39c79ce6@kalimero.tijl.coosemans.org> <20190221183040.GA42303@night.db.net> <20190221231850.46dd5374@kalimero.tijl.coosemans.org> <20190222001315.GA24225@troutmask.apl.washington.edu> <20190222122841.6d48b473@kalimero.tijl.coosemans.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Feb 22, 2019 at 12:28:41PM +0100, Tijl Coosemans wrote: > > PS: For the record, the GCC_4.6.0 are needed for gfortran REAL(16) > > type. > > With my patch gfortran resolves the GCC_4.6.0 symbols statically just > like the C compilers do. If the C compilers didn't do this we'd have > this libgcc_s problem all over the place. It makes perfect sense to > make gfortran do the same thing. I'm fine with your patch. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190222160108.GB32886>