Date: Mon, 22 Aug 2016 08:26:04 +0200 From: Matthias Andree <matthias.andree@gmx.de> To: freebsd-ports@freebsd.org Subject: Re: Problems with out libgcc_s.so in base Message-ID: <6f6a2c65-216a-3d7e-825f-222a06428f60@gmx.de> In-Reply-To: <AB844E50-01A9-4559-8F7A-FE1F7B768F3A@FreeBSD.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --udHTT4bCE2lR8EP2Lqo3w3N1CocJXIKr3 Content-Type: multipart/mixed; boundary="wELlwcB9Xfn7ugGNV4QD8MPFsTfP4vlff" From: Matthias Andree <matthias.andree@gmx.de> To: freebsd-ports@freebsd.org Message-ID: <6f6a2c65-216a-3d7e-825f-222a06428f60@gmx.de> Subject: Re: Problems with out libgcc_s.so in base 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> In-Reply-To: <AB844E50-01A9-4559-8F7A-FE1F7B768F3A@FreeBSD.org> --wELlwcB9Xfn7ugGNV4QD8MPFsTfP4vlff Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Am 18.08.2016 um 14:48 schrieb Dimitry Andric: > For example, on one of my systems, I now have these: > > /usr/local/lib/gcc47/libgcc_s.so.1 > /usr/local/lib/gcc48/libgcc_s.so.1 > /usr/local/lib/gcc49/libgcc_s.so.1 > /usr/local/lib/gcc5/libgcc_s.so.1 > /usr/local/lib/gcc6/libgcc_s.so.1 > /usr/local/lib/gcc7/libgcc_s.so.1 This in itself - to me - seems to be the actual problem, how do different versions of the library the same major version? If these were, say: /usr/local/lib/gcc47/libgcc_s.so.2 /usr/local/lib/gcc48/libgcc_s.so.3 /usr/local/lib/gcc49/libgcc_s.so.4 /usr/local/lib/gcc5/libgcc_s.so.5 /usr/local/lib/gcc6/libgcc_s.so.6 /usr/local/lib/gcc7/libgcc_s.so.7 Or possibly the compatible ones folded into 2.0, 2.1, 2.2, 3.0 ... and our linker be taught that it can always grab a newer minor version, but not a different major version component, then that would also help because you then match the proper libgcc_s. Does libgcc_s version symbols when semantics change over releases? The counter-argument will be that it will be much harder to use indirectly linked libgcc_s (say, project A needs lib B and lib C, lib B depends on older libgcc_s than lib C) - but as I understood from past discussions (around libssl.so.X in that case) that causes crashes at run-time if the libraries aren't compatible, so this argument is invalid.= > Steve's proposed scheme solves that quite nicely, in my opinion. The > problem is only in the details, as usual. There will be many configure= > scripts and libtool-like utilities out there, that assume libgcc must b= e > linked using -lgcc_s, not -lgcc_s$VERSION. Which can be solved with proper -L options and does not incur renaming libraries. --wELlwcB9Xfn7ugGNV4QD8MPFsTfP4vlff-- --udHTT4bCE2lR8EP2Lqo3w3N1CocJXIKr3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJXupsBAAoJEOQSsVbv84VaI8wQAIinV90ttEEdHGKdgrBnq6DQ Fp+FNWLr5CpFqyzp3ZL4wxdySd20c9DA3WewEN69zwBBqUAmQ83g07g/5gI1NpUh IioVV/JAys6VNOUZSmWyzcBcMNCtAZ01dd0W0EAYFMRdyJoNzfh72PlyDT4TWBOm t5INCTXMjT9cOc11s2V2XOyx7uojL9l5I7MTBHmro7QT5we2RFTQavwPNR0Po6Yo lmRzuzvZ96MMMphnpOPNB5PcKBLCEQI2Ga6GJFavZz2JP+6zH1CHahQeVX11PoiD RfBKQakgoTYsdgq9572oOMqyImOseUfYh9rR7fx8yLG7hyHzaGbLwEAOyw8j4e0k pll8nIRsiGFXUV46xdR52kp1+j6Do327iLjpks02sVa672Ydswsql784EAqjvGda eLSwvM6wmmROWCvwlLJUfggZ/Ppdyb7U0XIlkgLUNP8IdhJpwc0fhlDdE6X313TE RVNALtr4hsl/631JOHbXW1/g0XBuSulocSZovgcr0NGR1L3JOEvNCPIEBmbkFNmF uUI6luh9fX/lwiJpQgfW9MV7sPSp5TNnFY9/rgbFc3a8VI9nHHFA6AD2AnAXYqoL biU1aPQCcZEXGhqITQsukNV0sjcZ8Ajrfr9SUfs8otmOmbT7c/Whni3I1rj4DvoV vngZU4p9qOskC08K2gS7 =X3/U -----END PGP SIGNATURE----- --udHTT4bCE2lR8EP2Lqo3w3N1CocJXIKr3--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6f6a2c65-216a-3d7e-825f-222a06428f60>