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: Mon, 21 Jan 2002 08:06:00 -0000 [thread overview] Message-ID: <20020121160601.28919.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: Mon, 21 Jan 2002 09:02:16 -0700 In message <20020118191617.A8286@mediaone.net>, Craig Rodrigues writes: > Now, PR 3250 reports the same error, but using > gcc 2.95.3 on Solaris 2.5.1: > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?database=gcc&pr=3250&cmd=view > > steve@smc.vnet.net rejects my e-mail domain, so I can't get feedback. :( > > What should I do with this PR?\ Unsure -- I scanned it, but didn't find the details I was looking for; specifically we'd need both the gcc.log output and maybe more details for the Solaris system (the gcc.log appears to be for hpux). It's also likely we'd have to look at the header files on the Solaris machine where this build is failing -- at least in the HPUX case the root of the problem is an annoying mis-match between va_list provided by the system header files and the one provided by GCC. This causes gcc-2.95.x era compilers to issue a warning (gcc-3.0.x compilers will ignore the minor mis-match). The warning causes the configure process to believe that locale.h is unusable. Thus HAVE_LOCALE_H is not defined and thus it isn't included by toplev.c. However configure did fine the setlocale function, so toplev.c has the call to setlocale which contains the LC_ALL as an argument. jeff
next reply other threads:[~2002-01-21 16:06 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-21 8:06 law [this message] -- strict thread matches above, loose matches on Subject: below -- 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 law 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=20020121160601.28919.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).