public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Pedro Lamarão" <pedro.lamarao@ccppbrasil.org>
To: "Jason Merrill" <jason@redhat.com>,
	"Pedro Lamarão" <pedro.lamarao@ccppbrasil.org>,
	gcc@gcc.gnu.org
Subject: Re: [gcc-in-cxx] Trunk fails to bootstrap with --enable-build-with-cxx
Date: Thu, 27 Aug 2009 02:44:00 -0000	[thread overview]
Message-ID: <15727b460908261524m409f0ab0n654cbed5cf6b70af@mail.gmail.com> (raw)
In-Reply-To: <20090826213654.GA18470@gmx.de>

2009/8/26 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>:

>> >.../../trunk/libcpp/../include/libiberty.h:106: error: new declaration
>> >‘char* basename(const char*)’
>> >/usr/include/string.h:601: error: ambiguates old declaration ‘const
>> >char* basename(const char*)’
>>
>> The problem is that AC_CHECK_DECLS gets confused by overloaded
>> functions, and glibc 2.10 has overloaded declarations of basename
>> and some other string functions for const-correctness.
>
> Could you show the config.log snippet that shows the failed test?
> Is this a new error due to the autotools upgrade, or new due to
> glibc 2.10?

I think this is new in glibc 2.10, for the reasons given by Jason Merrill above.
I've discussed this problem with Jerry Quinn before, and he had a
tentative patch that worked for me.
As I understand things, this patch is on hold waiting for a solution
to the bootstrap comparison problem being discussed in another thread.

I am waiting for a solution to these problems to continue work on the
std::sort gcc-in-cxx subproject; keeping all these patches up to date
with trunk is too difficult for me right now.
Currently, I have a patch to an old revision of the trunk.

--
 P.

  reply	other threads:[~2009-08-26 22:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-03 21:35 Pedro Lamarão
2009-08-26 22:24 ` Jason Merrill
2009-08-27  1:44   ` Ralf Wildenhues
2009-08-27  2:44     ` Pedro Lamarão [this message]
2009-09-10 20:06       ` Ralf Wildenhues
2009-09-10 20:23         ` Pedro Lamarão
2009-08-28  3:05     ` Jason Merrill
2009-09-13 17:41 Jerry Quinn
2009-09-14  2:25 ` Ian Lance Taylor

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=15727b460908261524m409f0ab0n654cbed5cf6b70af@mail.gmail.com \
    --to=pedro.lamarao@ccppbrasil.org \
    --cc=gcc@gcc.gnu.org \
    --cc=jason@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).