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/5275: stat.h parse error in fdmatch.c on Solaris 2.8 Date: Sat, 05 Jan 2002 12:46:00 -0000 [thread overview] Message-ID: <20020105204602.4203.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/5275; it has been noted by GNATS. From: Craig Rodrigues <rodrigc@mediaone.net> To: Laszlo Megyeri <Laszlo.Megyeri@eth.ericsson.se> Cc: rodrigc@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: bootstrap/5275: stat.h parse error in fdmatch.c on Solaris 2.8 Date: Sat, 5 Jan 2002 15:39:17 -0500 On Sat, Jan 05, 2002 at 10:24:20AM +0100, Laszlo Megyeri wrote: > - I used binutils 2.11.2 compiled by gcc3.0.2 > (this gcc3.0.2 was compiled on Solaris 2.6) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ I suspect that this is your problem. I know that the header files for some basic types changed on Solaris between 2.6 and 2.7, and between 2.7 and 2.8. For this reason, I do not think a version of gcc compiled under Solaris 2.6 will work under Solaris 2.8, because when you built gcc, the configure script made some assumptions based on the Solaris 2.6 header files. I'm not sure what the workaround is at this point. There is a version of gcc 3.0.3 for Solaris 2.8 at http://www.sunfreeware.com. Could you try that? -- Craig Rodrigues http://www.gis.net/~craigr rodrigc@mediaone.net
next reply other threads:[~2002-01-05 20:46 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-05 12:46 Craig Rodrigues [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-01-09 23:06 rodrigc 2002-01-05 1:26 Laszlo Megyeri 2002-01-04 10:26 rodrigc 2002-01-04 8:16 Laszlo.Megyeri
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=20020105204602.4203.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: 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).