From: Grant Grundler <grundler@parisc-linux.org>
To: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] xfree86 4.2.1-9 build problem
Date: Sun, 10 Aug 2003 22:34:57 -0600 [thread overview]
Message-ID: <20030811043457.GA5653@dsl2.external.hp.com> (raw)
Hi all,
This started out as an issue with glxinfo program in xfree86.
The basic problem is glxinfo (C program) links against libGLU.so
(C++ built library). But glxinfo fails to link using gcc:
...
gcc -o glxinfo -g -O -ansi -pedantic -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wredundant-decls -Wnested-externs -Wundef -L../../exports/lib glxinfo.o -lGLU -lGL -lXext -lX11 -lpthread -lm -Wl,-rpath-link,../../exports/lib
../../exports/lib/libGLU.so: undefined reference to `_Unwind_SjLj_Resume@GCC_3.0'
../../exports/lib/libGLU.so: undefined reference to `_Unwind_SjLj_Register@GCC_3.0'
/usr/bin/../lib/libstdc++.so.5: undefined reference to `_Unwind_SjLj_RaiseException@GCC_3.0'
../../exports/lib/libGLU.so: undefined reference to `_Unwind_SjLj_Unregister@GCC_3.0'
/usr/bin/../lib/libstdc++.so.5: undefined reference to `_Unwind_SjLj_Resume_or_Rethrow@GCC_3.3'
collect2: ld returned 1 exit status
...
If I use g++ instead, glxinfo links just fine since libgcc_eh.a gets
picked up automagically. But it seems wrong to require a C program
link using g++.
Is libGLU.so getting built wrong? (ie resolved in libGLU.so directly)
Or should C programs not use C++ built libs? (How can the author know?)
Or is this a bug in gcc/binutils? (not picking up libgcc_eh.a)
This might be a generic problem since a few other libs on
my box have _Unwind_SjLj_Resume (for example) unresolved:
libasprintf.a
libgmpxx.a
libncurses++.a
thanks,
grant
next reply other threads:[~2003-08-11 4:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-11 4:34 Grant Grundler [this message]
2003-08-11 7:11 ` [parisc-linux] xfree86 4.2.1-9 build problem Joel Soete
2003-08-11 14:07 ` Carlos O'Donell
2003-08-11 14:24 ` John David Anglin
2003-08-11 15:24 ` Grant Grundler
2003-08-11 16:41 ` Joel Soete
2003-08-11 17:30 ` John David Anglin
2003-08-11 19:09 ` Grant Grundler
2003-08-11 19:25 ` John David Anglin
2003-08-11 20:21 ` Carlos O'Donell
2003-08-11 20:41 ` John David Anglin
2003-08-11 19:27 ` Carlos O'Donell
2003-08-11 19:12 ` Grant Grundler
2003-08-11 20:38 ` John David Anglin
2003-08-11 20:55 ` John David Anglin
2003-08-11 22:39 ` Grant Grundler
2003-08-11 22:58 ` John David Anglin
2003-08-11 23:55 ` John David Anglin
2003-08-13 17:53 ` Grant Grundler
2003-08-13 20:11 ` James Bottomley
2003-08-13 21:32 ` Grant Grundler
2003-08-13 22:53 ` James Bottomley
2003-08-14 0:12 ` Alan Cox
2003-08-14 5:12 ` Grant Grundler
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=20030811043457.GA5653@dsl2.external.hp.com \
--to=grundler@parisc-linux.org \
--cc=parisc-linux@lists.parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.