Consider the a.cpp, b.cpp attached in this email. I can compile the code using > g++ a.cpp b.cpp However, I am unable to compile it when -m64 option is used. > g++ a.cpp b.cpp -m64 /var/tmp//ccJd8iNV.o(.eh_frame+0x40): relocation truncated to fit: R_SPARC_DISP32 .gnu.linkonce.t._ZNSt6vectorISsSaISsEEC1Ev collect2: ld returned 1 exit status g++ -v gives (system specific paths are munged for security) Using built-in specs. Target: sparc-sun-solaris2.8 Configured with: <munge1>/software/unZipped/gcc-4.4-wkly_gmp-4.2.4_mpfr-2.4.0/configure --enable-languages=c,c++,fortran --with-as=<munge2>/bin/as --with-ld=<munge2>/bin/ld --with-build-time-tools=<munge2>/bin --prefix=<munge1>/software/myroot/gcc-4.4-20090123 : (reconfigured) <munge1>/software/unZipped/gcc-4.4-wkly_gmp-4.2.4_mpfr-2.4.0/configure --enable-languages=c,c++,fortran --with-as=<munge2>/bin/as --with-ld=<munge2>/bin/ld --with-build-time-tools=<munge2>/bin --prefix=<munge1>/software/myroot/gcc-4.4-20090123 Thread model: posix gcc version 4.4.0 20090206 (experimental) (GCC) Is this a bug or am I doing something crazy in the code?
Attachment:
a.cpp
Description: Binary data
Attachment:
b.cpp
Description: Binary data
