Celestia Forums

The configure script just die with this messages:

checking for GL/gl.h... yes
checking for glNewList in -lGL... no
checking for glNewList in -lMesaGL... no
configure: error: GL library was not found

I'm not the sysadm on that system, so I need to know what ask him. I can't believe that on an SGI machine there are no GL libraries.... then I would like to be a little more sure about the nature of the problem, before asking a stupid question.

Have you any hint?

I'm only guessing, but I think from your output that you have GL libraries (at least the gl.h is there), but they haven't the exactly functions Celestia is seeking for (glNewList). Maybe it has the libraries in nonstandard directories, or perhaps they have that function with another name (look in gl.h), and in the last case you will have to modify the source code...

Please post the last part of the config.log file, or send me to jamarsa@yahoo.es

Ok, GL are there, but their version is 1.2.3. Is it a too old version for Celestia?

I think it's enough, albeit you won't have some of the fanciest effects...

The relevant part in your config.log seems to be here:

Somehow it complains about the format of the objects located into the libz library. It needs 'n32', and it finds 'o32'.
I think you should locate another instance of the libz library, or create it yourself
from the source code.

Look at here (Homepage): http://www.gzip.org/zlib/
And here (Irix specific help): http://freeware.sgi.com/Installable/libz-1.1.4.html

Ah!! and, BTW, it seems not to find the glNewList in the GL library, that's why it says:

ld32: WARNING 84 : /usr/lib32/libGL.so is not used for resolving any
symbol.

You still have to look at the gl.h include...

Has anyone got Celestia to compile and run on an IRIX machine?

Maybe you could try to compile some other OpenGL program to see if the problem is with your system or with the Celestia build system.

Hello,

was a no go for me too. However, it appeared to be complaining about the location of the jpeg library rather than OpenGL.

The sys-admin pointed out that it wasn't looking in all the right places for an IRIX machine and recommended:

which worked. The only problem now is getting it to compile:


The sys-admin also pointed out:

There is a problem with OpenGL programs that will only compile under the
gcc/g++ compiler. The problem is that there is no driver for hardware graphics acceleration on SGI under gcc/g++. So OpenGL programs must use the Mesa emulation library, which is very slow if the graphics hardware is not
being used. Normally on an SGI, you would use the system compiler cc/CC to compile with the OpenGL libraries and with hardware graphics acceleration. But that compiler does not allow a lot of the code that gcc/g++ does allow. So the program may not compile at all under cc/CC.

You may need mesa and some kde or gnome libraries, they are not widely used on irix so may not be installed, but are available.

Anyone have any comments on this?

There is a problem with OpenGL programs that will only compile under the
gcc/g++ compiler. The problem is that there is no driver for hardware graphics acceleration on SGI under gcc/g++. So OpenGL programs must use the Mesa emulation library, which is very slow if the graphics hardware is not
being used. Normally on an SGI, you would use the system compiler cc/CC to compile with the OpenGL libraries and with hardware graphics acceleration. But that compiler does not allow a lot of the code that gcc/g++ does allow. So the program may not compile at all under cc/CC.

I think it's not even worth trying to get Celestia to compile with Mesa (i.e. software only OpenGL), you would get something unusable.

The problem probably lies with the fact that there is no standard C++ ABI. Which means that for example you can't use a C++ lib compiled with CC with a program build with g++. The hardware accelerated OpenGL lib under Irix is obviously compiled with CC (and no source available), so you can't link against it unless you use CC as well (and I'm not even mentioning licence issues here.)

So to be able to run Celestia under Irix you need to compile all your 'freeware' C++ libs (plain C is okay) and Celestia with CC. Not a small task probably...

The bright side of things is that there is a standard C++ ABI in the works, in another couple of years it might be possible to mix libraries build with different compilers... that is if propietary unices are still there by that time.

Chris, You mentioned that there are some licence issues, can you elaborate/paste some links?

And, what kind of work needs to be done in order to get Celestia to compile under CC? Is there a way to check if all the other "freeware" apps where compiled with CC too?

How DOES one attempt to compile Celestia with CC? Is it just a matter of changing the Makefile portion:


To: (changes were gcc -> cc and g++ -> CC)

???

Trying to compile with the above changes gives errors in glext.cpp:

abush wrote:Chris, You mentioned that there are some licence issues, can you elaborate/paste some links?

I'm not a licence specialist, but since Celestia is GPL, I don't think you can legaly link it against a proprietary library. And you would need to do that to get hardware accelerated OpenGL. That being said I don't think any of the Celestia developers will take you to court for trying this.

abush wrote:And, what kind of work needs to be done in order to get Celestia to compile under CC? Is there a way to check if all the other "freeware" apps where compiled with CC too?

Since Celestia compiles both with VC++ and various versions of GCC, there is a good chance that only minor modifications are needed to get it to compile with CC.

Getting the GTK/Gnome version is probably feasible since these are C libraries. The KDE version is another matter, you would have to recompile all of QT/KDE with CC.

abush wrote:How DOES one attempt to compile Celestia with CC? Is it just a matter of changing the Makefile portion:

Don't tweak the makefile by hand, check the ./configure --help output:

HI all! Sorry to post up on an older thread, been trying to build Celesia on irix 6.5.



As squeen pointed out, this error message is resolved by declaring 'glxGetProcAddressARB' in
glext.cpp:
extern void (* glXGetProcAddressARB (const GLubyte *procName))( void );

However, the build does fail on the object file for glext.cpp using gcc:


I'm using the suggested configure flags of:


Other then that, everything else appears to compile properly. We'll keep working on it (somthing to do with build order, maybe?). Thanks!

Christophe wrote:

abush wrote:Chris, You mentioned that there are some licence issues, can you elaborate/paste some links?

I'm not a licence specialist, but since Celestia is GPL, I don't think you can legaly link it against a proprietary library. And you would need to do that to get hardware accelerated OpenGL. That being said I don't think any of the Celestia developers will take you to court for trying this.

No license problems exist for linking GPL or other open source against anything, as far as I know. You can't distribute for profit anything that you wrote that includes viral-licensed code, or contrary to the provisions of such licenses; but this should not be a limitation.

Encourage work to continue on Irix compilation and building. It seems a bit crazy to have an openGL project not able to compile and link on SGI -- the original platform of GL and OpenGL development!

scienceman wrote:No license problems exist for linking GPL or other open source against anything, as far as I know.

The situation is far from being that simple.
See the GPL FAQ.

So it depends if you consider the OpenGL lib as part of the 'core' of the operating system or not.

scienceman wrote:You can't distribute for profit anything that you wrote that includes viral-licensed code, or contrary to the provisions of such licenses; but this should not be a limitation.

Of course you can distribute GPL code for profit. How would RedHat and others make a living otherwise?

scienceman wrote:Encourage work to continue on Irix compilation and building. It seems a bit crazy to have an openGL project not able to compile and link on SGI -- the original platform of GL and OpenGL development!

I'm all for it and I don't think the licence issues are real anyway, they could just make it difficult to distribute compiled packages.

I think the technical problems are a lot more important.

Christophe wrote:

scienceman wrote:You can't distribute for profit anything that you wrote that includes viral-licensed code, or contrary to the provisions of such licenses; but this should not be a limitation.

Of course you can distribute GPL code for profit. How would RedHat and others make a living otherwise?

OK, so I should have said "You can't distribute for profit anything that you wrote that includes viral-licensed code contrary to the provisions of such licenses." (What a difference a comma and two characters makes!) Of course I know that the open source model can be used for commercial purposes. You seemed to imply in your original post and above that no one can link on their own to closed-source packages. Nothing in the GPL prevents you from linking on your own to whatever you want. For this crowd, distributing instructions on linking should be as good as distributing the linked code itself, if that's what you are worried about.

Back to technical issues. I am not an Irix user, but one of the machines available here, with a terrific display, is an SGI. Why are the OpenGL calls not sufficiently standardized to allow linking to SGI's version?

scienceman,

I don't have access to any SGI Irix systems, but...
Celestia does make use of some of the most recent OpenGL v1.4 features if they're available, so you need to make sure that the system actually has the most recently available OpenGL library installed.

I've been looking at SGI's IRIX 6.5.x Web pages and not looking good.
I can only hope that it doesn't reflect the software that's actually being shipped. The online manual is for OpenGL v1.1 and the OpenGL web page itself mentions OpenGL v1.2.

scienceman wrote:OK, so I should have said "You can't distribute for profit anything that you wrote that includes viral-licensed code contrary to the provisions of such licenses." (What a difference a comma and two characters makes!) Of course I know that the open source model can be used for commercial purposes.

OK, that's what I thought you meant, just clearing it up.

scienceman wrote:You seemed to imply in your original post and above that no one can link on their own to closed-source packages. Nothing in the GPL prevents you from linking on your own to whatever you want.

Well, re-reading this, yes, I think it does prevent you from doing it even if you're not redistributing it.

But once again nobody is going to sue you if you do.

Hi Christophe,

Thanks for the reference. Here are a couple of others that may be relevant:

SGI's Open Source Software license terms (incl. additions apparently to go with the above):
http://oss.sgi.com/projects/GenInfo/NoticeExplan/

OpenGL Sample Implementation code:
http://oss.sgi.com/projects/ogl-sample/
(with many further links contained on the accompanying sidebar.)

The above links go primarily to SGI's contributions to the open source community that are aimed at deployment on Linux, Mac OS X, and Windows, and explain the difference between the software API and the hardware acceleration that must be present to take advantage of the API calls; the software is only loosely licensed, it seems, whereas the hardware acceleration is the part where the vendors have to work hard and conform to licenses for compatibility. Having said that, I am certain that I am still missing something about why it is hard to build Celestia on Irix. I will now simply hope that someone who knows the technical details of how to code in OpenGL on Irix will explain it (or explain it again). Sorry for the diversion.

Maybe you could try asking on one of the SGI newsgroups?