[Bug 160] New: Build fails on Fedora Core 4 on x86_64 due to libtool problem

http://sablevm.org/bugs/show_bug.cgi?id=160

           Summary: Build fails on Fedora Core 4 on x86_64 due to libtool
                    problem
           Product: SableVM
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P2
         Component: default
        AssignedTo: [email protected]
        ReportedBy: [email protected]
         QAContact: [email protected]


When I try to build SableVM SDK 1.13-pre1 on Fedora Core 4 on x86_64, the build
fails with the following error message, caused by libtool improperly
substituting /usr/lib/libpopt.so (which is 32-bit) for -lpopt.

/bin/sh ../../libtool --tag=CC --mode=link gcc  -g -O2 -Wall -fno-gcse
-fno-strict-aliasing   -o libsablevm.la -rpath /usr/local/lib -release
trunk+4699  libsablevm.lo -lm -lltdl -lz -lpthread
../libffi/libffi_convenience.la -lpopt
gcc -shared  .libs/libsablevm.o -Wl,--whole-archive
../libffi/.libs/libffi_convenience.a -Wl,--no-whole-archive  -lm -lltdl -lz
-lpthread /usr/lib/libpopt.so  -Wl,-soname -Wl,libsablevm-trunk+4699.so -o
.libs/libsablevm-trunk+4699.so
/usr/lib/libpopt.so: could not read symbols: File in wrong format
collect2: ld returned 1 exit status
make[6]: *** [libsablevm.la] Error 1
make[6]: Leaving directory `/r/src/sablevm-sdk-1.13-pre1/sablevm/src/libsablevm'
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory `/r/src/sablevm-sdk-1.13-pre1/sablevm/src/libsablevm'
make[4]: *** [all] Error 2
make[4]: Leaving directory `/r/src/sablevm-sdk-1.13-pre1/sablevm/src/libsablevm'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/r/src/sablevm-sdk-1.13-pre1/sablevm/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/r/src/sablevm-sdk-1.13-pre1/sablevm'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/r/src/sablevm-sdk-1.13-pre1/sablevm'
make: *** [build-main] Error 1



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.