I apologize for not including the details. I issued the same command as the Makefile command that builds abi_check, but in addition I included the path to libsupc++.a and also added -v -lsupc++ /Storage2/gcc-3.2.3-bld2/gcc/g++ -v -shared-libgcc -B/Storage2/gcc-3.2.3-bld2/gcc/ -nostdinc++ -B/usr/local/m68k-next-nextstep3/bin/ -B/usr/local/m68k-next-nextstep3/lib/ -isystem /usr/local/m68k-next-nextstep3/include -g -O2 -o abi_check abi_check.o -L/Storage2/gcc-3.2.3-bld2/m68k-next-nextstep3/libstdc++-v3/src -L/Storage2/gcc-3.2.3-bld2/m68k-next-nextstep3/libstdc++-v3/src/.libs -L/Storage2/gcc-3.2.3-bld2/m68k-next-nextstep3/libstdc++-v3/libsupc++/.libs -lsupc++ -lm Reading specs from /Storage2/gcc-3.2.3-bld2/gcc/specs Configured with: ../gcc-3.2.3-NS/configure --prefix=/usr/local --enable-languages=c,c++ --disable-shared --disable-threads --enable-cpp --enable-obsolete m68k-next-nextstep3 Thread model: single gcc version 3.2.3 /Storage2/gcc-3.2.3-bld2/gcc/collect2 -o abi_check -lcrt0.o -lcrtbegin.o -L/Storage2/gcc-3.2.3-bld2/m68k-next-nextstep3/libstdc++-v3/src -L/Storage2/gcc-3.2.3-bld2/m68k-next-nextstep3/libstdc++-v3/src/.libs -L/Storage2/gcc-3.2.3-bld2/m68k-next-nextstep3/libstdc++-v3/libsupc++/.libs -L/Storage2/gcc-3.2.3-bld2/gcc -L/usr/local/lib/gcc-lib/m68k-next-nextstep3/3.2.3 -L/usr/local/lib/gcc-lib/m68k-next-nextstep3/3.2.3/../../.. abi_check.o -lsupc++ -lstdc++ -lm -lgcc -lsys_s -lgcc -lcrtend.o I am now trying to identify which gcc or libstdc++ configuration files need to be modified to automatically link libsupc++ whenever g++ is run, as Jonathan earlier suggested should be happening. Thank you. On 2012-03-19, at 11:53 AM, Jonathan Wakely wrote: > On 19 March 2012 15:39, Vaugha Brewchuk wrote: >> I have a quick update. I was able to find an issue with the way my gcc configuration was using crtstuff.c. After I corrected it I can now successfully link abi_check with a manual command! >> >> What configuration or setup file determines automatic linking of libsupc++? I would like to fix it such that no manual intervention is required. > > It would be a lot easier to answer if you showed the exact command you > used when it did link successfully.
