------- Comment #16 from alex at milivojevic dot org 2006-01-05 21:50 ------- (In reply to comment #15) > It's a build machinery problem.
Actually it is the "configure" script and "libtool" scripts in 99% of open source packages not handling the sparc64 correctly (not handling it at all would be more correct description). This sometimes makes compiling stuff on bi-arch systems a nightmare. One workaround is to use 'LDFLAGS=-R/prefix/lib/sparcv9 ./configure --libdir=/prefix/lib/sparcv9' (however, there might be sideeffects). Gcc is about the only open source thing that I saw so far that handles sparc64 installs as it should. You type one make command, you get both 32-bit and 64-bit libs. You type one make install, you get both libs installed in correct locations (well, except for libiberty ;-). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16507
