Sam Steingold wrote: > Package: libffcall1 > Version: 1.10+2.41-3 > > on dual-arch systems, specifically, on sparc (but possibly others), > libavcall.so and libcallback.so are distributed in a 32-bit variant, not > 64-bit variant: > /usr/lib/libavcall.so.0.0.0: ELF 32-bit MSB shared object, SPARC, > version 1 (SYSV), dynamically linked, stripped
64bit libraries and applications are *slow* on sparc and rarely needed. You know that to build a library in 64bit you need all build-dependencies being available in 64bit, too? > this makes the library useless for 64-bit applications because configure > cannot find it (it looks in /usr/lib64). > moreover, even if it did find the library, it is dubious that it would > work properly. configure should not find it. > Suggested resolution: > the bottom line is that the files /usr/lib64/libavcall.* and > /usr/lib64/libcallback.* are missing. > thus I see 3 ways to solve the problem: > > 1. build the llibffcall1 package like this: > ./configure && make && make check && make install && make distclean && > ./configure CC='gcc -m64' && make && make check && make install > i.e., include both 32-bit libraries and 64-bit libraries in one package. not possible, that would pull in all needed 64bit libs when installing the package, also it would violate the policy. > 2. build the llibffcall1 package like this: > ./configure CC='gcc -m64' && make && make check && make install > i.e., replace the 32-bit libraries with the 64-bit libraries. OUCH OUCH OUCH. You know that something like that would break a *ton* of packages? > 3. replace llibffcall1 with 2 packages: llibffcall1-32 and llibffcall1-64. no. Building lib64ffcall1 is the only option here, but I can't see the sense in it. -- Bernd Zeimetz Debian GNU/Linux Developer GPG Fingerprint: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
