On Wed, Aug 20, 2014 at 11:04:52AM -0600, Eric Blake wrote:
> Oops, I totally overlooked what file you were patching. Autoconf
> doesn't maintain config.guess; you'll probably want to resubmit the
> patch upstream to config-patches (cc'd), as mentioned in the header
> of that file. Once it is up
On 08/20/2014 10:15 AM, Thomas Jahns wrote:
> Hello Eric,
>
> On 08/20/14 18:10, Eric Blake wrote:
>>> - eval `$CC_FOR_BUILD -E $dummy.c 2>/dev/null | grep '^LIBC'` + eval
>>> `$CC_FOR_BUILD -E $dummy.c 2>/dev/null | sed -n '/^LIBC/{s/LIBC *=
>>> *\(.*\)$/LIBC='"'"'\1'"'"'/;p;}'`
>>
>> Thanks
Hello Eric,
On 08/20/14 18:10, Eric Blake wrote:
>> -eval `$CC_FOR_BUILD -E $dummy.c 2>/dev/null | grep '^LIBC'` + eval
>> `$CC_FOR_BUILD -E $dummy.c 2>/dev/null | sed -n '/^LIBC/{s/LIBC *=
>> *\(.*\)$/LIBC='"'"'\1'"'"'/;p;}'`
>
> Thanks for the patch. We like to keep to 80-column lines whe
On 08/20/2014 09:47 AM, Thomas Jahns wrote:
> Hello,
>
> I've found and fixed a problem where pgcc -E translates its input to contain
> extra spaces. Since config.guess expects the preprocessor output to be a well
> formed shell variable assignment, I've added some sed code to ensure this.
>
> Pl
Hello,
I've found and fixed a problem where pgcc -E translates its input to contain
extra spaces. Since config.guess expects the preprocessor output to be a well
formed shell variable assignment, I've added some sed code to ensure this.
Please consider the attached patch for inclusion in autoconf
