Celestia Forums

Hi
I have a prolem to build celestia for Linux
I run configure successfully,
than I run make and I get an Error.

Here my output:



Help me please!
Thx

I can tell you what happens but not (yet) why it does!

In the source directory src/celengine, where 3dsmesh.cpp is located,
there are also the /local/ GL header files gl.h and glext.h. These
have the same names as the systems headers in /usr/include/GL, but are
meant to be read /first/. Apparently this works
incorrectly in your case but works fine with the majority of users.

1) Please do the following: go to src/celengine. Add a -v in
CXXFLAGS = -O2 -Wall ... that you find in the Makefile. Save and
type 'make' from the same directory. You should get a detailed list
of the actual include search path of your compiler as well as other
info which you did not give before. Show me the output.

2) Examine again carefully the ./configure output whether you did
not overlook some warnings etc.

3) You should use some recent versions of autoconf, automake
packages. At least: autoconf-2.52, automake-1.4_p5.

4) Please specify name and version of your Linux distribution, graphics card.

Bye Fridger

1)


2)



3)
I have autoconf-2.52, automake-1.4_p5

4) I am using SuSE 7.3 and a Voodoo 3

PS: Wir k?nnen auch deutsch mit einander sprechen.

It is better to use English, since others had or might have a similar problem in the future. They may not be able to understand German...

Judging from your directory structure, I suspected already that you are using SuSE. Fortunately, your setup is identical to mine, except for the graphics card (which drivers are you using, by the way!?).

I compared your output line by line with mine. While your ./configure
run indeed looks perfect, your include path sequence does not agree with mine, which may well be related to your problem:

Your compiler does not run through

/usr/include/orbit-1.0

and looks into /usr/include
instead. This may be too early..

Visiting of the standard header dir /usr/include should happen last.

From your configure output, it looks however that you did not forget to
install 'orbit-devel', containing the above headers that the compiler
did not find. Please control again, whether you installed all *-devel
packages (headers!) of the needed libraries!

From which package are your glx headers in /usr/include/GL?
You find this out by typing in this dir

rpm -qf *.h

Also, is this the first program with openGL hardware support that you are trying to compile yourself on your installation??

Are you sure that your hardware support works? What fps does
'glxgears' quote?

Show me your output from glxinfo...

Honestly, without examining your system in detail, it looks like a
mere question of luck to find out the solution to your problem...

Bye Fridger

Erst mal vielen Danke f?r deine M?he!


I do not have a dir named:
/usr/include/orbit-1.0
but i have a dir called:
/usr/include/orb


package for glx headers in /usr/include/GL:



glxgears



glxinfo:

Now this /is/ revealing! You have NO hardware openGL support (direct
rendering = NO) and your installation is quite messed up. First of all, you should correctly configure your system for hardware openGL support of your Vodoo3 card. You find the instructions with SuSE or use SAX2. Presently, you have /Software rendering/ activated using Mesa-3.4.2. The fps rates of glxgears are correspondingly low. I have 2592 fps, for example...

Next, and this is probably the reason for your problem, you installed /both/ the mesa-devel and the xf86glx-devel packages the headers of which are conflicting! This is explicitly said in the package notes and in the SDB at SUSE. Moreover, there are further headers from glx-devel-010330-85. What is this??

You probably did not install orbit-devel either. Simply check the files in the package with

rpm -ql orbit-devel|less

Look for the headers.

Your glxinfo should look somehow like this, of course with NVIDIA etc appropriately replaced.

name of display: :0.0
display: :0 screen: 0
direct rendering: Yes <=======
server glx vendor string: NVIDIA Corporation
server glx version string: 1.2
server glx extensions:
client glx vendor string: NVIDIA Corporation
client glx version string: 1.2
client glx extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_visual_info,
GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_SGI_video_sync,
GLX_SGIX_swap_group, GLX_SGIX_swap_barrier
GLX extensions:
OpenGL vendor string: NVIDIA Corporation <===============
OpenGL renderer string: GeForce2 GTS/AGP/SSE <================
OpenGL version string: 1.2.2


So, you first have to clean-up your Linux installation thoroughly...

Bye Fridger

Here my new Output form glxinfo:

I test it wiht glxgears but i get only 75 fps!

rpm -ql orbit-devel|less :

Well, at least you now got direct rendering. I cannot go from here through your whole system to find out where the installation is broken. You must /very/ carefully follow the instructions of the 3d driver installation for your card, since there are several places where conflicting file names and wrong symbolic links may destroy everything!

In general, it cannot be the purpose of this Celestia forum to fix people's messed-up Linux installations (within 2 days I am currently dealing with 3 such cases simultaneously...).

Sorry & good luck

Bye Fridger

Again the Box forgot my user name over a telephone call...
----------------------------------


Well, at least you now got direct rendering. I cannot go from here
through your whole system to find out where the installation is
broken. You must /very/ carefully follow the instructions of the 3d
driver installation for your card, since there are several places where conflicting file names and wrong symbolic links may destroy everything!
The important file to inspect is the output log from your X-server.

In general, however, it cannot be the purpose of this Celestia forum to fix
people's messed-up Linux installations (within 2 days I am currently
dealing with 3 such cases simultaneously...).

Sorry & good luck

Bye Fridger

Thanks for your help

Messed-up Linux installations is a good description.

Anonymous wrote:Thanks for your help

Messed-up Linux installations is a good description.
:D

In order to make progress, you have to deinstall first the 3 partly conflicting packages:

mesa-devel
xf86glx-devel
glx-devel

If according to SusE, glx-devel belongs to the driver packs you need for you graphics card, try just to get along with it alone.

Certainly, you cannot install all three at once, since then part of the glx headers are from one package others from another. This is bound to create a "Big Bang";-)

Bye Fridger

You may simply convince yourself that the 3 packages contain partly the same header names as follows:

After downloading the three packs into your home dir, examine their file content with

rpm -pql <package>.rpm

I now have install celestia with an rpm paket
and it runs
but it ist very slow! ( < 1fps )
is that normal?

Hi,

no hardware accel yet,
Axel

Hmmm,

I figure you're not the same 'anonymous' from the start of the thread, right?

Then please follow Fridger's suggestions by doing:

If you've got SUSE >7.2 plaese use the 'You' online update util. this will detect any outdated rpms when connected to the internet and try to down them from ftp.suse.com.
(Because of copyright issues no hardware accelerated 3D drivers are included with Suse/linux.)
So 'You' will grasp there's e.g. an old nVidia driver on the system and then download the new from ftp.nvidia.com. Afterwards it'll install and ask for reboot.
The next time Celestia ought to run accelerated.

If you own something else try to down the proper driver from nVidia's website and install it themselve.

Take care and good luck,
Axel