On Tuesday 15 November 2011, Bruno Haible wrote:
> Eric Blake wrote:
> > > ... on an unstable Debian using pcc
> > > (Portable C Compiler, version 1.1.0~DEVEL+20110422-1
> > ...
> > Warnings like this, and the error in test-float.c, mean that all other
> > packages using the same gnulib modules wil
Eric Blake wrote:
> > ... on an unstable Debian using pcc
> > (Portable C Compiler, version 1.1.0~DEVEL+20110422-1
> ...
> Warnings like this, and the error in test-float.c, mean that all other
> packages using the same gnulib modules will have the same problem. We
> should fix it upstream in gnul
Paul Eggert writes:
> On 11/14/11 06:17, Eric Blake wrote:
>> Is there any easy way to identify pcc at compile time, such as a
>> preprocessor macro it sets differently than gcc?
>
> It's not *easy*, but the C macro __VERSION__
> expands to a string that starts with "pcc ".
> On my host (Fedora 1
On 11/14/11 06:17, Eric Blake wrote:
> Is there any easy way to identify pcc at compile time, such as a
> preprocessor macro it sets differently than gcc?
It's not *easy*, but the C macro __VERSION__
expands to a string that starts with "pcc ".
On my host (Fedora 15 x86-64) the exact string is
"pc
[adding bug-gnulib]
On 11/13/2011 06:50 AM, Stefano Lattarini wrote:
> I don't know if it's of any interest, but I'm experiencing the following
> failure while trying to test grep on an unstable Debian using pcc
> (Portable C Compiler, version 1.1.0~DEVEL+20110422-1, installed from
> experimental
