Date: Sat, 20 Aug 2016 08:00:56 -0400 From: Diane Bruce <db@db.net> To: Shane Ambler <FreeBSD@ShaneWare.Biz> Cc: freebsd-ports@freebsd.org Subject: Re: Problems with out libgcc_s.so in base Message-ID: <20160820120056.GA1475@night.db.net> In-Reply-To: <9663a390-080e-462d-84d7-2a27987b83e5@ShaneWare.Biz> References: <20160814230351.GA10587@troutmask.apl.washington.edu> <20160814233430.GA35872@night.db.net> <20160817211710.GA59205@troutmask.apl.washington.edu> <20160818111521.7f79b9f8@kalimero.tijl.coosemans.org> <AB844E50-01A9-4559-8F7A-FE1F7B768F3A@FreeBSD.org> <20160819011432.6f2eadbd@kalimero.tijl.coosemans.org> <20160819004304.GA94021@troutmask.apl.washington.edu> <9663a390-080e-462d-84d7-2a27987b83e5@ShaneWare.Biz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Aug 20, 2016 at 03:04:44PM +0930, Shane Ambler wrote: > On 19/08/2016 10:13, Steven G. Kargl wrote: ... > You should find that all newer copies of libgcc_s contain compatibility > support for binaries that were linked to earlier versions. > Indeed. And the version masquerading as a GNU libgcc_s in base does the same thing. Two problems: our base libgcc_s only covers version up to GCC_4.2.0 and there is a name conflict on the library name with libgcc_s from the gnu compiler. Hence if a program links against base libgcc_s first then requires libgfortran which itself requires support for above GCC_4.2.0, the program fails. OR Whenever a program requires support that is missing on the platform it is running on from our libgcc_s, it will fail. There are numerous PR's on this which all have the common problem of linking with a libgcc_s that does not support > GCC_4.2.0 Diane -- - db@FreeBSD.org db@db.net http://www.db.net/~db
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160820120056.GA1475>