Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 13 May 2020 21:09:13 +0200
From: Anders Magnusson <ragge@...d.ltu.se>
To: Rich Felker <dalias@...ifal.cx>
Cc: John Arnold <iohannes.eduardus.arnold@...il.com>,
 musl@...ts.openwall.com, pcc@...ts.ludd.ltu.se
Subject: Re: Re: [Pcc] PCC unable to build musl 1.2.0 (and
 likely earlier)

Den 2020-05-13 kl. 16:30, skrev Rich Felker:
> On Wed, May 13, 2020 at 09:10:40AM +0200, Anders Magnusson wrote:
>> Den 2020-05-12 kl. 23:21, skrev Rich Felker:
>>> Thanks. Adding pcc list to cc.
>>>
>>> On Tue, May 12, 2020 at 03:59:36PM -0500, John Arnold wrote:
>>>> With an i386 PCC 1.2.0.DEVEL built from source from
>>>> http://pcc.ludd.ltu.se/ftp/pub/pcc/pcc-20200510.tgz, I was unable to
>>>> build an i386 musl 1.2.0. The compiler first hits this error:
>>>>
>>>> ../include/limits.h:10: error: bad charcon
>>>>
>>>> This line was the only change made in commit cdbbcfb8f5d, but it has a
>>>> lengthy commit message about the proper way of determining CHAR_MIN
>>>> and CHAR_MAX.
>>> I think this is clearly a PCC bug, one they can hopefully fix. The
>>> commit message cites the example from 6.4.4.4:
>> Can you please sen med the offending line?
> #if '\xff' > 0
>
Thanks, fixed now, it was a missing pushback of ' that was the problem.

Note that this check cannot be used to see whether a target uses signed 
or unsigned char.
In pcc the above is always true, no matter what char is.  See C11 clause 
6.10.1 clause 4.

-- Ragge

Powered by blists - more mailing lists

Your e-mail address:

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.