> I do know know why the linker can not find libSDL. Perhaps it is
> because the -L option from `sdl-config --libs` is not correct somehow.
>
> What happens if you do this instead:
>
> gcc test.cc `sdl-config --libs`
This works fine. Also, executing
sdl-config --libs
yields
-L/usr/lib -Wl,-rpath,/usr/lib -lSDL -lpthread
which is correct for my setup.
> What does the failed linking command look like? Maybe seeing the
> failed command will provide a clue about what is not working.
Here it is:
[EMAIL PROTECTED] lavtools]$ make
/bin/sh ../libtool --mode=link gcc -mcpu=i686 -march=i686 -march=athlon
-pipe -O2 -ffast-math -fomit-frame-pointer -s -Wall -Wunused -s -o
lavplay lavplay.o ../utils/libmjpegutils.a liblavplay.la liblavjpeg.la
liblavfile.la -lpthread -L/usr/lib -Wl,-rpath,/usr/lib -lSDL -lpthread
-L/usr/X11R6/lib -lX11
libtool: link: cannot find the library `'
I don't know why it fails to tell me which library it can't find, but I
found out that it is the SDL library. Removing the '-lSDL' part of the
command allows the linker to start doing it's job. It fails of course,
because of the missing references to SDL symbols.
Cheers,
Dik
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users
