public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "croze at nsisoftware dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/12462] gcc-3.3.1 can't build shared library with libstdc++.a
Date: Fri, 14 Nov 2003 21:11:00 -0000 [thread overview]
Message-ID: <20031114211123.29266.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030930150333.12462.bs@okyz.com>
------- Additional Comments From croze at nsisoftware dot com 2003-11-14 21:11 -------
I have also seen this issue on RedHat 9. Here is the build output:
g++ -v -g -fPIC -shared -static-libgcc -L../../Common/lib/Linux/debug \
-o lib/Linux/debug/libRSResource.so \
src/obj/Linux/debug/ComputerSystemInfo.o src/obj/Linux/debug/RSResource.o
src/obj/Linux/debug/OemNone.o \
-Wl,-static -lpthread -ldl -lCommon
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --enable-shared --enable-threads=posix
--disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux
Thread model: posix
gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)
/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/collect2 --eh-frame-hdr -m elf_i386
-shared -o lib/Linux/debug/libRSResource.so
/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/../../../crti.o
/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/crtbeginS.o
-L../../../Common_3party/ObjectSpace.Solaris/lib/Linux
-L../../Common/lib/Linux/debug -L/usr/lib/gcc-lib/i386-redhat-linux/3.2.2
-L/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/../../..
src/obj/Linux/debug/ComputerSystemInfo.o src/obj/Linux/debug/RSResource.o
src/obj/Linux/debug/OemNone.o -static -lpthread -ldl -lospace -lCommon
-lstdc++ -lm -lgcc -lgcc_eh -lc -lgcc -lgcc_eh
/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/crtendS.o
/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/../../../crtn.o
/usr/bin/ld: lib/Linux/debug/libRSResource.so: undefined versioned symbol name
std::time_put_w@@GLIBCPP_3.2
/usr/bin/ld: failed to set dynamic section sizes: Bad value
(In reply to comment #0)
> gcc -shared doesn't work
> i want to make a shared library, and i link with the static library libstdc++.a
> ld answer me that libstdc++.a isn't position independant code (PIC).
> I built gcc.3.3.1 passing with-pic and disable-shared to configure, but the HP
> linker still doesn't want to link with libstdc++.a, which isn't a PIC library
> for him. (try to compile with +Z)
> i have installed the latest ld linker HP patch.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12462
next prev parent reply other threads:[~2003-11-14 21:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 15:43 [Bug bootstrap/12462] New: " bs at okyz dot com
2003-10-28 15:31 ` [Bug bootstrap/12462] " pinskia at gcc dot gnu dot org
2003-11-08 21:15 ` dhazeghi at yahoo dot com
2003-11-14 21:11 ` croze at nsisoftware dot com [this message]
2004-01-20 13:56 ` bangerth at dealii dot org
2004-01-28 17:37 ` pinskia at gcc dot gnu dot org
2004-10-06 11:30 ` pinskia at gcc dot gnu dot org
2004-10-06 11:53 ` pinskia at gcc dot gnu dot org
2004-10-06 12:05 ` info at yourkit dot com
2004-10-06 12:43 ` pinskia at gcc dot gnu dot org
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=20031114211123.29266.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).