public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: pagnin@sssup.it To: gcc-gnats@gcc.gnu.org Subject: bootstrap/10028: gcc 3.1 and later up to 3.2.2 included, does not boostrap on alpha Tru64 Unix 5.1B using the native Compaq C compiler Date: Tue, 11 Mar 2003 15:26:00 -0000 [thread overview] Message-ID: <20030311152552.10031.qmail@sources.redhat.com> (raw) >Number: 10028 >Category: bootstrap >Synopsis: gcc 3.1 and later up to 3.2.2 included, does not boostrap on alpha Tru64 Unix 5.1B using the native Compaq C compiler >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Tue Mar 11 15:26:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Davide Pagnin >Release: gcc version 3.2.2 >Organization: >Environment: uname -a OSF1 V5.1 2650 alpha CC = /bin/cc (native Compaq C compiler) >Description: In the 3.1 and subsequent series of gcc, a workaround for a fstat (and friends) class of function not properly exposed in Tru64 Unix has been introduced. (Relevant PR ID number is: 6126) The workaround, that applies to Tru64 Unix 5.1A (and to 5.1 as far as I know) is included in the os and platform specific file: gcc/config/alpha/osf.h as a define for CPP_SUBTARGET_SPEC: -D__EXTERN_PREFIX This workaround plays bad with fixes that Compaq (now HP) has introduced to Tru64 Unix 5.1B, and in particular with the new /usr/include/sys/stat.h file By issuing a make bootstrap, after building the first stage, you get errors indicating that _F64__F64_ symbols aren't defined (this is due to the fact that both HP fixes and gcc osf workaround help in add a _F64_ symbol before *stat class of function and ending up in add that symbol twice!) By removing -D__EXTERN_PREFIX the compilation completes cleanly (but then the old bug will return if you compile the source gcc on a Tru64 Unix 5.1A system) >How-To-Repeat: On a Tru64 Unix 5.1B alpha system: setenv CC /bin/cc ./configure make bootstrap >Fix: remove -D__EXTERN_PREFIX on 5.1B osf perhaps a proper workaround can be generated by correctly fix the /usr/include/sys/stat.h file, through a fixinclude macro (tough I have not the knowledge do produce it) >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-03-11 15:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-11 15:26 pagnin [this message] 2003-03-11 21:20 ro
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=20030311152552.10031.qmail@sources.redhat.com \ --to=pagnin@sssup.it \ --cc=gcc-gnats@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).