Hey guys, I’ve got a slight problem with building SDL 1.2.2 – not sure if
this has been covered in the past as the FAQs list nothing about it, and I
couldn’t find any mention of a similar issue in the list archives.
Basicially, I’m able to compile the actual libraries without a problem.
Thing is, when I go to compile against them, I get an unresolved symbol
error with libasound.so (exact error is: “/usr/lib/libasound.so.1: undefend
reference to `atexit’”). I realize that this library is used with the ALSA
sound system and is really an issue with it, but when I attempt to configure
SDL with the --disable-alsa flag or the --with-alsa=no flags, it still
builds and links against ALSA and I still end up with the aforementioned
unresolved symbol.
My question is this: is the source configuration system broken or am I just
doing something wrong here? What can I do to prevent SDL from compiling with
ALSA?–
Thomas “Mondoshawan” Tate
phoenix at psy.ed.asu.edu
http://tank.dyndns.org
-------------- next part --------------
A non-text attachment was scrubbed…
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: http://lists.libsdl.org/pipermail/sdl-libsdl.org/attachments/20011016/1bef75ae/attachment.pgp
After some digging, I found out what the issue is – turns out that glibc
versions 2.2.2 to 2.2.3 have a problem where the atexit symbol has been
moved from the standard libc.so.6 file to an external file by the name of
libc_nonshared.a. It has been confirmed (the guys at KDE had to deal with
this little annoying bug) that 2.2.4 does not have this issue.
I, for one, am going to see about upgrading to 2.2.4. Might want to post the
above into the FAQ just for reference – finding information regarding this
annoying little issue was quite difficult.On Tue, Oct 16, 2001 at 02:53:15PM -0700, Thomas Mondoshawan Tate wrote:
Hey guys, I’ve got a slight problem with building SDL 1.2.2 – not sure if
this has been covered in the past as the FAQs list nothing about it, and I
couldn’t find any mention of a similar issue in the list archives.
Basicially, I’m able to compile the actual libraries without a problem.
Thing is, when I go to compile against them, I get an unresolved symbol
error with libasound.so (exact error is: “/usr/lib/libasound.so.1: undefend
reference to `atexit’”). I realize that this library is used with the ALSA
sound system and is really an issue with it, but when I attempt to configure
SDL with the --disable-alsa flag or the --with-alsa=no flags, it still
builds and links against ALSA and I still end up with the aforementioned
unresolved symbol.
My question is this: is the source configuration system broken or am I just
doing something wrong here? What can I do to prevent SDL from compiling with
ALSA?
–
Thomas “Mondoshawan” Tate
phoenix at psy.ed.asu.edu
http://tank.dyndns.org
-------------- next part --------------
A non-text attachment was scrubbed…
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: http://lists.libsdl.org/pipermail/sdl-libsdl.org/attachments/20011016/05214ad6/attachment.pgp