public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rkl@connect.org.uk To: gcc-gnats@gcc.gnu.org Subject: bootstrap/4097: "make bootstrap" fails in HP-UX (10.20 or 11.00) Date: Thu, 23 Aug 2001 08:26:00 -0000 [thread overview] Message-ID: <20010823151659.403.qmail@sourceware.cygnus.com> (raw) >Number: 4097 >Category: bootstrap >Synopsis: "make bootstrap" fails in HP-UX (10.20 or 11.00) >Confidential: no >Severity: critical >Priority: high >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu Aug 23 08:26:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: rkl@connect.org.uk >Release: 3.0.1 (and all 2.95.X releases too) >Organization: >Environment: HP-UX 10.20 or 11.00. Flaw is in all platforms, but HP-UX is one of the few to highlight it. >Description: There is a serious flaw in the "make bootstrap" procedure: If you "make bootstrap", the stage2 build fails because it tries to link gcc-built .o files using the "cc" command. You cannot do this in HP-UX (results in an "__main not found" error when using cc to link - this is because gcc adds that symbol when linking, but cc doesn't). This has affected all 2.95.X and 3.X releases on HP-UX 10.20 and 11.00 to date. >How-To-Repeat: Use HP's C (K&R C or ANSI C, it doesn't matter) for the build - we assume, quite correctly, that the end-user doesn't have gcc already installed (this is the case with a new HP-UX 10.20 or 11.00 system). If you have gcc installed, move it out of the way first. Run configure (will pick up HP's cc), then type "make bootstrap". Build will fail during stage2. >Fix: There is no current fix I have for this, except the workaround of using "make" instead of "make bootstrap". This brings its own problems (which I worked through - hence my other HP-UX-filed reports today, which can't be dismissed yet because "make bootstrap" isn't working on HP-UX). The fix is to make sure that stage2 builds do *not* use the native compiler for linking, but actually use the intermediate gcc built with stage1 ("xgcc" I think) to link. The Makefiles are a bit too complex for me to work out how to do that :-) >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-08-23 8:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-08-23 8:26 rkl [this message] 2001-08-24 1:38 aoliva
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=20010823151659.403.qmail@sourceware.cygnus.com \ --to=rkl@connect.org.uk \ --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).