I'm sending a small README update with instructions to build for power. yours faithfully,
-- Jose Flavio Aguilar Paulino ([EMAIL PROTECTED]) System / Software Engineer Toolchain Team LTC, Linux Technology Center IBM Brazil
Index: libunwindTest2/libunwind/README =================================================================== --- libunwindTest2.orig/libunwind/README +++ libunwindTest2/libunwind/README @@ -49,6 +49,24 @@ libunwind should be configured and insta Caveat: Unwinding of 32-bit (ILP32) binaries is not supported at the moment. +* Building for PowerPC64 / Linux + +For building for power64 you should use: + + $ ./configure CFLAGS="-g -O2 -m64" CXXFLAGS="-g -O2 -m64" + +If your power support altivec registers: + $ ./configure CFLAGS="-g -O2 -m64 -maltivec" CXXFLAGS="-g -O2 -m64 -maltivec" + +To check if your processor has support for vector registers (altivec): + cat /proc/cpuinfo | grep altivec +and should have something like this: + cpu : PPC970, altivec supported + +If libunwind seens to not work (backtracing failing), try to compile it with -O0, +without optimizations. There are some compiler problems depending on the version +of your gcc. + ** Workaround for older versions of GCC GCC v3.0 and GCC v3.2 ship with a bad version of sys/types.h. The
Index: libunwindTest2/libunwind/README =================================================================== --- libunwindTest2.orig/libunwind/README +++ libunwindTest2/libunwind/README @@ -49,6 +49,24 @@ libunwind should be configured and insta Caveat: Unwinding of 32-bit (ILP32) binaries is not supported at the moment. +* Building for PowerPC64 / Linux + +For building for power64 you should use: + + $ ./configure CFLAGS="-g -O2 -m64" CXXFLAGS="-g -O2 -m64" + +If your power support altivec registers: + $ ./configure CFLAGS="-g -O2 -m64 -maltivec" CXXFLAGS="-g -O2 -m64 -maltivec" + +To check if your processor has support for vector registers (altivec): + cat /proc/cpuinfo | grep altivec +and should have something like this: + cpu : PPC970, altivec supported + +If libunwind seens to not work (backtracing failing), try to compile it with -O0, +without optimizations. There are some compiler problems depending on the version +of your gcc. + ** Workaround for older versions of GCC GCC v3.0 and GCC v3.2 ship with a bad version of sys/types.h. The
_______________________________________________ Libunwind-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/libunwind-devel
