From: "Rick \"Zero_Chaos\" Farina" <zerochaos@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] libtool lt_dlopenext vs. gen_ld_script: breakages at runtime
Date: Wed, 08 Jan 2014 15:43:06 -0500 [thread overview]
Message-ID: <52CDB85A.6030906@gentoo.org> (raw)
In-Reply-To: <robbat2-20140108T202349-264675106Z@orbis-terrarum.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/08/2014 03:27 PM, Robin H. Johnson wrote:
> On Wed, Jan 08, 2014 at 09:14:43PM +0100, Peter Stuge wrote:
>> Robin H. Johnson wrote:
>>> Comments:
>>> ---------
>>> In bug #4411, comment 43, vapier noted:
>>>> any package that does dlopen("libfoo.so") without the version info like ".so.X" is broken.
>>> In this case, the lt_dlopenext consumer is explicitly testing multiple
>>> versions of libusb at runtime, and picking the correct interface:
>>> it doesn't need to depend on a specific version.
>> vapier is still correct and the consumer is indeed broken, it does
>> too need to specify the .so version in the dlopen() call, at least
>> in the case of libusb.
>>> This is also because the lt_dlopenext interface does NOT accepted
>>> files versioned after the .so: it needs the filename with no extensions.
>> Hm, that seems limited?
> It's NOT calling dlopen directly. It's calling the lt_dlopenext
> interface from libtool. That iterates over the possible combinations
> that end with ".so", and never iterates over the numbered suffixes.
>
> lt_dlforeachfile actully complicates it even more, but also doesn't see
> the numbered suffixes.
>
> So should you're saying that we need to change libtool's code now?
>
Or we could just stop randomly moving libs across the system and
breaking things then hackmeating things back to a "working" state with
gen_ld_script.
The whole reason for having gen_ld_script is because people wanted
dynamic libs in / and static libs in /usr (which seems insane) and it
broke everything (because that idea is insane). Maybe we could just
install all the libs together (either / or /usr) and stop pretending
that what we are doing isn't wrong?
Just my 0.02$
- -Zero
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJSzbhaAAoJEKXdFCfdEflKsJ4QAIhT02bWH1FxtZG5ALMQcEmr
tnj9YeulX5zp7NCaX+k4MfUn/VgSCAlcjPcWhJW2D2nYIhAFs8uUUb75jhgaFiOr
CIE5PamUE4FeE5NJ3tp2W2T+OXECmo0D0FUBg1ceDBadXDHncwjHS7Go3jTKdcsP
BgVTda3kigoN2BTfj4Gd8WBL2qFMFbRSQlZ9RcmiWTKCNTRvp2bMovgCMpOSgTwg
wIozmzaBTcYJH3TVC2p+Vkf0EZI00nMHAsLVyI/hbT97YVAxZWJG7N5UayK6IxBs
zUxREifT8ZEDXliWuJLBIa6S6HiujViZeKty/1axuMPonM7oEBXeGKS6dT1IJz3J
Hq1HEdccu66rfY1q8BakbKoR4SH2jeQhjP3Uaf/1NXb0sTRRqd7M9rnoTgmMMTfk
HQw8iUWgrHoEkE/VV/2L8kAVAdYPP+Igpyqobib+2gLD6wiufCXRUog0jGtYMCZA
wmGi43zWbXSqDhZ8tsyFLaHVbSqBlNRdiSW3XDB4hIrrveEF4++Cd0ecl3VIyXii
gGxSNJajZxGXtDwQer2dF15J8GSi6inZ+ZJLSj30EcTnPzsLcdcZItnE9m/getQs
3OMMDqnTvfYw/HrT9xcnOhg+YP2+NuufpOXXbQTbJXyQm0uDn6iFKIXVUPhek9R7
SEtDxmqBYrL95+c9IvQq
=8D0j
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-01-08 20:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-05 4:09 [gentoo-dev] libtool lt_dlopenext vs. gen_ld_script: breakages at runtime Robin H. Johnson
2014-01-06 19:23 ` William Hubbs
2014-01-06 19:31 ` Robin H. Johnson
2014-01-08 8:59 ` [gentoo-dev] " Steven J. Long
2014-01-08 20:14 ` [gentoo-dev] " Peter Stuge
2014-01-08 20:27 ` Robin H. Johnson
2014-01-08 20:43 ` Rick "Zero_Chaos" Farina [this message]
2014-01-12 11:15 ` [gentoo-dev] " Steven J. Long
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52CDB85A.6030906@gentoo.org \
--to=zerochaos@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox