[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: failure in building gnulib tests wih pcc on debian
|
From: |
Paul Eggert |
|
Subject: |
Re: failure in building gnulib tests wih pcc on debian |
|
Date: |
Mon, 14 Nov 2011 10:15:59 -0800 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20110927 Thunderbird/7.0 |
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
"pcc 1.0.0.RELEASE 20110221 for x86_64-unknown-linux-gnu, mockbuild@".
Also, on my host, pcc fails so badly that it can't build executables; see
<http://bugzilla.redhat.com/show_bug.cgi?id=708305> and
<http://pcc.ludd.ltu.se/jira/browse/PCC-353>.
pcc seems like pretty low priority so I'm not inclined to
follow up on this.