hi,
well, one of your libs ( made with some efforts ) seems actually unloadable at all and that's not really related to PiDiP....
hum, lame and vorbis should go along well... actually they do here.
maybe cleanup libs you get with 'ldd pidip.pd_linux' and reinstall all from sources?
cheers, sevy
ben@ekran.org wrote:
I finally got PiDiP compiled. It took 5 hours today. The real problem was SUSE Rpm's not having the right versions of software. (for example aalib 1.2 does not work, but aalib1.4 (latest release candidate for today) does). Also Lame and vorbis don't work very well together. What exact version of everything do I need to be using? I had to comment out an include to modes.h in Lame because it was not part of vorbis (or anything else as far as I can tell).
First I was getting a bunch of unresolved symbols in -lmp3lame Eventually I had to disable vorbis support in lame even to get lame to compile. PiDiP seemed happy about that at the configure stage.
I got it compiled and now I segfault on load:
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 25374)] 0x40009e53 in _dl_relocate_object () from /lib/ld-linux.so.2 (gdb) where #0 0x40009e53 in _dl_relocate_object () from /lib/ld-linux.so.2 #1 0x4015d4e4 in dl_open_worker () from /lib/libc.so.6 #2 0x4000c040 in _dl_catch_error () from /lib/ld-linux.so.2 #3 0x4015d7af in _dl_open () from /lib/libc.so.6 #4 0x40021447 in dlopen_doit () from /lib/libdl.so.2 #5 0x4000c040 in _dl_catch_error () from /lib/ld-linux.so.2 #6 0x40021890 in _dlerror_run () from /lib/libdl.so.2 #7 0x40021486 in dlopen@@GLIBC_2.1 () from /lib/libdl.so.2 #8 0x0809924b in sys_load_lib () Cannot access memory at address 0x2d
Attached is my config.log for PiDiP
Thanks Ben