Re: Building PCC for "tools" is broken (missing symbol __USE)- PCC bug or NetBSD source tree error?

[Anders Magnusson <ragge%ludd.ltu.se@localhost>]

The commit messages are saved at marc.info, see 
http://marc.info/?l=pcc-commit-list&m=140628065609751&w=2

To get a diff you can use cvs -d 
:pserver:anonymous%pcc.ludd.ltu.se@localhost:/cvsroot rdiff -u -r1.376 -r1.377 
pcc/cc/ccom/cgram.y

Should be directly applyable.

-- Ragge

William D. Jones skrev 2014-07-26 02:05:
> Do you have a patch that I can apply to my private NetBSD source tree 
> of pcc for the time being? My pcc is compiled into the NetBSD tools 
> directory, at which point it is used to compile the rest of the NetBSD 
> source tree.
>
> -----Original Message----- From: Anders Magnusson
> Sent: Friday, July 25, 2014 5:41 AM
> To: William D. Jones ; Iain Hibbert
> Cc: current-users%NetBSD.org@localhost
> Subject: Re: Building PCC for "tools" is broken (missing symbol 
> __USE)- PCC bug or NetBSD source tree error?
>
> William D. Jones skrev 2014-07-25 07:58:
> > > Yes, I think you can set UNSUPPORTED_COMPILER.pcc in the Makefile 
> > > and it
> > > will proceed using a different one
> >
> > For the time being, I'll make a note of all the tools that pcc cannot
> > currently build, and set Makefiles accordingly. I'm not sure if these
> > tools under gpl track upstream or not, so at least for tonight I'm not
> > sure if feel comfortable changing the actual source code of binutils
> > to make pcc compile it successfully. Although perhaps submitting a
> > patch to binutils that undefines __restrict in arrays if pcc is being
> > used is a possible solution for the time being.
> pcc accepted __restrict but not restrict in array declaration.  I just
> added a yacc rule to pcc to accept both (to master tree).
>
> -- Ragge
>
> --
> William D. Jones