Ok, here are the patches for the Makefile.am and Makefile.in files. I am also having trouble with the following issue: I need to make sure that one of the new libraries is linked in with libstdc++ when libstdc++ gets built. I have not been able to successfully figure out where exactly is the command that builds & links libstdc++.so.* (yes I've looked at the build; it's being built with libtool somewhere, somehow, and no matter where/how I specify the link flag to link in my new library, the libtool link command is not picking it up).
-- Caroline Tice cmt...@google.com On Fri, Oct 26, 2012 at 2:28 PM, Ian Lance Taylor <i...@google.com> wrote: > On Fri, Oct 26, 2012 at 10:58 AM, Caroline Tice <cmt...@google.com> wrote: >> >> I am working on a patch (which I hope to be able to submit in the next >> few days), and I have run into a snag that I am hoping someone can >> help me with. >> >> As part of this patch, I am trying to build two new *.a (static >> archive) libraries in libstdc++-v3/libsupc++. I have modified >> Makefile.am and rebuilt Makefile.in in libsupc++ to do this. I had >> this working just fine on GCC 4.6.3, but when I try to apply the >> changes to GCC ToT, I find that something in the build system seems to >> have changed: Not only is it building the two static archive >> libraries, it is ALSO then building two dynamic shared libraries (*.so >> files), which I do NOT want. And even worse, it's putting the wrong >> stuff into the .so files. I have not been able to find/isolate the >> code that is telling GCC to go build the .so files. As I said, this >> worked for me in GCC 4.6.3. Does anybody know what might be going >> wrong or where/how to fix this? Help, please?? > > Kind of hard to say without seeing the patch. Look at the build log, > and make sure that libtool is being invoked with --tag disable-shared. > That should be all that is required. > > Ian
Makefile.am.diff
Description: Binary data
Makefile.in.diff
Description: Binary data
