On Mon, Apr 6, 2009 at 7:13 PM, Ian Lance Taylor <iant@xxxxxxxxxx> wrote: > kamaraju kusumanchi <raju.mailinglists@xxxxxxxxx> writes: > >> This g++ 4.4.0 20090206 is compiled with GNU ld 2.14 20030612. > > 2.14 is fairly old. > > >>> g++ -m64 -B<munge1>/software/myroot/binutils-2.19.1/bin -L<munge1>/software/myroot/binutils-2.19.1/lib a.cpp b.cpp >> /var/tmp//cc4Tw4B3.o(.eh_frame+0x40): relocation truncated to fit: >> R_SPARC_DISP32 .gnu.linkonce.t._ZNSt6vectorISsSaISsEEC1Ev >> collect2: ld returned 1 exit status >> >> >> BTW, is the -B option correct way to specify the location of the linker? > > Yes, that should work. You can confirm by using -Wl,-debug and making > sure that it does indeed run your newly installed linker. > > Ian > Very weird. Even after specifying the new linker using -B, -L options, the g++ is still linking the object files with the old linker. I used the following command. g++ -v -B<munge1>/software/myroot/binutils-2.19.1/bin -L<munge1>/software/myroot/binutils-2.19.1/lib -Wl,-debug a.cpp b.cpp > link.txt 2>&1 The output (link.txt.mng) is attached. Any idea why this could be happening? raju
Attachment:
link.txt.mng
Description: Binary data
