public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: law@redhat.com To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/3250: gcc Date: Fri, 18 Jan 2002 13:46:00 -0000 [thread overview] Message-ID: <20020118214605.9685.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/3250; it has been noted by GNATS. From: law@redhat.com To: Craig Rodrigues <rodrigc@mediaone.net> Cc: jzago@ifaedi.insa-lyon.fr, gcc-gnats@gcc.gnu.org, rodrigc@gcc.gnu.org, gcc-bugs@gcc.gnu.org Subject: Re: bootstrap/3250: gcc Date: Fri, 18 Jan 2002 14:40:48 -0700 In message <20020118163620.A4723@mediaone.net>, Craig Rodrigues writes: > Hi, > > This is the source of the problem: > > configure:4839: checking for locale.h > configure:4849: gcc -E conftest.c >/dev/null 2>conftest.out > In file included from /usr/include/locale.h:157, > from configure:4845: > /users/ie/jza/arch/lauhpj7/lib/gcc-lib/hppa2.0w-hp-hpux11.00/2.95.3/include/ > stdio.h:30: warning: `__va__list' redefined > /usr/include/locale.h:26: warning: this is the location of the previous defi > nition > configure: failed program was: > #line 4844 "configure" > #include "confdefs.h" > #include <locale.h> gcc-2.95.xx is not supported on hpux11. This one of the various different failure modes. It may also be the case that gcc-3.0.x will not work on your platform -- you've got one or more patches from HP which affect GCC's behavior in various unpleasant ways. On a more positive note the current development tree knows how to deal with the HP patches you've got installed on that system and should work properly. jeff
next reply other threads:[~2002-01-18 21:46 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-18 13:46 law [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-01-21 8:06 law 2002-01-18 16:26 Craig Rodrigues 2002-01-18 15:26 law 2002-01-18 14:06 Craig Rodrigues 2002-01-18 13:46 Craig Rodrigues 2002-01-18 9:06 jzago
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=20020118214605.9685.qmail@sources.redhat.com \ --to=law@redhat.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.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: linkBe 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).