From: Nathanael Nerode <neroden@twcny.rr.com>
To: gcc@gcc.gnu.org
Subject: libffi failure during bootstrap
Date: Mon, 19 May 2003 17:05:00 -0000 [thread overview]
Message-ID: <20030519164936.GA3547@doctormoo> (raw)
I'm getting this when bootstrapping GCC mainline on i686-pc-linux-gnu:
make[3]: Entering directory
`/home/neroden/gnu/build/i686-pc-linux-gnu/libffi'
/bin/sh ./libtool --mode=link /home/neroden/gnu/build/gcc/xgcc
-B/home/neroden/gnu/build/gcc/
-B/home/neroden/gnu/inst/i686-pc-linux-gnu/bin/
-B/home/neroden/gnu/inst/i686-pc-linux-gnu/lib/ -isystem
/home/neroden/gnu/inst/i686-pc-linux-gnu/include -isystem
/home/neroden/gnu/inst/i686-pc-linux-gnu/sys-include
-L/home/neroden/gnu/build/ld -fexceptions -O2 -g -O2 -o ffitest
-shared-libgcc ffitest.lo libffi.la
/home/neroden/gnu/build/gcc/xgcc -B/home/neroden/gnu/build/gcc/
-B/home/neroden/gnu/inst/i686-pc-linux-gnu/bin/
-B/home/neroden/gnu/inst/i686-pc-linux-gnu/lib/ -isystem
/home/neroden/gnu/inst/i686-pc-linux-gnu/include -isystem
/home/neroden/gnu/inst/i686-pc-linux-gnu/sys-include -fexceptions -O2 -g
-O2 -o .libs/ffitest -shared-libgcc .libs/ffitest.o
-L/home/neroden/gnu/build/ld ./.libs/libffi.so -Wl,--rpath
-Wl,/home/neroden/gnu/inst/lib
./.libs/libffi.so: undefined reference to `FFI_TYPE_DOUBLE'
./.libs/libffi.so: undefined reference to `FFI_TYPE_SINT64'
./.libs/libffi.so: undefined reference to `FFI_TYPE_LONGDOUBLE'
./.libs/libffi.so: undefined reference to `FFI_TYPE_INT'
./.libs/libffi.so: undefined reference to `FFI_TYPE_FLOAT'
collect2: ld returned 1 exit status
make[3]: *** [ffitest] Error 1
Any ideas? Everything else is working so I'm guessing this really is a
libffi issue...
--Nathanael
next reply other threads:[~2003-05-19 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 17:05 Nathanael Nerode [this message]
2003-05-19 21:02 ` Anthony Green
2003-05-19 21:14 ` Neil Booth
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=20030519164936.GA3547@doctormoo \
--to=neroden@twcny.rr.com \
--cc=gcc@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).