[Fwd: [JEDI-SDL] SDL, Kylix and Debian testing]

HI All,
I am forwarding this message from the JEDI-SDL mailing list. Can
anyone shed some light on what needs to be done to get this working?> ----- Original Message -----

Debian has decided that usage of SDL libraries requires linking to the
static
XFree86 libraries. IOW, the output of ‘sdl-config --libs’. When I run that
command, I get:

-L/usr/lib -lSDL -lpthread -L/usr/X11R6/lib -lXxf86dga -lXxf86vm -lXv

Although my projects compile fine, when I attempt to execute them, I get an
undefined symbol error:

ApplName: relocation error: /usr/lib/libSDL-1.2.so.0: undefined symbol:
XF86VidModeQueryExtension

What switches or changes to I have to make in Kylix to fix this problem?

Logan Bear

P.S. Even though this is Debian testing, Debian will not change the SDL
libraries, since the current change fixes problems with SDL on many non-i386
platforms.

Thanks,

Dominique Louis
http://www.DelphiGamer.com := for all your Object Pascal game
development needs;

Arghh!! Why can’t Linux stuff just freaking work???

Okay, first make sure that the XF86VidModeQueryExtension call actually
exists in the Xv library. Second, make sure that the dynamic linker
actually loads it as a dependency for the program. Third, make sure
that it’s not a problem specific to JEDI programs - i.e. do the test
programs in the SDL source archive work? Fourth, see if uninstalling
whatever debian SDL package is installed and then and installing SDL
from source fixes the problem. Fifth, head down to the pub and get snockered.

Bloddy Linux distributions.
Freaking FAQ getting cluttered with hack workarounds for broken tools.
mutter mutter ignore me. :slight_smile:

-Sam Lantinga, Software Engineer, Blizzard Entertainment> -------- Original Message --------

Debian has decided that usage of SDL libraries requires linking to the
static
XFree86 libraries. IOW, the output of ‘sdl-config --libs’. When I run that
command, I get:

-L/usr/lib -lSDL -lpthread -L/usr/X11R6/lib -lXxf86dga -lXxf86vm -lXv

Although my projects compile fine, when I attempt to execute them, I get an
undefined symbol error:

ApplName: relocation error: /usr/lib/libSDL-1.2.so.0: undefined symbol:
XF86VidModeQueryExtension

In my experience with debian (especially debian unstable), it’s really best just
to remove all SDL packages and install SDL from source, making sure to properly
compile it with more sane flags :slight_smile:

-EvilTypeGuyOn Fri, Oct 26, 2001 at 07:25:04AM -0700, Sam Lantinga wrote:

-------- Original Message --------
Debian has decided that usage of SDL libraries requires linking to the
static
XFree86 libraries. IOW, the output of ‘sdl-config --libs’. When I run that
command, I get:

-L/usr/lib -lSDL -lpthread -L/usr/X11R6/lib -lXxf86dga -lXxf86vm -lXv

Although my projects compile fine, when I attempt to execute them, I get an
undefined symbol error:

ApplName: relocation error: /usr/lib/libSDL-1.2.so.0: undefined symbol:
XF86VidModeQueryExtension

Arghh!! Why can’t Linux stuff just freaking work???

Okay, first make sure that the XF86VidModeQueryExtension call actually
exists in the Xv library. Second, make sure that the dynamic linker
actually loads it as a dependency for the program. Third, make sure
that it’s not a problem specific to JEDI programs - i.e. do the test
programs in the SDL source archive work? Fourth, see if uninstalling
whatever debian SDL package is installed and then and installing SDL
from source fixes the problem. Fifth, head down to the pub and get snockered.

Bloddy Linux distributions.
Freaking FAQ getting cluttered with hack workarounds for broken tools.
mutter mutter ignore me. :slight_smile:

-Sam Lantinga, Software Engineer, Blizzard Entertainment

Thanks Sam and EvilTypeGuy,
I will forward these on .

Thanks,

Dominique.

Sam Lantinga wrote:>>-------- Original Message --------

Debian has decided that usage of SDL libraries requires linking to the
static
XFree86 libraries. IOW, the output of ‘sdl-config --libs’. When I run that
command, I get:

-L/usr/lib -lSDL -lpthread -L/usr/X11R6/lib -lXxf86dga -lXxf86vm -lXv

Although my projects compile fine, when I attempt to execute them, I get an
undefined symbol error:

ApplName: relocation error: /usr/lib/libSDL-1.2.so.0: undefined symbol:
XF86VidModeQueryExtension

Arghh!! Why can’t Linux stuff just freaking work???

Okay, first make sure that the XF86VidModeQueryExtension call actually
exists in the Xv library. Second, make sure that the dynamic linker
actually loads it as a dependency for the program. Third, make sure
that it’s not a problem specific to JEDI programs - i.e. do the test
programs in the SDL source archive work? Fourth, see if uninstalling
whatever debian SDL package is installed and then and installing SDL
from source fixes the problem. Fifth, head down to the pub and get snockered.

Bloddy Linux distributions.
Freaking FAQ getting cluttered with hack workarounds for broken tools.
mutter mutter ignore me. :slight_smile:

-Sam Lantinga, Software Engineer, Blizzard Entertainment


SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl

Debian has decided that usage of SDL libraries requires linking to
the static
XFree86 libraries. IOW, the output of ‘sdl-config --libs’. When I
run that command, I get:

-L/usr/lib -lSDL -lpthread -L/usr/X11R6/lib -lXxf86dga -lXxf86vm -lXv

Although my projects compile fine, when I attempt to execute them, I
get an undefined symbol error:

ApplName: relocation error: /usr/lib/libSDL-1.2.so.0: undefined
symbol: XF86VidModeQueryExtension

Arghh!! Why can’t Linux stuff just freaking work???

VVVFAQ indeed - and still no solution. heh

Okay, first make sure that the XF86VidModeQueryExtension call actually
exists in the Xv library. Second, make sure that the dynamic linker
actually loads it as a dependency for the program. Third, make sure
that it’s not a problem specific to JEDI programs - i.e. do the test
programs in the SDL source archive work? Fourth, see if uninstalling
whatever debian SDL package is installed and then and installing SDL
from source fixes the problem.

I might add that after upgrading my system to the latest automake and
autoconf, I had to run ‘aclocal’ (that’s all, IIRC…) on projects using
older autoconf versions, to link with OpenGL. Using the ac scripts from
older autoconf versions won’t work if the system is using one of the
latest versions.

(And no, ./configure or make does not deal with this. I had to spend a
good while tracing the construction of the link arguments to figure out
why the libGL path silently went missing…)

Fifth, head down to the pub and get snockered.

That’s a good one! Maybe I should try it some time… :slight_smile:

Bloddy Linux distributions.
Freaking FAQ getting cluttered with hack workarounds for broken tools.
mutter mutter ignore me. :slight_smile:

Great fun with new cool versions, isn’t it!? :wink:

//David Olofson — Programmer, Reologica Instruments AB

.- M A I A -------------------------------------------------.
| Multimedia Application Integration Architecture |
| A Free/Open Source Plugin API for Professional Multimedia |
----------------------------> http://www.linuxdj.com/maia -' .- David Olofson -------------------------------------------. | Audio Hacker - Open Source Advocate - Singer - Songwriter |-------------------------------------> http://olofson.net -'On Friday 26 October 2001 16:25, Sam Lantinga wrote:

-------- Original Message --------

Fifth, head down to the pub and get snockered.

Bloddy Linux distributions.
Freaking FAQ getting cluttered with hack workarounds for broken tools.
mutter mutter ignore me. :slight_smile:

Aaahahahaaaa…

Wooboy, Sam’s flipped his lid.

–ryan.