From: Mark Wielaard <mark@klomp.org>
To: gcc-help@gcc.gnu.org
Subject: Build failure of GCC-3.0 branch on powerpc
Date: Mon, 19 Feb 2001 14:49:00 -0000 [thread overview]
Message-ID: <20010219234910.A16753@klomp.org> (raw)
Hi,
I am trying to build the GCC 3.0 branch on powerpc including gcj.
It is the CVS version of yesterday configured with --enable-languages=c++,java
It gives the following error:
make[6]: Entering directory `/opt/mark/gcc-obj/powerpc-unknown-linux-gnu/nof/libffi'
/bin/sh ./libtool --mode=link /opt/mark/gcc-obj/gcc/xgcc -B/opt/mark/gcc-obj/gcc/ -B/usr/local/gcc/powerpc-unknown-linux-gnu/bin/ -B/usr/local/gcc/powerpc-unknown-linux-gnu/lib/ -isystem /usr/local/gcc/powerpc-unknown-linux-gnu/include -msoft-float -fPIC -mstrict-align -fexceptions -g -O2 -msoft-float -fPIC -mstrict-align -msoft-float -fPIC -mstrict-align -o ffitest ffitest.o libffi.la
/opt/mark/gcc-obj/gcc/xgcc -B/opt/mark/gcc-obj/gcc/ -B/usr/local/gcc/powerpc-unknown-linux-gnu/bin/ -B/usr/local/gcc/powerpc-unknown-linux-gnu/lib/ -isystem /usr/local/gcc/powerpc-unknown-linux-gnu/include -msoft-float -fPIC -mstrict-align -fexceptions -g -O2 -msoft-float -fPIC -mstrict-align -msoft-float -fPIC -mstrict-align -o .libs/ffitest ffitest.o
./.libs/libffi.so+-Wl,--rpath -Wl,/usr/local/gcc/lib/nof
/usr/bin/ld: warning: libgcc_s_nof.so.0, needed by ./.libs/libffi.so, not found (try using --rpath)
./.libs/libffi.so: undefined reference to `__extendsfdf2@GCC_3.0'
collect2: ld returned 1 exit status
make[6]: *** [ffitest] Error 1
Someone suggested that configuring with --disable-multilib could be a
workaround. But that gives me the following error:
make[3]: Entering directory
`/opt/mark/gcc-obj/powerpc-unknown-linux-gnu/libffi'/bin/sh ./libtool --mode=link /opt/mark/gcc-obj/gcc/xgcc -B/opt/mark/gcc-obj/gcc/ -B/usr/local/gcc/powerpc-unknown-linux-gnu/bin/ -B/usr/local/gcc/powerpc-unknown-linux-gnu/lib/ -isystem /usr/local/gcc/powerpc-unknown-linux-gnu/include -fexceptions -g -O2 -o ffitest ffitest.o libffi.la
/opt/mark/gcc-obj/gcc/xgcc -B/opt/mark/gcc-obj/gcc/ -B/usr/local/gcc/powerpc-unknown-linux-gnu/bin/ -B/usr/local/gcc/powerpc-unknown-linux-gnu/lib/ -isystem /usr/local/gcc/powerpc-unknown-linux-gnu/include -fexceptions -g -O2 -o .libs/ffitest ffitest.o ./.libs/libffi.so -Wl,--rpath -Wl,/usr/local/gcc/lib
/usr/local/gcc/lib/libgcc_s.so.0: undefined reference to `__SBSS2_END__'
/usr/local/gcc/lib/libgcc_s.so.0: undefined reference to `__init'
/usr/local/gcc/lib/libgcc_s.so.0: undefined reference to `__SBSS_END__'
/usr/local/gcc/lib/libgcc_s.so.0: undefined reference to `__SDATA2_START__'
/usr/local/gcc/lib/libgcc_s.so.0: undefined reference to `__SDATA_START__'
collect2: ld returned 1 exit status
make[3]: *** [ffitest] Error 1
Could someone help me analyse this problem?
I can build a functional gcj compiler on i386.
Thanks,
Mark
--
Stuff to read:
< http://www.toad.com/gnu/whatswrong.html >
What's Wrong with Copy Protection, by John Gilmore
next reply other threads:[~2001-02-19 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-19 14:49 Mark Wielaard [this message]
2001-02-20 12:45 ` Mark Wielaard
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=20010219234910.A16753@klomp.org \
--to=mark@klomp.org \
--cc=gcc-help@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).