public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "david dot billinghurst at comalco dot riotinto dot com dot au" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/19796] [4.0 Regression] Bootstrap fails: Unresolved data symbol "set_fpc_csr" Date: Tue, 08 Feb 2005 13:55:00 -0000 [thread overview] Message-ID: <20050208003044.5511.qmail@sourceware.org> (raw) In-Reply-To: <20050206232304.19796.billingd@gcc.gnu.org> ------- Additional Comments From david dot billinghurst at comalco dot riotinto dot com dot au 2005-02-08 00:30 ------- Subject: RE: [4.0 Regression] Bootstrap fails: Unresolved data symbol "set_fpc_csr" I can see the problem here once I compile with -v. get_fpc_csr and set_fpc_csr are in libc.so, but -lc linked before stage1/irix-csr.o, so the routines aren't found. If I run collect2 by hand with -lc after irix-csr.o then all is well. bash-2.04$ stage1/xgcc -Bstage1/ -B/disk4/billingd/tmp/gcc/mips-sgi-irix6.5/bin/ -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wold-style-definition -Werror -fno-common -DHAVE_CONFIG_H -DGENERATOR_FILE -o build/genmodes build/genmodes.o build/errors.o ../build-mips-sgi-irix6.5/libiberty/libiberty.a -v Reading specs from stage1/specs Target: mips-sgi-irix6.5 Configured with: /disk4/billingd/src/gcc/configure --enable-shared --enable-haifa --enable-threads=single --enable-libjava --with-as=/disk4/billingd/tmp/binutils/bin/as --disable-nls --with-gmp=/usr/local --enable-languages=c,c++,java,objc,f95 --disable-libmudflap --prefix=/disk4/billingd/tmp/gcc Thread model: single gcc version 4.0.0 20050203 (experimental) stage1/collect2 -call_shared -no_unresolved -init __gcc_init -fini __gcc_fini -_SYSTYPE_SVR4 -woff 131 -n32 -o build/genmodes /usr/lib32/mips3/crt1.o stage1/irix-crti.o stage1/crtbegin.o -Lstage1 -L/disk4/billingd/tmp/gcc/lib/gcc/mips-sgi-irix6.5/../.. -L/lib/../lib32 -L/usr/lib/../lib32 build/genmodes.o build/errors.o ../build-mips-sgi-irix6.5/libiberty/libiberty.a -dont_warn_unused -lgcc -lgcc_eh -warn_unused -L/usr/lib32/mips3 -L/usr/lib32 -dont_warn_unused -lc -warn_unused -dont_warn_unused -lgcc -lgcc_eh -warn_unused stage1/irix-csr.o stage1/crtend.o stage1/irix-crtn.o /usr/lib32/mips3/crtn.o ld32: ERROR 33 : Unresolved data symbol "get_fpc_csr" -- 1st referenced by stage1/irix-csr.o. Use linker option -v to see when and which objects, archives and dsos are loaded. ld32: ERROR 33 : Unresolved data symbol "set_fpc_csr" -- 1st referenced by stage1/irix-csr.o. Use linker option -v to see when and which objects, archives and dsos are loaded. ld32: INFO 152: Output file removed because of error. collect2: ld returned 2 exit status NOTICE This e-mail and any attachments are private and confidential and may contain privileged information. If you are not an authorised recipient, the copying or distribution of this e-mail and any attachments is prohibited and you must not read, print or act in reliance on this e-mail or attachments. This notice should not be removed. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19796
next prev parent reply other threads:[~2005-02-08 0:30 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-02-07 6:02 [Bug bootstrap/19796] New: " billingd at gcc dot gnu dot org 2005-02-07 17:22 ` [Bug target/19796] [4.0 Regression] " pinskia at gcc dot gnu dot org 2005-02-07 20:34 ` cvs-commit at gcc dot gnu dot org 2005-02-07 20:48 ` rsandifo at gcc dot gnu dot org 2005-02-08 10:13 ` david dot billinghurst at comalco dot riotinto dot com dot au 2005-02-08 13:55 ` david dot billinghurst at comalco dot riotinto dot com dot au [this message] 2005-04-20 2:14 ` pinskia at gcc dot gnu dot org
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=20050208003044.5511.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).