|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi,
I am trying to compile povray 3.5c on a SGI Octane Irix6.5 without success.
After ./configure ; make the compilation stops with the error message:
c++ atmosph.cpp
cc1plus: Invalid option `align-double'
cc1plus: Invalid option `inline-all-stringops'
I have gcc version 3.0.4 installed. Later I tried it on another SGI with
native compilers also without success.
It seems that configure, won't recognize the machine type atomatically as it
always assumes -DCOMPILER_VER=\".Linux.gcc\. So far I found no way to coax
it into accepting other compiler switches. It does not react fully to
environment variables like CFLAGS but it accepts CC when I try to compile it
with a native compiler.
I had similar problems on Compaq(HP) Alpha workstations with Tru64 Unix
5.1a.
Again it appears that configure definitly expects linux i646 for which it
works.
Can someone help ?
L.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <web.3e3935dac6c37b31dce8a3800@news.povray.org> , "Lothar"
<les### [at] helixnihgov> wrote:
> Can someone help ?
Removing the two options should be sufficient. -DCOMPILER_VER is just a
declare of COMPILER_VER and not relevant for the compiler.
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thorsten Froehlich wrote:
>In article <web.3e3935dac6c37b31dce8a3800[at]news.povray.org> , "Lothar"
><les### [at] helixnihgov> wrote:
>
>> Can someone help ?
>
>Removing the two options should be sufficient.
No. You need to do more.
>-DCOMPILER_VER is just a
>declare of COMPILER_VER and not relevant for the compiler.
I know. I just wanted to point out that somehow configure does not know
which machine it is running on.
There are a number of problem like inappropriate type casts etc. which I
mostly ignore but in unix.cpp I get this:
unix.cpp:658: cannot convert `void (*)(int)' to `void (*)()' for argument`2'
to `void (* signal(int, void (*)()))()'
and more of this kind.
Any ideas ?
L.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <web.3e396da957e82f2edce8a3800@news.povray.org> , "Lothar"
<les### [at] helixnihgov> wrote:
>>Removing the two options should be sufficient.
>
> No. You need to do more.
For me on Mac OS X it works with gcc 3.1 if I remove those, and specify the
correct architecture, of course.
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <web.3e396da957e82f2edce8a3800@news.povray.org> , "Lothar"
<les### [at] helixnihgov> wrote:
> I know. I just wanted to point out that somehow configure does not know
> which machine it is running on.
>
>
> There are a number of problem like inappropriate type casts etc. which I
> mostly ignore but in unix.cpp I get this:
> unix.cpp:658: cannot convert `void (*)(int)' to `void (*)()' for argument`2'
> to `void (* signal(int, void (*)()))()'
> and more of this kind.
>
> Any ideas ?
Well, here the problem is that you are running on the worst and most
outdated Unix implementation around. Either IRIX does not support an
argument here or the headers its supplies are broken (both is likely).
IRIX does not seem to like that the signal handler takes an argument, but
that is how ANSI defined the signal function. If there isn't a way to get
IRIX to behave as standardized, I am afraid you will have to change the
source code.
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi,
Has anyone a running Povray 3.5 for IRIX 6.5 so far? I was trying to
compile povray3.50c on an Indigo2 10K but had no success.
Claus.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Lothar, Claus, and anyone interested :o)
I've finally managed to compile POV-Ray 3.5c on IRIX 6.5
with gcc-3.2.1 and a statically linked libpng (all other libs
are normally shared). I DIDN'T TEST IT AT ALL. Available here:
http://pov4grasp.free.fr/download/povray.gz
PS1: IRIX is a f***ing environment for compiling anything. I spent
several days for nothing trying to compile the successive
versions of gcc (starting at gcc-3.0) when they appeared online,
until I got this gcc-3.2.1 working with a single mod in the
source makefile. POV-Ray was almost as difficult to get here.
(only gcc-2.8.1, from 1998, was already installed, and could
not work properly).
PS2: I'm currently working on a rewrite of the ./configure script
that won't be targetted towards Linux, but with compilation
flags detected on-the-fly. It's moslty ready, however it still
fails on IRIX. Not surprising though... Damnit.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Nicolas Calimet wrote:
> Lothar, Claus, and anyone interested :o)
>
> I've finally managed to compile POV-Ray 3.5c on IRIX 6.5
>with gcc-3.2.1 and a statically linked libpng (all other libs
>are normally shared). I DIDN'T TEST IT AT ALL. Available here:
>
>http://pov4grasp.free.fr/download/povray.gz
>
Thanks a lot Nicolas for providing the bins. Unfortunately I have
difficulties to unpack your gz. Using gunzip I'll receive the message: Not
in gz format. Any recommendation? Have Irix 6.5 with no Overlays. Tried on
an Indigo II and Octane.
>
>PS1: IRIX is a f***ing environment for compiling anything. I spent
> several days for nothing trying to compile the successive
> versions of gcc (starting at gcc-3.0) when they appeared online,
> until I got this gcc-3.2.1 working with a single mod in the
> source makefile. POV-Ray was almost as difficult to get here.
> (only gcc-2.8.1, from 1998, was already installed, and could
> not work properly).
>
>PS2: I'm currently working on a rewrite of the ./configure script
> that won't be targetted towards Linux, but with compilation
> flags detected on-the-fly. It's moslty ready, however it still
> fails on IRIX. Not surprising though... Damnit.
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |