public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: hughett@bbl.med.upenn.edu To: gcc-gnats@gcc.gnu.org Subject: bootstrap/8796: Bootstrap fails on Tru64 4.0f with native make and cc Date: Tue, 03 Dec 2002 07:06:00 -0000 [thread overview] Message-ID: <20021203150235.3085.qmail@sources.redhat.com> (raw) >Number: 8796 >Category: bootstrap >Synopsis: Bootstrap fails on Tru64 4.0f with native make and cc >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Tue Dec 03 07:06:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Paul Hughett >Release: gcc 3.2.1 >Organization: >Environment: alphaev6-dec-osf4.0f using native cc and make (Tru64 4.0f) >Description: Cannot bootstrap gcc-3.2.1 on alphaev6-dec-osf4.0f using the native make and cc without manually tweaking the build process. >How-To-Repeat: When bootstrapping gcc-3.2.1 on alphaev6-dec-osf4.0f using the native make and cc and configured as ../$srcdir/configure --disable-threads make bootstrap dies after generating an error . . . (cd intl && make all) . . . cc -c -DIN_GCC -DLOCALEDIR=\"/usr/local/gcc-3.2.1/share/locale\" -DLOCALE_ALIAS_PATH=\"/usr/local/gcc-3.2.1/share/locale\" -DLIBDIR=\"/usr/local/gcc-3.2.1/lib\" -DHAVE_CONFIG_H -I.. -I. -I../../../gcc-3.2.1/gcc/intl -I../../../gcc-3.2.1/gcc -I../../../gcc-3.2.1/gcc/config -I../../../gcc-3.2.1/gcc/../include -g plural.c -o plural.o cc: Severe: No such file or directory ... file is 'plural.c' >Fix: Creating a link from $bindir/gcc/intl/plural.c to $srcdir/gcc/intl/plural.c and typing make bootstrap again fixes this error. On a fresh build directory, creating the link after configure but before make bootstrap works without any errors. >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-12-03 15:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-03 7:06 hughett [this message] 2003-05-14 9:46 Dara Hazeghi 2003-05-14 10:50 giovannibajo
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=20021203150235.3085.qmail@sources.redhat.com \ --to=hughett@bbl.med.upenn.edu \ --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).