Crystal Space
Welcome, Guest. Please login or register.
November 20, 2017, 02:56:12 am

Login with username, password and session length
Search:     Advanced search
9081 Posts in 2051 Topics by 80488 Members
Latest Member: Ertopqwe
* Home Help Search Login Register
+  Crystal Space
|-+  Crystal Space Development
| |-+  General Crystal Space Discussion
| | |-+  Cannot use latest psudo-release on linux (fedora core 4)
« previous next »
Pages: [1] Print
Author Topic: Cannot use latest psudo-release on linux (fedora core 4)  (Read 3044 times)

« on: September 21, 2005, 08:11:05 am »

I've tried several times, but while it compiles with only  warnings (about non-virtual destructors on pure virtual structs) it will not run any of the applications.

I untar the source, then

./configure --prefix=/opt/crystalspace --enable-new-renderer --enable-debug
jam all
make install

export CRYSTAL=/opt/crystalspace

And try to run the walktest from /opt/crystalspace/bin but I get this error on anything I try...

/opt/crystalspace/bin/walktest flarge
WARNING: could not load plugin 'crystalspace.graphics2d.glx'
Error loading Graphics2D plugin.
WARNING: failed to initialize plugin 'crystalspace.graphics3d.opengl'
ERROR: Console: Unable to locate 3D renderer plugin!
WARNING: failed to initialize plugin 'crystalspace.console.output.simple'
No 3D driver!

  World saving enabled.
crystalspace.system:  No iGraphics3D plugin!
crystalspace.system:  Error initializing system!
Cleaning up...

Can anyone explain what I'm doing wrong?
Full Member
Posts: 101

View Profile
« Reply #1 on: September 21, 2005, 08:33:49 am »

which compiler do you use? gcc 3.4.4 works fine, gcc 4.0 is said to be evil with CS

Gentoo Linux ~x86, kernel 2.6.11-cko9 smp, gcc 3.4.4-r1, binutils 2.16.1, glibc 2.3.5 NPTL
CS+CEL Pseudo Stable 2005.09.03
Sr. Member
Posts: 295

View Profile
« Reply #2 on: September 21, 2005, 10:03:46 am »

The gcc 4.x 'virtual destructor' warnings should be harmless. We haven't yet come up with a good, general-purpose solution to that problem.

gcc 4.0.x is buggy and generates bogus code which causes CS to crash. gcc 4.1.x is said to fix the crasher.

You don't need the --enable-new-renderer option. The old renderer was dropped after the 0.98 release, so the new renderer is now the default.

From the output of your program run, I'm guessing that the X-windows canvas (CS/plugins/video/canvas/softx) did not get built, which might mean that the CS configure script did not find X-windows. Look in the generated Jamconfig file at the root of your build directory and see if it contains a line 'X11.AVAILABLE=yes'. If it does not, consult config.log to see why the X11 check failed.
Pages: [1] Print 
« previous next »
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.2 | SMF © 2006-2007, Simple Machines LLC Valid XHTML 1.0! Valid CSS!
Page created in 5.159 seconds with 16 queries.