I was wondering what you made of this. I noticed that
the libasound2_0.9.0rc6-1_powerpc.deb package had a
libasound.so.2.0.0 which caused alsactl to fail with the
./alsactl: error while loading shared libraries: /usr/lib/libasound.so.2: R_PPC_REL24 relocation at 0x0ff92ff0 for symbol `m_info_is_volatile' out of range
if I do...
objdump -R ./libasound.so.2.0.0 | grep R_PPC_REL24
0008fff0 R_PPC_REL24 abort
for the package built on voltaire with gcc 2.95.4. I also get that
on my machine if I use gcc 2.95.4. However if I use gcc 3.2.2 instead
to build this package locally I get...
objdump -R ./libasound.so.2.0.0 | grep abort
000ac48c R_PPC_JMP_SLOT abort
with no symbols at all being R_PPC_REL24. I am told that R_PPC_REL24
suggests not building with -fPIC but I don't see any obvious case
of that with the gcc 2.95 build of libasound2. Guess just one more
reason why we should be moving to gcc 3.2 asap. Oh, the libasound2
built with gcc 3.2.2 runs alsactl without problems.