Building on OS X 10.2

Has anyone built 5.0 for OS X 10.2?

loopless's picture

My attempts to build for 10.2 have really hit a bit of a brick wall. I am using the latest developer tools from Apple. gcc is version 3.1

The
./configure --with-tclconfig=/Library/Frameworks/Tcl.framework/ --with-tkconfig=/Library/Frameworks/Tk.framework/ --with-java-include=/Library/Java/Home/include/

Seemed to work fairly well, though building libtool had a minor problem. The detection of the JNI version seems flawed as well.

Once past all that , I tried the obvious from the top level src directory.
% make
make all-recursive
Making all in TKernel
/bin/sh: cd: TKernel: No such file or directory
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

The TKernel directory is present.

Any hints?

William Jones's picture

`cd src; make` might help. You should probably check out http://autoopencas.sourceforge.net to get a working Autoconfig version if you have not already done so.

loopless's picture

That (cd src;make) did in fact show some promise. However the next issue was ( in TKernel)

Makefile:1504: Dico_DictionaryOfInteger_0.Plo: No such file or directory
...
...
....
Makefile:1980: Units_UtsSequence_0.Plo: No such file or directory
make: *** No rule to make target `Units_UtsSequence_0.Plo'. Stop.

Eventually I got a make to actually start doing some compiling with a
make -k ( ignore errors)

Andrew

William Jones's picture

You may want to just grab the copy from http://autoopencas.sourceforge.net and try that. It has been reported elsewhere on this forum to configure/build out of the box. Unfortunately, I do not think that it is strictly current with opencascade.org CVS (i.e. OCC SA 5.0). I wish that opencascade.org would incorporate Robert Boehne's autoconfig stuff in their repository SOON! This is after all open source right? Where is the incentive for outside contributors if changes are not incorporated. It should have been done prior to 5.0 release, but appears not.

loopless's picture

I am somewhat suprised that no "developers/packagers" are commenting on this issue. Is this the wrong forum to discuss build problems?