Re: Why so many out-of-disk-space failures on buildfarm machines?

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Why so many out-of-disk-space failures on buildfarm machines?
Date: 2007-07-19 15:37:57
Message-ID: 469F8555.50202@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>
>> Tom Lane wrote:
>>
>>> BTW, while I'm thinking of it --- it'd be real nice if the buildfarm
>>> "configuration" printout included the flex and bison version numbers.
>>>
>
>
>> Interestingly, none of our tools actually outputs the bison/flex
>> versions - perhaps configure should be doing that.
>>
>
> Hmm, that's a good solution, especially since it'll start working right
> away instead of waiting for buildfarm owners to update their scripts ;-)
>
> I think I can get it to do
> checking for flex... /usr/local/bin/flex 2.5.4
> ... does that seem reasonable?
>

looks good to me.
>
>> We do log the gcc
>> version (look in the config.log if you want to make sure).
>>
>
> Oh, that seems to be something in the base autoconf macros rather than
> anything we put in. I don't especially like hiding it in config.log
> --- who reads that?
>
>
>

Well, we should be able to add something along the lines of what you did
above, though, can't we? We already have a section in configure.in
specifically for gcc (see around line 272).

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2007-07-19 16:02:20 Re: write_pipe_chunks patch messes up early error message output
Previous Message Stephen Frost 2007-07-19 12:03:59 Re: Can someone explain this code?