|
 |
earthdog wrote:
> Specs:
> Athlon 1.1 gHz Thunderbird
> RedHat 7.2
> gcc v.2.96 (stock on rh7.2)
>
> Problem:
> Can't get 3.5 source to compile.
I finally had a chance to compile 3.5 on my system (rh7.1 Athlon XP
1900+ gcc 2.96). I didn't run into any problems other than having to
edit optout.h like everyone else and creating a povray.conf file in the
/usr/local/etc directory to stop the I/O Restriction problem.
After doing ./configure and make, I tested the resulting binary out and
it worked fine. Then I edited the src/Makefile to add some compiler
optimization flags. The CXXFLAGS now look like this:
CXXFLAGS = -g -O3 -DCPU=athlon -march=athlon -finline-functions \
-fomit-frame-pointer -Wall -funroll-loops -fexpensive-optimizations \
-malign-double $(NOMULTICHAR)
There's probably some redundant flags but it works ;) I then ran
benchmark.pov (+a0.3 +w320 +h240) and got the following results:
windows prebuilt binary = 25m 48s (1548s)
linux prebuilt binary = 55m 40s (3340s)
Micha's p3 optimized = 25m 14s (1514s)
my gcc2.96 optimized = 28m 1s (1681s)
I then applied Micha's patch and got the following result:
my optimized + patch = 28m 14s (1694s)
So the patch didn't really help me but it may help with gcc 3.1. I'm
going to get that next and see what the results are. It sure looks like
gcc has improved :)
> Errors:
>
> Making all in src
> make[1]: Entering directory `/home/jgentry/temp/povray-3.50a/src'
> g++ -DPREFIX=\"/usr/local\"
> -DPOV_LIB_DIR=\"/usr/local/share/povray-3.5\"
> -DCOMPILER_VER=\".Linux.gcc\" -DSYSCONFDIR=\"/usr/local/etc\" `if
> [ "Xgcc" = "Xgcc" ]; then echo "-Wno-multichar"; fi ` -c atmosph.cpp
> g++ -DPREFIX=\"/usr/local\"
> -DPOV_LIB_DIR=\"/usr/local/share/povray-3.5\"
> -DCOMPILER_VER=\".Linux.gcc\" -DSYSCONFDIR=\"/usr/local/etc\" `if
> [ "Xgcc" = "Xgcc" ]; then echo "-Wno-multichar"; fi ` -c bbox.cpp
> In file included from bbox.cpp:47:
> optout.h:75: syntax error before `char'
[snip]
Since it looks like the first error is in optout.h and you had edited
optout.h, I'm wondering if something weird happened as a result of the
edit. Perhaps you could yank the original optout.h from the tarball,
edit the DISTRIBUTION_MESSAGE_2, comment out the error line above it and
give it another go.
-Roz
Post a reply to this message
|
|
