From: "Tobias Schlüter" <tobias.schlueter@physik.uni-muenchen.de>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Bootstrap broken on darwin / fink
Date: Mon, 01 Jun 2009 13:27:00 -0000 [thread overview]
Message-ID: <4A23D731.7000702@physik.uni-muenchen.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0906011042220.28902@digraph.polyomino.org.uk>
Joseph S. Myers wrote:
> On Mon, 1 Jun 2009, Tobias Schlüter wrote:
>
>> The complaint is about:
>> ICONV_CONST char *inbuf = CONST_CAST (char *, ident);
>> [...snip...]
>> iconv_ret = iconv (cd, &inbuf, &inbytesleft,
>> &outbuf, &outbytesleft);
>
> The types are exactly the same as in the corresponding code in
> libcpp/charset.c.
>
> ICONV_CONST char *inbuf;
> iconv (cd, &inbuf, &inbytesleft, &outbuf, &outbytesleft);
>
> You'll need to work out what's different on your system between gcc and
> libcpp to make it work in one place only. Note that iconv.m4 comes from
> gettext; it's possible the configure support has since been refined
> upstream and should be updated.
>
In gcc/auto-host.h I have #define HAVE_ICONV_H, whereas in libcpp/ I
haven't. From PR31932, I presume that HAVE_ICONV_H should never be
defined. The check is explicitly made in AC_CHECK_HEADERS in
gcc/configure.ac. I can't see what happens if I remove the check as
fink symlinks autoconf-2.59 to autoconf which in turn is a symlink to
autoconf-2.63.
Cheers,
- Tobi
next prev parent reply other threads:[~2009-06-01 13:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 10:08 Tobias Schlüter
2009-06-01 10:44 ` Joseph S. Myers
2009-06-01 13:27 ` Tobias Schlüter [this message]
2009-06-01 13:18 ` Peter O'Gorman
2009-06-01 14:20 ` Jack Howarth
2009-06-01 15:03 ` Tobias Schlüter
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=4A23D731.7000702@physik.uni-muenchen.de \
--to=tobias.schlueter@physik.uni-muenchen.de \
--cc=gcc@gcc.gnu.org \
--cc=joseph@codesourcery.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).