>  This is a problem with GCC, not POV-Ray.  I have faced it myself
> (though when compiling the Zlib included in the POV-Ray distro) trying
> to compile with gcc-3.3.4.  According to GCC bugzilla*, this internal
> compiler error (aka ICE) seems to occur in the 3.3 series on the AMD64,
> at least this 3.3.4 release.
>
>  OTOH, POV-Ray compiles fine with the GCC 3.4.x series.  Moreover
> the later supports the k8/opteron compiler flags, which should result in
> a faster POV-Ray binary (also the 3.3.x series usually produce slightly
> slower code on other platforms).  I recommand you install GCC 3.4.1 (or
> the newest 3.4.2) and try again compiling POV-Ray with it -- works for me.
>
>  - NC
>
> (*) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16874

Hello and thank you for your reply,

but I still have the same error with gcc 3.4x series,
unpacked form fresh source code did not use the "old" one:

povms.cpp: In function `int POVMSUtil_TempAlloc(void**, int)':
povms.cpp:3830: error: unerkennbares insn:
(insn:HI 82 81 64 2 0x2a9682e780 (set (reg:SI 58)
        (plus:SI (mult:SI (reg:SI 58)
                (const_int 2 [0x2]))
            (const_int -2 [0xfffffffffffffffe]))) -1 (insn_list 81 (nil))
    (nil))
povms.cpp:3830: internal compiler error: in extract_insn, at recog.c:2175
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions, see
<URL:file:///usr/share/doc/gcc-3.3/README.Bugs>.
make[3]: *** [povms.o] Fehler 1

make[2]: *** [all-recursive] Fehler 1

make[1]: *** [all-recursive] Fehler 1

make: *** [all] Fehler 2

/usr/src/povray-3.6.1$> gcc -v
Lese Spezifikationen von /usr/lib/gcc/x86_64-linux/3.4.2/specs
Konfiguriert mit: ../src/configure -v
--enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr
--libexecdir=/usr/lib --with-gxx-include-dir=/usr/include/c++/3.4
--enable-shared --with-system-zlib --enable-nls --without-included-gettext
--program-suffix=-3.4 --enable-__cxa_atexit --enable-libstdcxx-allocator=mt
--enable-clocale=gnu --enable-libstdcxx-debug --enable-java-gc=boehm
--enable-java-awt=gtk --disable-werror x86_64-linux
Thread-Modell: posix
gcc-Version 3.4.2 (Debian 3.4.2-2)

Is it possible to send me your .deb package?

Post a reply to this message

In article <web.414d5f85dec77a7acb08306a0@news.povray.org> , "" 
<nomail@nomail> wrote:

> but I still have the same error with gcc 3.4x series,
> unpacked form fresh source code did not use the "old" one:

As you were told, this is an error in your compiler, not in the POV-Ray
source code.  The error message contains information where to report
compiler bugs.  You need to follow these instructions, there is no other
answer you can get here other than that it is a bug in your compiler, for
which nobody here is responsible and about which nobody here can do
anything.

> gcc-Version 3.4.2 (Debian 3.4.2-2)

I would strongly recommend to get the official gcc version from the gcc
website rather than whatever Debian ships with their distribution!  Debian
is known to screw up perfectly good open source packages and to distribute
supposedly "improved" versions full of bugs due to untested patches Debian
adds to their distribution.  You might also want to consider using a less
outdated Linux distribution like Redhat or Suse.

POV-Ray has been successfully - without encountering compiler bugs -
compiled by many users using recent versions of the official gcc
distribution.  Internal compiler errors are bugs in your compiler, and not
in POV-Ray or the POV-Ray source code.  As others have successfully used the
official gcc version you mentioned, it is  there is either some other bug
in your Debian system installation or the gcc you got from them.

> Is it possible to send me your .deb package?

There is no such thing.  You should use the official POV-Ray source package
from the povray.org website.  If you are unable to compile POV-Ray yourself,
I can only strongly recommend you use the binary version available on our
website.

    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

nomail@nomail wrote:
> 
> Hello and thank you for your reply,
> 
> but I still have the same error with gcc 3.4x series,
> unpacked form fresh source code did not use the "old" one:
> 
> [...]

Then your gcc is most likely messed up somehow.  Did you bootstrap it 
from the official gcc source package or use a version coming with your 
distribution?

BTW it would be adequate to post with a real name and not anonymously.

Christoph

-- 
POV-Ray tutorials, include files, Sim-POV,
HCR-Edit and more: http://www.tu-bs.de/~y0013390/
Last updated 06 Jul. 2004 _____./\/^>_*_<^\/\.______

Post a reply to this message

...hey never said the source code from povray is bugged...
I know the problem is between chair and keyboard, so I tried to get some
help here, that was the only reason for posting!

Iam new to Debian AMD64 and povray, so there are lot of things I try to
explore.
I used Debian Woody before and never had big problems with it, this was the
main reason to get back to Debian....
anyway I will not reinstall all my OS to get a new one like Redhat or Suse,
was hard work enough to get it all running.....

My personal information is updated, so I hope this ok now, never meant to be
mr. invisible :)..first time posting here, sorry

Iam using the gcc that is shiped with Debian AMD64, and did not boostrap
anything.
It was a netboot installation, and installed all with apt-get.

Thank you and best regards

Andree

Post a reply to this message

Andree Zeulner <nomail@nomail> wrote:
> I know the problem is between chair and keyboard

  Not according to the error message given by the compiler.

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

"Thorsten Froehlich" <tho### [at] trfde> writes:
> I would strongly recommend to get the official gcc version from the gcc
> website rather than whatever Debian ships with their distribution!  Debian
> is known to screw up perfectly good open source packages and to distribute
> supposedly "improved" versions full of bugs due to untested patches Debian
> adds to their distribution.  You might also want to consider using a less
> outdated Linux distribution like Redhat or Suse.

Yeesh, quit it with the clueless flames.  Did Debian steal your
girlfriend or something?

-Miles
-- 
Would you like fries with that?

Post a reply to this message

> Yeesh, quit it with the clueless flames.  Did Debian steal your
> girlfriend or something?

	They don't steal girlfriends (AFAIK), but occasionally some
package maintainers do manage to "destabilize" the softwares they
have in charge  :-)  [I should actually  :-(  instead]

	Not only Debian does that, in fact.  I also heard some funny
things about other Linux distributors.  One well-known example is
about a GCC 2.96 (which was never released by the GCC development
team) that caused many troubles.

	- NC

Post a reply to this message

In article <87y### [at] tc-1-100kawasakigolnejp> , Miles Bader 
<mil### [at] gnuorg>  wrote:

>> I would strongly recommend to get the official gcc version from the gcc
>> website rather than whatever Debian ships with their distribution!  Debian
>> is known to screw up perfectly good open source packages and to distribute
>> supposedly "improved" versions full of bugs due to untested patches Debian
>> adds to their distribution.  You might also want to consider using a less
>> outdated Linux distribution like Redhat or Suse.
>
> Yeesh, quit it with the clueless flames.

I think it is you who is clueless here.  Did you ever check out what junk
Debian distributes a "stable" or "testing" povray packages.  Their "stable
version is a seven year outdated version of POV-Ray with more broken and
incompatible patches than POV-Ray has lines of code.  Their "testing"
version is not a tiny bit better, and there is no serious interest in
correcting it either.

If I would dare to install Debian anywhere, I am sure I would quickly find
that most of their packages enjoy the same kind of improvements.  And this
thread regarding gcc problems pretty much emphasizes this point perfectly!

    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

Nicolas Calimet <pov### [at] freefr> writes:
> 	They don't steal girlfriends (AFAIK), but occasionally some
> package maintainers do manage to "destabilize" the softwares they
> have in charge  :-)  [I should actually  :-(  instead]
>
> 	Not only Debian does that, in fact.  I also heard some funny
> things about other Linux distributors.  One well-known example is
> about a GCC 2.96 (which was never released by the GCC development
> team) that caused many troubles.

That's the point of course -- _all_ distros patch their software.
Sometimes this causes problems (as the infamous redhat "gcc 2.96" case),
but usually it's for good reaons (otherwise they wouldn't do it).
Debian is no different.

-Miles
-- 
I'm beginning to think that life is just one long Yoko Ono album; no rhyme
or reason, just a lot of incoherent shrieks and then it's over.  --Ian Wolff

Post a reply to this message

"Thorsten Froehlich" <tho### [at] trfde> writes:
>> Yeesh, quit it with the clueless flames.
>
> I think it is you who is clueless here.  Did you ever check out what junk
> Debian distributes a "stable" or "testing" povray packages.  Their "stable
> version is a seven year outdated version of POV-Ray with more broken and
> incompatible patches than POV-Ray has lines of code.  Their "testing"
> version is not a tiny bit better, and there is no serious interest in
> correcting it either.

The quality of packages depends on the package maintainer; for major
packages (gcc, X, etc), debian's maintainers are second to none.  I have
no idea what's up with the povray package, but Debian is a free software
distro, and Povray is _not free software_, so what do you really expect?

Hey, I use Povray, and run Debian (on several machines); I certainly
wish the Povray package would get a bit of love!

> If I would dare to install Debian anywhere, I am sure I would quickly find
> that most of their packages enjoy the same kind of improvements.  And this
> thread regarding gcc problems pretty much emphasizes this point perfectly!

So you've never actually used Debian then?  Do you have any actual
_evidence_ that the gcc problems in this thread have anything to do with
a Debian patch, or of the systemic problems you accuse them of?  Or are
you just randomly spewing wild-ass generalizations because you're pissed
over the state of the Povray package?

Every GNU/linux user that I know runs Debian, for good reason:  It's
more functional, more solid, and _far_ easier to administer than most
other distros, and upholds the ideals of free software better than all.

-Miles
-- 
`The suburb is an obsolete and contradictory form of human settlement'

Post a reply to this message