Can someone comment on this? The user had CPP defined in the environment
and pointed to a less-than-optimal version. A number of CPP related
autoconf tests gave losing results, but for compilation gcc was used,
whose preprocessor has different properties and so things went wrong.
It looks like a bit of a design problem, but I'm not sure whose.
We use Autoconf 2.13.
--
Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
---------- Forwarded message ----------
Date: Tue, 17 Jul 2001 18:07:38 +0200
From: Kov�cs P�ter <[EMAIL PROTECTED]>
To: Peter Eisentraut <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: RE: [PORTS] Unable to build on Solaris 2.6
In my .profile I had CPP set to /usr/ccs/lib/cpp and autoconf probably used
this instead of gcc -E. On the other hand, at build time gcc is probably not
looking at the CPP environment variable for a preprocessor, but simply uses
its own. After all I would not say that this is a bug in autoconf, but being
a bit more idiot-proof :) would certainly not hurt.
Peter
-----Original Message-----
From: Peter Eisentraut [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 17, 2001 5:21 PM
To: Kov�cs P�ter
Cc: [EMAIL PROTECTED]
Subject: RE: [PORTS] Unable to build on Solaris 2.6
Kov�cs P�ter writes:
> Apparently, the configure script did not correctly recognize the
stringizing
> capibality of the preprocessor. (Should I report this as a bug in
> autoconf???)
Hmm. I've never seen this test give a wrong result. Can you check *why*
it does that?
--
Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
