On Mon, 9 Jun 2003 David Thompson wrote: > I bet if you had -O2 set in your CFLAGS that you would see this on > the head branch, by default this is off on the head but I believe > libtool sets it on. > >>I observe the same behavior with the tarball using gcc-3.2.2 on >>FreeBSD-4.8. Also, doesn't occur with cvs HEAD branch. >> >>On Mon, 9 Jun 2003, Rob Lahaye wrote: >> >>> David Thompson wrote: >>> > I have updated the tarball at opendx.npaci.edu/source/dx-4.3.0.tar.gz >>> >>> Still, zclipQ.c compliles forever here. Let it be a gcc-compiler bug, >>> but this only occurs with your tarball; not with the HEAD branch of CVS! >>> >>> Please consider an easy solution to bypass this problem/bug. >>> >>> I'm using gcc 2.95.4 on FreeBSD 4.8.
David, The "-O2" in this tarball is too persistent. I have set environment vars to use "-O" instead (e.g. CFLAGS, CPPFLAGS, CXXFLAGS, FFLAGS etc.), but to no avail. The compilation then went on with both present, "-O" and "-O2" !! At last I edited the configure script and replaced all "-O2" by "-O" and that worked. But this is a rather dirty way of solving the problem. Regards, Rob.
