From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] libtool lt_dlopenext vs. gen_ld_script: breakages at runtime
Date: Mon, 6 Jan 2014 13:23:53 -0600 [thread overview]
Message-ID: <20140106192353.GA2191@laptop.home> (raw)
In-Reply-To: <robbat2-20140105T033326-886000793Z@orbis-terrarum.net>
[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]
The reason that gen_usr_ldscript exists is that we do not install
static libraries in /. I think the argument for this is that they
aren't needed at boot time. I would agree that they are not, but, given
all of the issues we have had in the past with gen_usr_ldscript, and
that issues keep coming up with it, I would like to propose something
different.
I would like to propose that we stop splitting the installation
locations of libraries and use the upstream build systems to install the
libraries where we want them. If we do that, it means we could get rid
of gen_usr_ldscript completely.
We could start doing this today, except that portage has a hard ban
against installing static libraries in /, which I have opened up a bug
about [1]. I don't know when or why the hard ban was introduced, but I'm sure
it was pre-2004 and pre-council.
The down side of doing this that I see would be that people who have
static-libs in their use flags might have / too small to have the static
libs installed there.
Thoughts?
William
[1] https://bugs.gentoo.org/show_bug.cgi?id=492542
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-01-06 19:24 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 [this message]
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
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=20140106192353.GA2191@laptop.home \
--to=williamh@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