From: Ian Lance Taylor <iant@google.com>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Cc: Paolo Bonzini <bonzini@gnu.org>,
binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix PR bootstrap/42798
Date: Fri, 04 Jun 2010 14:59:00 -0000 [thread overview]
Message-ID: <mcrocfqaloq.fsf@dhcp-172-17-9-151.mtv.corp.google.com> (raw)
In-Reply-To: <20100603065852.GA28617@gmx.de> (Ralf Wildenhues's message of "Thu\, 3 Jun 2010 08\:58\:57 +0200")
Ralf Wildenhues <Ralf.Wildenhues@gmx.de> writes:
> This is the followup patch for src. Tested by building binutils+gdb,
> I'm starting a combined tree with --enable-build-with-cxx now.
> Ok to commit if no problems show up?
>
> A note to the gold change: I've looked at git glibc headers, of the
> declarations tested only 'basename' was overloaded. If more are added
> in the future, the configure.ac files need to be adjusted to give
> parameters for them, too. This applies to the whole tree of course for
> --enable-build-with-cxx, not just for gold.
With regard to the gold change. What will happen if the system header
files provide only a declaration
char *basename(const char *)
?
Since gold doesn't actually basename, another option here would be to
skip the check of the basename declaration entirely. In fact, we
should consider dropping basename from libiberty; our code should in
general use lbasename anyhow.
Ian
next prev parent reply other threads:[~2010-06-04 14:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100601204405.GA1170@gmx.de>
[not found] ` <AANLkTim4-8VpK907cHTIcT2ELeZEgOBpLf0FUJmpPCJN@mail.gmail.com>
[not found] ` <20100602111845.GA16161@ins.uni-bonn.de>
[not found] ` <4C064B77.3020207@gnu.org>
2010-06-03 6:33 ` Ralf Wildenhues
2010-06-03 6:59 ` Ralf Wildenhues
2010-06-04 14:59 ` Ian Lance Taylor [this message]
2010-06-04 15:04 ` Paolo Bonzini
2010-06-04 18:44 ` Ralf Wildenhues
2010-06-06 11:28 ` Ralf Wildenhues
2010-06-06 21:42 ` Ian Lance Taylor
2010-06-07 6:11 ` Ralf Wildenhues
2010-06-07 14:04 ` Ian Lance Taylor
2010-06-07 20:24 ` Ralf Wildenhues
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=mcrocfqaloq.fsf@dhcp-172-17-9-151.mtv.corp.google.com \
--to=iant@google.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=binutils@sourceware.org \
--cc=bonzini@gnu.org \
--cc=gdb-patches@sourceware.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