From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com
Subject: Re: needed-list fails in libiberty
Date: Tue, 14 Apr 2009 14:19:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0904141417090.2174@digraph.polyomino.org.uk> (raw)
In-Reply-To: <83vdp7mile.fsf@gnu.org>
On Tue, 14 Apr 2009, Eli Zaretskii wrote:
> The following snippet from libiberty/Makefile.in:
>
> # needed-list is used by libstdc++. NEEDED is the list of functions
> # to include there. Do not add anything LGPL to this list; libstdc++
> # can't use anything encumbering.
Since this comment relates to libstdc++ v2 and GCC 3.0 and later do not
use this, removing all the obsolete code (and maybe everything relating to
building a target libiberty) would be the obvious fix for any problems
with it.
(As far as I can tell, the only use of any libiberty code for the target
is libstdc++-v3 using a demangler source file; libiberty built for the
target doesn't seem to be used at all.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2009-04-14 14:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 14:10 Eli Zaretskii
2009-04-14 14:19 ` Joseph S. Myers [this message]
2009-04-14 14:42 ` Eli Zaretskii
2009-04-15 0:30 ` Ian Lance Taylor
2009-04-15 8:15 ` Eli Zaretskii
2009-04-15 13:50 ` Ian Lance Taylor
2009-04-16 17:47 ` Eli Zaretskii
2009-04-25 9:58 ` Eli Zaretskii
2009-04-25 22:41 ` Ian Lance Taylor
2009-04-26 17:44 ` Eli Zaretskii
2009-04-26 2:23 ` DJ Delorie
2009-04-26 17:44 ` Eli Zaretskii
2009-04-14 14:10 Eli Zaretskii
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=Pine.LNX.4.64.0904141417090.2174@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
/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