This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Shared library that needs stuff from another library...
- To: gcc at gcc dot gnu dot org
- Subject: Shared library that needs stuff from another library...
- From: Mark Crosland <mjc at c1000907-b dot sttls1 dot wa dot home dot com>
- Date: Tue, 7 Sep 1999 12:49:24 -0700 (PDT)
I am building some s/w I want to put into a shared library. It is a C++
class library that uses stuff that is in libstdc++.
If I build gcc with -enable-shared, everything builds fine.
If I build gcc without -enable-shared my shared library doesn't quite make
it, g++ exits with lots of complaints about "relocations remain against
allocatable but non-writable sections".
Is there a way (link flag?) to build my shared lib against a statically
built libstdc++, i.e., when I build my lib, the linker pulls in the stuff
my lib needs from libstdc++.a?
I would rather not have to distribute libstdc++.so with our product...
Thanks,
Mark Crosland