From: Andreas Jaeger <aj@suse.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: libffi broken with your latest change
Date: Mon, 19 May 2003 06:34:00 -0000 [thread overview]
Message-ID: <u84r3r5ujj.fsf@gromit.moeb> (raw)
Jakub,
this patch:
2003-05-16 Jakub Jelinek <jakub@redhat.com>
* configure.in (HAVE_RO_EH_FRAME): Check whether .eh_frame section
should be read-only.
* configure: Rebuilt.
* fficonfig.h.in: Rebuilt.
* include/ffi.h.in (EH_FRAME_FLAGS): Define.
* src/alpha/osf.S: Use EH_FRAME_FLAGS.
* src/powerpc/linux64.S: Likewise.
* src/powerpc/linux64_closure.S: Likewise. Include ffi.h.
* src/powerpc/sysv.S: Use EH_FRAME_FLAGS. Use pcrel encoding
if -fpic/-fPIC/-mrelocatable.
* src/powerpc/powerpc_closure.S: Likewise.
* src/sparc/v8.S: If HAVE_RO_EH_FRAME is defined, don't include
#write in .eh_frame flags.
* src/sparc/v9.S: Likewise.
* src/x86/unix64.S: Use EH_FRAME_FLAGS.
* src/x86/sysv.S: Likewise. Use pcrel encoding if -fpic/-fPIC.
* src/s390/sysv.S: Use EH_FRAME_FLAGS. Include ffi.h.
Is the only change to libffi in the last few days and since it's in,
i686-linux-gnu does not compile any more:
/builds/gcc/misc/gcc/xgcc -B/builds/gcc/misc/gcc/ -B/opt/gcc/3.4-devel/i686-suse-linux-gnu/bin/ -B/opt/gcc/3.4-devel/i686-suse-linux-gnu/lib/ -isystem /opt/gcc/3.4-devel/i686-suse-linux-gnu/include -isystem /opt/gcc/3.4-devel/i686-suse-linux-gnu/sys-include -fexceptions -O2 -g -O2 -o .libs/ffitest -shared-libgcc .libs/ffitest.o ./.libs/libffi.so -Wl,--rpath -Wl,/opt/gcc/3.4-devel/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[4]: *** [ffitest] Error 1
make[4]: Leaving directory `/builds/gcc/misc/i686-suse-linux-gnu/libffi'
Can you look into this, please?
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next reply other threads:[~2003-05-19 6:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 6:34 Andreas Jaeger [this message]
2003-05-19 6:49 ` Andreas Jaeger
2003-05-19 7:33 ` Andreas Jaeger
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=u84r3r5ujj.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
/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).