public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Craig Rodrigues <rodrigc@mediaone.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/3250: gcc 3.0 will not compile on SPARC Solaris 2.5.1 system
Date: Fri, 04 Jan 2002 21:06:00 -0000	[thread overview]
Message-ID: <20020105050602.22037.qmail@sources.redhat.com> (raw)

The following reply was made to PR bootstrap/3250; it has been noted by GNATS.

From: Craig Rodrigues <rodrigc@mediaone.net>
To: Tom Tromey <tromey@redhat.com>
Cc: rodrigc@gcc.gnu.org, gcc-bugs@gcc.gnu.org, steve@smc.vnet.net,
   gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/3250: gcc 3.0 will not compile on SPARC Solaris 2.5.1 system
Date: Sat, 5 Jan 2002 00:03:44 -0500

 On Fri, Jan 04, 2002 at 08:53:01PM -0700, Tom Tromey wrote:
 > We have seen problems like this in some situations.
 > 
 > In this case, toplev.c needs <locale.h>.  I don't see this include.
 > Perhaps it is hidden somewhere, though I failed to find that as well.
 > 
 > Steve's approach to a fix seems reasonable to me.
 > 
 > Tom
 
 Tom,
 
 toplev.c already includes intl.h which has:
 
 #ifdef HAVE_LOCALE_H
 # include <locale.h>
 #endif
 
 If the configure script did not correctly detect
 locale.h on the system, then that might cause
 problems.  I'm wondering, is this a repeat of the problems
 you saw in:
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?pr=4972&database=gcc&cmd=view
 
 


             reply	other threads:[~2002-01-05  5:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-04 21:06 Craig Rodrigues [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-17 18:30 rodrigc
2002-01-18  8:16 Craig Rodrigues
2002-01-18  8:06 Craig Rodrigues
2002-01-04 19:46 Tom Tromey
2001-12-26 20:13 rodrigc
2001-06-19  0:46 steve

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=20020105050602.22037.qmail@sources.redhat.com \
    --to=rodrigc@mediaone.net \
    --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: 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).