 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
When compiling PovRay on a 64 bit Linux system, is it sufficient to just do
the configure and make as per the install file or do I need to add the -64
option someplace to optimize it for a 64 bit system?
--
Ger
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ger wrote:
> When compiling PovRay on a 64 bit Linux system, is it sufficient to just do
> the configure and make as per the install file or do I need to add the -64
> option someplace to optimize it for a 64 bit system?
POV-Ray compiles fine on most 64 bit Unix systems including AMD64.
Christoph
--
POV-Ray tutorials, include files, Sim-POV,
HCR-Edit and more: http://www.tu-bs.de/~y0013390/
Last updated 03 May. 2005 _____./\/^>_*_<^\/\.______
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> When compiling PovRay on a 64 bit Linux system, is it sufficient to just do
> the configure and make as per the install file
Yes. In principle any 64 bit Linux distro comes with a development
environment set to produce 64 bit binaries. If for some reason you need to
get 32 bit binaries instead, then you have to pass the "-32" flag to the
compiler (and implicitely to the assembler and linker as well).
FYI, on non-Linux 64 bit systems, however, it might be slighlty
more complicated. For instance on IRIX64 (SGI machines), compiling a
64 bit povray binary with a gcc distro installed under my home directory,
I had to do the following:
./configure CFLAGS=-mabi=64 CXXFLAGS=-mabi=64 LDFLAGS=-mabi=64 \
-L$HOME/software/irix/lib/mabi=64 -L/usr/lib64/mips4 -L/usr/lib64
make check install
since gcc on IRIX64 produces 32 bit binaries by default. Note that
the -L$HOME/software/irix/lib/mabi=64 flag points to my user-installed gcc,
the other -L flags point to the system libraries.
- NC
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Nicolas Calimet wrote:
>> When compiling PovRay on a 64 bit Linux system, is it sufficient to just
>> do the configure and make as per the install file
>
> Yes. In principle any 64 bit Linux distro comes with a development
> environment set to produce 64 bit binaries. If for some reason you need
> to get 32 bit binaries instead, then you have to pass the "-32" flag to
> the compiler (and implicitely to the assembler and linker as well).
>
>
> FYI, on non-Linux 64 bit systems, however, it might be slighlty
> more complicated. For instance on IRIX64 (SGI machines), compiling a
> 64 bit povray binary with a gcc distro installed under my home directory,
> I had to do the following:
>
> ./configure CFLAGS=-mabi=64 CXXFLAGS=-mabi=64 LDFLAGS=-mabi=64 \
> -L$HOME/software/irix/lib/mabi=64 -L/usr/lib64/mips4 -L/usr/lib64
> make check install
>
> since gcc on IRIX64 produces 32 bit binaries by default. Note that
> the -L$HOME/software/irix/lib/mabi=64 flag points to my user-installed
> gcc, the other -L flags point to the system libraries.
>
>
> - NC
Thanks Nicolas.
I have compiled it on a 64 bit system and it runs fine. I was just wondering
if it was the optimum compile.
Btw, the speed difference is roughly 35-45% on an AMD 3500+
--
Ger
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Btw, the speed difference is roughly 35-45% on an AMD 3500+
If you refer to the speed difference between 32 and 64 bit povray
binaries, what you observe will greatly depend on the pov scenes. On the
official benchmark.pov/.ini you should get closer to a 20% speedup.
- NC
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Nicolas Calimet wrote:
>> Btw, the speed difference is roughly 35-45% on an AMD 3500+
>
>
> If you refer to the speed difference between 32 and 64 bit povray
> binaries, what you observe will greatly depend on the pov scenes. On the
> official benchmark.pov/.ini you should get closer to a 20% speedup.
More important than the scene is if you compare a custom 64bit compile
with the official binary or an optimized 32bit compile. :-)
Christoph
--
POV-Ray tutorials, include files, Sim-POV,
HCR-Edit and more: http://www.tu-bs.de/~y0013390/
Last updated 03 May. 2005 _____./\/^>_*_<^\/\.______
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Christoph Hormann wrote:
> Nicolas Calimet wrote:
>>> Btw, the speed difference is roughly 35-45% on an AMD 3500+
>>
>>
>> If you refer to the speed difference between 32 and 64 bit povray
>> binaries, what you observe will greatly depend on the pov scenes. On the
>> official benchmark.pov/.ini you should get closer to a 20% speedup.
>
> More important than the scene is if you compare a custom 64bit compile
> with the official binary or an optimized 32bit compile. :-)
>
> Christoph
>
It was the official 32 bit binary compared with a recompiled 64 bit binary.
And the "test" was not an extensive one, just 4 scenes that I have made
myself. Those scenes never have stuff like isosurfaces or meshes. So you
might not even consider it a test, just a quick and dirty speed compare.
--
Ger
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> ./configure CFLAGS=-mabi=64 CXXFLAGS=-mabi=64 LDFLAGS=-mabi=64 \
> -L$HOME/software/irix/lib/mabi=64 -L/usr/lib64/mips4 -L/usr/lib64
Whoops, that is not correct as double-quotes are missing (I copied
and pasted the string from config.log which does not store quotes from the
command-line):
./configure CFLAGS=-mabi=64 CXXFLAGS=-mabi=64 \
LDFLAGS="-mabi=64 -L$HOME/software/irix/lib/mabi=64 -L/usr/lib64/mips4
-L/usr/lib64"
- NC
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
