Rob,
The persistancy you're seeing is from higher versions of autoconf
being used and a misunderstanding how to override the default CFLAGS.
If you wish to override the optimization, etc, do the following with
the newer autoconf stuff:
./configure CFLAGS=-O
However, I'd recommend using -O2
This can't be unless the libtool branch is just passing a different
param to the compiler. The files are exactly the same from the head
and the libtool branch. You may look at the params sent to the
compiler. Is -O2 being set for one and not the other? If so, that is
your problem. People have
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.
Tom
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
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.
Tom
On Mon, 9 Jun
I have compiled the tarball without errors on my FreeBSD 4.8 PC
(with gcc 2.95.4). However, I get an enormous list of warnings.
A file with all the warnings is attached.
Please have a look whether these address possible bugs.
Regards,
Rob.
warnings.gz
Description: Unix tar archive
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
