Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Need help
03-21-2007, 12:52 PM,
The "sh: o: not found" problem is from not having a compiler installed. I guess I should make SCons check for that...Also, you should be able to get by with just Are you still using the source release from 10-6? You should probably be compiling from SVN now, as what's in there is the current release that is about to come out as soon as I finish writing the release notes (I wrote them the other day and then forgot to save them...and accidentally closed my text editor Sad )
03-24-2007, 09:14 PM,
Well, I waited for the new version to come out, and I download it and the autopackage installer starts working, and I'm thinking finally this things going to work, but I got this message in the dialog box:

Checking for required C library versions ... OK
Checking for X ... OK
Checking for OpenGL Graphics Toolkit ... OK
Checking for OpenGL Utility Library ... OK
Checking for Simple DirectMedia Layer (SDL) ... OK
Checking for SDL Image Library ... OK
Checking for required C library versions ... OK
Checking for Simple DirectMedia Layer Mixer (SDL_mixer) ... OK
Checking for SDL Network Library ... failed
Error: Could not find 'SDL Network Library'. Try using the native package manager for SUSE Linux (yast) to install a package with similar name to 'sdl_net'.

Error: Unable to prepare package VDrift.

The sdl_net files are installed on my system they reside here:

/usr/lib64/ :x

Does anybody else have vdrift installed on Suse 10.1 or is it just not possible?
Please Help
03-25-2007, 02:48 AM,
I have been talking to the autopackage developers about 64-bit support and basically autopackage is untested on that platform. I built a package on my 64-bit machine where I'm running all 64-bit libs and the result was that it failed to find most of the libraries, because of the problems like yours - the libs are in a different place (lib64 instead of lib) and thus the autopackage skeleton system can't find them. I may be able to come up with a way to use manual library checks to find the libs instead of the skeleton system; unfortunately this has some drawbacks like all the messages will only be in English, it will not take advantage of autopackage's very extensive translations. Anyway the 32-bit version will probably not run properly on a system with all 64-bit libraries.

That's the long answer. Smile The short answer is, I'll try to have a 64-bit package together soon. I'll keep you posted on the progress.

Forum Jump:

Users browsing this thread: 1 Guest(s)