public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ray.degennaro@eriscorp.com To: gcc-gnats@gcc.gnu.org Subject: bootstrap/8304: quadlib.c can't be found Date: Mon, 21 Oct 2002 11:16:00 -0000 [thread overview] Message-ID: <20021021180645.5696.qmail@sources.redhat.com> (raw) >Number: 8304 >Category: bootstrap >Synopsis: quadlib.c can't be found >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Oct 21 11:16:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Ray DeGennaro >Release: gcc-3.2 (build fails, can't 'gcc -v') >Organization: >Environment: OS: HP-UX B.11.00 Using latest GNU make and gcc-3.0.1-32 to build 3.2 >Description: When I try to do the bootsteap build, I get the following error on the first pass: ./xgcc -B./ -B/usr/contrib/hppa2.0w-hp-hpux11.00/bin/ -isystem /usr/contrib/hppa2.0w-hp-hpux11.00/include -isystem /usr/contrib/hppa2.0w-hp-hpux11.00/sys-include -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include -fPIC -g -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I. -I/tmp/gcc-3.2/gcc -I/tmp/gcc-3.2/gcc/. -I/tmp/gcc-3.2/gcc/config -I/tmp/gcc-3.2/gcc/../include -c /tmp/gcc-3.2/gcc/config/pa/quadlib.c -o libgcc/./quadlib.o xgcc: quadlib.c: No such file or directory xgcc: no input files make[3]: *** [libgcc/./quadlib.o] Error 1 make[3]: Leaving directory `/tmp/gcc-3.2-obj/gcc' make[2]: *** [libgcc.a] Error 2 make[2]: Leaving directory `/tmp/gcc-3.2-obj/gcc' make[1]: *** [stage1_build] Error 2 make[1]: Leaving directory `/tmp/gcc-3.2-obj/gcc' make: *** [bootstrap] Error 2 # It looks like the full path to quadlib.c was left off the "-c" argument. >How-To-Repeat: >Fix: Work-around: Change lines 106-107 of libgcc.mk (in OBJDIR) to: libgcc/./quadlib.o: stmp-dirs quadlib.c $(GCC_FOR_TARGET) $(LIBGCC2_CFLAGS) $(INCLUDES) -c /tmp/gcc-3.2/gcc/quadlib.c -o libgcc/./quadlib.o But that's for my build specifically, and it looks like the 'configure' files that build the libgcc.mk file will need to be fixed. >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2002-10-21 18:16 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20021021180645.5696.qmail@sources.redhat.com \ --to=ray.degennaro@eriscorp.com \ --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).