Hello:

Having difficulties getting POV-Ray 3.50c to compile on Mac OS X 10.2.5.
Configure runs fine, but when make reaches actual compilation I'm finding
some X86-specific compile flags in there which chokes the compiler.

I've tried setting build targets for darwin, OSX, powerPC, whatever...
nothing seems to get rid of that.

Manually removing it from the makefiles (along with -mcpu=i586, etc.) works,
but then I hit some other errors that don't make sense.

Here's the error in question:

Making all in src
c++ -DPREFIX=\"/sw\" -DPOV_LIB_DIR=\"/sw/share/povray-3.5\"
-DCOMPILER_VER=\".Linux.gcc\" -DSYSCONFDIR=\"/sw/etc\"
-DUSE_IO_RESTRICTIONS=\"\"     `if [ "Xgcc" = "Xgcc" ]; then echo
"-Wno-multichar"; fi ` -O3 -finline-functions -ffast-math
-fomit-frame-pointer -funroll-loops -fexpensive-optimizations
-malign-double -foptimize-sibling-calls -minline-all-stringops
-Wno-multichar -c atmosph.cpp
cc1plus: invalid option `align-double'
cc1plus: invalid option `inline-all-stringops'
make[1]: *** [atmosph.o] Error 1

Thanks for any help!

-Bischofftep
bis### [at] maccom

Post a reply to this message

> Having difficulties getting POV-Ray 3.50c to compile on Mac OS X 10.2.5.
> Configure runs fine, but when make reaches actual compilation I'm finding
> some X86-specific compile flags in there which chokes the compiler.

	Look a few threads ago and find the one called 'New configure script'.
It's a first attempt to make all those non-x86 archs to be able to compile
POV-Ray. It might work for you, although there are known problems (I did not
yet find the time to make and upload a new version).

	Hope this helps,
	- NC

Post a reply to this message

On Thu, 24 Apr 2003 13:44:07 -0400, Bischofftep wrote:

> Hello:
> 
> Having difficulties getting POV-Ray 3.50c to compile on Mac OS X 10.2.5.
> Configure runs fine, but when make reaches actual compilation I'm finding
> some X86-specific compile flags in there which chokes the compiler.

If you follow this thread, its a step by step guide to building the
unix code on OSX, I'm afard its make file editing. Make et al are pretty
rubbish once you move out of x86 *nix land.

http://news.povray.org/povray.macintosh/27178/?mtop=205516


The last article lists the valid optimization setting for a mac.
Which ones are of any use is another matter.

http://news.povray.org/3de66f2a%241%40news.povray.org

Dave

Post a reply to this message

> Make et al are pretty
> rubbish once you move out of x86 *nix land.

  What do you mean by that?  As a Sun UltraSparc user I find that the Sun
 development tools are excellent.  Even the Intel port of Solaris is very
 much a corporate full blown unix.

Dennis

Post a reply to this message

On Fri, 25 Apr 2003 07:48:54 -0400, Dennis Clarke wrote:


>> Make et al are pretty
>> rubbish once you move out of x86 *nix land.
> 
>   What do you mean by that?  As a Sun UltraSparc user I find that the
>   Sun
>  development tools are excellent.  Even the Intel port of Solaris is
>  very much a corporate full blown unix.

Perhaps that was a little badly phrased, its not the quality of the
programs mostly its just set up. In my experience there's very few
./configure scripts that actually end up with a finished product unless
you're on a *nix.

Taking for example the situation under discusion, the make setup for UNIX
povray assumes x86 only optimization options for a ppc only platform
(ignoring marklar for the moment). now as uname -p returns powerpc you'd
thing the ./configure would have the smarts to say hey this is powerpc let
get the right optimisation. Can anyone tell me if it builds properly under
PPC linux ?

Libtool can be a nightmare too for lesser know OS's like BeOS for example.
Until very recently libtool claimed that BeOS could not used shared
libraries, which was complete and utter rubbish.

Dave

Post a reply to this message

In article <pan### [at] ntlworldcom> , "David Burnett"
<var### [at] ntlworldcom> wrote:

> Taking for example the situation under discusion, the make setup for UNIX
> povray assumes x86 only optimization options for a ppc only platform
> (ignoring marklar for the moment). now as uname -p returns powerpc you'd
> thing the ./configure would have the smarts to say hey this is powerpc let
> get the right optimisation. Can anyone tell me if it builds properly under
> PPC linux ?

You are completely on the wrong track here.  The configure script doesn't
even try to detect what platform you are on.  And that has been discussed in
the threads you have already been pointed to...

    Thorsten

Post a reply to this message

On Sat, 26 Apr 2003 01:31:38 +0200, Thorsten Froehlich wrote: 
> You are completely on the wrong track here.  The configure script doesn't
> even try to detect what platform you are on.  And that has been discussed in
> the threads you have already been pointed to...

Cut and patse from povray-3.50c/configure

  if test -z "$CC"; then
    case "`uname -s`" in
    *win32* | *WIN32*)


...

   case "`(uname -sr) 2>/dev/null`" in
    "SunOS 5"*)



which bit of those are not detecting which platform the script is 
running on. 

That is beside the point though, I wasn't having a go at povray's
build per se (although a working --without-x would be nice for
3.51 :-) just the general crappiness of all the stuff 
that gets run to create and build, from autoconf, a million
m4 macros, right down to configure, especially for cross platform 
stuff.

Post a reply to this message

In article <pan### [at] ntlworldcom> , "David Burnett"
<var### [at] ntlworldcom> wrote:

> On Sat, 26 Apr 2003 01:31:38 +0200, Thorsten Froehlich wrote:
>> You are completely on the wrong track here.  The configure script doesn't
>> even try to detect what platform you are on.  And that has been discussed in
>> the threads you have already been pointed to...
>
> Cut and patse from povray-3.50c/configure
>
>   if test -z "$CC"; then
>     case "`uname -s`" in
>     *win32* | *WIN32*)
>
>
> ...
>
>    case "`(uname -sr) 2>/dev/null`" in
>     "SunOS 5"*)
>
>
>
> which bit of those are not detecting which platform the script is
> running on.

Just take my word for it!  Also certain parts haven't been removed from the
configure script template because they are meant for later use, that in no
way implies there are supposed to detect anything right now.

    Thorsten


____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg

I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message