From: Simon Strandman <simon.strandman@telia.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Glibc builds and --as-needed
Date: Wed, 12 Oct 2005 10:55:25 +0200 [thread overview]
Message-ID: <434CCF7D.1020109@telia.com> (raw)
In-Reply-To: <434C3BDB.7050301@gentoo.org>
Mark Loeser skrev:
>Simon Strandman wrote:
>
>
>>I'm curious why --as-needed is disabled for glibc builds. It was first
>>added over a year ago in one of the early 2.3.4 builds so is it still
>>nessecary?
>>
>>I tried removing it and had no problems building glibc and I could see
>>that it was used when looking at the compile output. Then I tried
>>bootstraping from stage1 with --as-needed and neither my amd64 or x86
>>has any problems completeing it. Perhaps this can be reconsidered?
>>
>>
>>
>
>Please file a bug. It'll be much easier for us to keep track of that way.
>
>Thanks,
>
>Mark
>
>
Ok! Done:
http://bugs.gentoo.org/show_bug.cgi?id=108976
--
Simon Strandman <simon.strandman@telia.com>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-10-12 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 20:43 [gentoo-dev] Glibc builds and --as-needed Simon Strandman
2005-10-11 22:25 ` Mark Loeser
2005-10-12 8:55 ` Simon Strandman [this message]
2005-10-11 23:56 ` Donnie Berkholz
2005-10-12 0:07 ` Mike Frysinger
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=434CCF7D.1020109@telia.com \
--to=simon.strandman@telia.com \
--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