[adding autoconf - I prefer discussions to be public rather than to just me]
On 02/15/2011 11:19 PM, Robert Dell wrote:
> Might I make a suggestion?
> EVERY time I run the configure script, it checks for the same things,
> over and over
> checking for sys/types.h... yes
> checking for sys/stat.h..
>> I would also encourage putting the source for all test programs into the
>> config.log file too, not just the failed ones. I don't know about other
>> folks, but we use config.log for the sole purpose of debugging problems,
>> and so the more information we can get in that file, the better off
Keith Bostic wrote:
> I'd like to make a small suggestion for autoconf -- it would be helpful
> in debugging configuration problems if the output that is displayed on
> the screen during configuration [...] were also copied into the
>config.log output.
That feature has already been incorporated i
Keith Bostic writes:
> I'd like to make a small suggestion for autoconf -- it would be
> helpful in debugging configuration problems if the output that is
> displayed on the screen during configuration were also copied into the
> config.log output.
This is already the case in the the development
On Wed, 31 May 2000, Keith Bostic wrote:
> I'd like to make a small suggestion for autoconf -- it would be helpful
> in debugging configuration problems if the output that is displayed on
> the screen during configuration:
>
> checking for gcc... cc
> checking whether the C compiler (cc -O2
