+- Forums (https://www.vdrift.net/Forum)
+-- Forum: Community (https://www.vdrift.net/Forum/forumdisplay.php?fid=3)
+--- Forum: Help (https://www.vdrift.net/Forum/forumdisplay.php?fid=5)
+--- Thread: Need help (/showthread.php?tid=544)
Pages:
1
2
- thelusiv - 03-21-2007
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 scons.py. 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
)
- rockin_XJ - 03-24-2007
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/include/SDL/SDL_net.h
/usr/lib64/libSDL_net-1.2.so.0
/usr/lib64/libSDL_net-1.2.so.0.0.5
/usr/lib64/libSDL_net.a
/usr/lib64/libSDL_net.la
/usr/lib64/libSDL_net.so :x
Does anybody else have vdrift installed on Suse 10.1 or is it just not possible?
Please Help
- thelusiv - 03-25-2007
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.
The short answer is, I'll try to have a 64-bit package together soon. I'll keep you posted on the progress.