[farvardin]

hello,

I'm trying to compile mzx (version mzx281csrc.tar.bz2 ) on linux (debian x86 and ppc), but it doesn't work (there are generally no problem for compiling sdl applications there).
I have all SDL dev. libraries, and the one for vorbis too.

All I got is :


****

robo_ed.cpp:(.text+0x3259): r?f?rence ind?finie vers ? XFree ?
collect2: ld returned 1 exit status

make: *** (mzx) Erreur 1

****


I've tried both with gcc 4 and gcc 3.4 and it's the same. What could I do ?

[Dr Lancer-X]

Er, I don't speak that language..whichever it is, but it seems to be a linker error, saying it can't find XFree. Honestly, XFree should be available to you so I don't really get why it isn't. But I don't run anything with X, so I can't really check this. You surely must have the X development libraries or whatever, maybe they're out of date? I dunno.

[RoSS]

It does say that it's an indefinite reference to XFree. If that's the case, you'll probably need XFree86, but I'm no Linux expert. It's a surprise to me that you have SDL (which requires some sort of window manager and graphical libraries). Although honestly, since you're running Debian, your best bet is probably apt-getting XFree.

Keep us informed,
RoSS

(also, moved to Technical Problems)

[Dr Lancer-X]

Er, RoSS, I don't think he needs xfree86. Look at the way the function is used =p

No, it's not a lack of xfree86. Nobody needs that. XFree is just a 'free' function in X11. It's got nothing to do with xfree86. Remember that an undefined reference refers to a FUNCTION, not a whole library. Anyway, install your X11 development stuff (headers and libraries both) and see where that gets you.

[RoSS]

Well I admit I usually don't know what I'm talking about when it comes to Lunix =)

[GetDizzy]

yes, you need the development headers to your X11 libraries.

[LogiCow]

It can't find it because it only has XLib?rer.

This post has been edited by LogiCow: 18 August 2006 - 05:49 PM

[ajs]

If the message wasn't horribly corrupt I think it'd be easy to fix.

Anyway, it is obvious that this is a linker error, and has nothing to do with headers. Newer SDL libraries don't link against X11 explicitly, which leaves undefined symbols in MZX. Linking X11 manually is necessary for clipboard support.

You have two options. Either, if you don't care about the clipboard, edit config.h and remove the line referring to CONFIG_X11, or try this patch:

http://devzero.co.uk...11-linkage.diff

Apply the patch with:

patch -Np0 -i ~/path/to/patch

Then run ./config.sh and make again. Please, other people, don't bug Exophase about this. He's already merged the patch.

--ajs.

[farvardin]

Hello,

thank you very much for the patch, it was exactly what was necessary, it compiled fine with it, and I can play MZX games now !
I'm sorry I couldn't enter more of the error log, the message board didn't like some code in it.

For the others, about xfree, it's much less used now, almost all linux distributions are using xorg instead. Maybe this undefined reference was because of this ?

[ajs]

I explained the reason for the link error. Xorg is binary compatible with XFree, and Xorg symbols still match XFree ones (mostly).

The problem is SDL's decision to no longer link against X11, but instead dlopen() it at runtime.

This was a very welcome change for developers like myself, because it allows SDL to be installed on embedded Linux platforms that have no X server, but still allow for an X11 option if a server is later deployed, or X11 connections are forwarded to another machine.

Unfortunately, since I could not have foreseen this action, MZX was not patched in 2.81c to take notice of it. Hopefully, Exo will do a 2.81d release in the near future that will include the patch.

--ajs.

[Dr Lancer-X]

totally unrelated fun fact-you don't need to use dlopen() or LoadLibrary() to load your shared libs any more! SDL's got a function for that now, too.

[ajs]

Bump, because I've been asked about this three times this week and I'm sick of it.

Sticky anybody?

[T-Bone]

I know this topic is 5 years old but I just had a quick question and didn't want to create a new topic to ask it. Has the issues with MZM files imported robotically still cause problems in Linux? I remember this being mentioned years back, but I couldn't see if it had been resolved.