Subject: Dealing with configure (bug?)
To: None <firstname.lastname@example.org>
From: Jon Buller <email@example.com>
Date: 03/03/2004 20:16:06
Over the past few years, I've tried off and on to use lang/clisp
with no luck. It failed some of its tests when built with egcs
(back when that was our main compiler) and would not finish building.
The CLisp people said "Update your compiler, that's an antique".
gcc-2.95 did the exact same thing.
So now I have gcc-3.3.3 and I thought I'd try again. When using
pkgsrc it failed for some reason, so I thought I'd beat on 2.32
(current release) instead of the 2.30 version in pkgsrc right now.
When just building the straight distfile from CLisp, I can get it
to build, but not install.
OK, there's the history. The good news is it looks like they rolled
in all the patches. The bad news is that when I use the pkgsrc
makefiles, I get configure griping like this:
configure: loading cache ../../config.cache
configure: error: `CPPFLAGS' has changed since the previous run:
configure: former value: -I/usr/pkg/include
configure: current value: -I/usr/pkg/include
configure: error: changes in the environment can compromise the build
configure: error: run `make distclean' and/or `rm ../../config.cache' and start over
It looks like configure is setting up a config.cache file, then
going into several subdirectories and configuring them. It looks
like it does it right several times, and then...
Anyone seen anything like this, or have a suggestion? Is it a
configure bug, or a problem with the way it's called? I'm not the
most clued when it comes to GNU configure. I just run it, let it
do it's magic, and move on. I'm more than happy to provide the
output, (or temp files) but it's 485 lines, so I thought I'd save
the list from such torture.
Thanks in advance,