public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: joel@gcc.gnu.org
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/3366: i960-elf fails to compile on gcc 3.0 CVS branch
Date: Fri, 22 Jun 2001 07:56:00 -0000 [thread overview]
Message-ID: <20010622145011.1339.qmail@sourceware.cygnus.com> (raw)
>Number: 3366
>Category: bootstrap
>Synopsis: i960-elf fails to compile on gcc 3.0 CVS branch
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Jun 22 07:56:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: joel@OARcorp.com
>Release: gcc 3.0 CVS branch
>Organization:
>Environment:
GNU/Linux RedHat 6.2 targetting i960-elf
>Description:
../gcc/configure --target=i960-elf --with-gnu-as --with-gnu-ld --with-newlib --verbose --prefix=/usr1/tmp-tools --enable-languages=c,c++ && make
fails with this error:
usr3/ftp_archive/gnu/gcc/ss/b3/b-i960-elf/gcc/xgcc -B/usr3/ftp_archive/gnu/gcc/ss/b3/b-i960-elf/gcc/ -nostdinc -B/usr3/ftp_archive/gnu/gcc/ss/b3/b-i960-elf/i960-elf/newlib/ -isystem /usr3/ftp_archive/gnu/gcc/ss/b3/b-i960-elf/i960-elf/newlib/targ-include -isystem /usr3/ftp_archive/gnu/gcc/ss/b3/gcc/newlib/libc/include -B/usr1/tmp-tools/i960-elf/bin/ -B/usr1/tmp-tools/i960-elf/lib/ -isystem /usr1/tmp-tools/i960-elf/include -DCROSS_COMPILE -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include libgcc1-test.o -o libgcc1-test \
-nostartfiles -nostdlib `/usr3/ftp_archive/gnu/gcc/ss/b3/b-i960-elf/gcc/xgcc -B/usr3/ftp_archive/gnu/gcc/ss/b3/b-i960-elf/gcc/ -nostdinc -B/usr3/ftp_archive/gnu/gcc/ss/b3/b-i960-elf/i960-elf/newlib/ -isystem /usr3/ftp_archive/gnu/gcc/ss/b3/b-i960-elf/i960-elf/newlib/targ-include -isystem /usr3/ftp_archive/gnu/gcc/ss/b3/gcc/newlib/libc/include -B/usr1/tmp-tools/i960-elf/bin/ -B/usr1/tmp-tools/i960-elf/lib/ -isystem /usr1/tmp-tools/i960-elf/include --print-libgcc-file-name`
libgcc1-test.o: In function `_main_without__main':
libgcc1-test.o(.text+0x4c): undefined reference to `___truncdfsf2'
libgcc1-test.o(.text+0x68): undefined reference to `___truncdfsf2'
libgcc1-test.o(.text+0x178): undefined reference to `___adddf3'
libgcc1-test.o(.text+0x194): undefined reference to `___subdf3'
libgcc1-test.o(.text+0x1b0): undefined reference to `___muldf3'
libgcc1-test.o(.text+0x1cc): undefined reference to `___divdf3'
libgcc1-test.o(.text+0x1fc): undefined reference to `___addsf3'
libgcc1-test.o(.text+0x208): undefined reference to `___extendsfdf2'
libgcc1-test.o(.text+0x224): undefined reference to `___subsf3'
libgcc1-test.o(.text+0x230): undefined reference to `___extendsfdf2'
libgcc1-test.o(.text+0x24c): undefined reference to `___mulsf3'
libgcc1-test.o(.text+0x258): undefined reference to `___extendsfdf2'
libgcc1-test.o(.text+0x274): undefined reference to `___divsf3'
libgcc1-test.o(.text+0x280): undefined reference to `___extendsfdf2'
libgcc1-test.o(.text+0x2a0): undefined reference to `___extendsfdf2'
libgcc1-test.o(.text+0x2b8): undefined reference to `_(float, int, long long, double, float, short, int)'
libgcc1-test.o(.text+0x2d0): undefined reference to `_(float, int, long long, short, float, short, int)'
etc...
>How-To-Repeat:
configure and build per description.
I used binutils 2.10 and newlib 1.9.0
>Fix:
unknown
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-06-22 7:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-22 7:56 joel [this message]
2001-07-06 11:10 neil
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=20010622145011.1339.qmail@sourceware.cygnus.com \
--to=joel@gcc.gnu.org \
--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: link
Be 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).