Hello!
I’m wondering which version of glibc is really
required for native Linux compilation of SDL
applications. When installing the SDL rpms
(i tried both 1.1.2 and 1.0.8 +devels of course)
the dependencies claims that both glibc2.0 and
2.1 are required. I’m using libc6.0.7 on Debian
(which is supposed to be the stable version)
and when configuring the demos (warp, water,
plasma) i get an error during ./configure
that it can’t run the SDL >= 1.0.1 test.
When looking at config.log, a lot of
symbols are not found in both glibc2.0
and glibc2.1. When upgrading to
libc6_2.1.3-8 the complaints about
undefined symbols disappears in config.lon,
but the SDL >= 1.0.1 test during configure
still does not run, and ldconfig starts to complain
that it can’t find libraries such as libm, libpthread
etc. - which sounds like a disaster…
So I think I’ll downgrade back to libc6.0.7
Any hints?
BTW - I seem to be able to crosscompile
the demos to Win32 just fine! 
(except for the {prefix} issue in the generated
Makefile as mentioned earlier)
Cheers–
http://www.HardcoreProcessing.com
Hello !
I think you could give in the directory where the SDK resides.
Give in a ./configure --help
Which should give you more infromation!
Hope this helps!
Regards
ANOQ of the Sun wrote:
I’m using libc6.0.7 on Debian
(which is supposed to be the stable version)
…
Actually I was using libc6_2.1.3-7 (apparently)
while also using libc6-dev_2.0.7… and there
were some incompatiple versions of libstdc++ too…
So it was just my system which was messed up
as usual… sorry.
But now I can recommend these packages on
Debian (even though you’re otherwise using stable):
libc6_2.1.3-8
libc6-dev_2.1.3-8
libstdc++2.10_2.95.2-8
libstdc++2.10-dev_2.95.2-8
I also upgraded to:
ldso_1.9.11-7
Now I can configure the demos both
for linux native and linux->win32 cross
compilation.
But… when running make afterwards I now get this:
cd . && aclocal
make: @SHELL@: Command not found
make: *** [aclocal.m4] Error 127
Does anybody know what this is about?
I’ve never seen && used on a cd command…
Anes Lihovac wrote:
I think you could give in the directory where the SDK resides.
Give in a ./configure --help
Which should give you more infromation!
I’ve tried this now, and I can’t find anything which helps…
But thanks!
Cheers–
http://www.HardcoreProcessing.com
ANOQ of the Sun wrote:
But… when running make afterwards I now get this:
cd . && aclocal
make: @SHELL@: Command not found
make: *** [aclocal.m4] Error 127
OK, this just happened when using the configure
that I created myself by running autoconf - but
I don’t know how to use autoconf anyways, so
using the configure script from the original
distribution - everything works just perfect!
So I guess I will try to be really quitet now
Cheers–
http://www.HardcoreProcessing.com