Once again, sorry for the delay (I need to work on this). Just as a
heads-up, prepare_import.sh appears to be broken on my (Ubuntu-Linux)
machine, so I'll go ahead and just apply the diff we discussed that add
__restrict in arrays directly. This means that my copy of pcc will be a
hybrid between the currently imported pcc tree in NetBSD and the current
master on pcc.ludd.ltu.se- not sure if that will be an issue in practice
however. I'm going to do a clean build of my 486 machine's tree beforehand
with the pcc-20140706, however, to make sure my source tree is sane (see
"Missing files in DESTDIR- NetBSD version increment problem?").
Have B. Harder's ("Re: pcc build error that has been outstanding for a few
days...") changes been added to the main tree yet?
Perhaps PCC will be ready by the time NetBSD 7 is released- there's still
time to make sure it works!
The following shows the error:
william@xubuntu-ltrain:~/Projects/NetBSD-CVS/src/external/bsd/pcc$
./prepare-import.sh
+ set -e
+ [ ! -d work -o ! -d work/pcc ]
+ echo ====> Removing pcc CVS directories...
====> Removing pcc CVS directories...
+ find work+ -typexargs rm -Rf
d -name CVS
+ echo ====> Fixing file and directory permissions...
====> Fixing file and directory permissions...
+ find work -type d -exec chmod u=rwx,go=rx {} ;
+ find work -type f -exec chmod u=rw,go=r {} ;
+ echo ====> Fixing RCS tags...
====> Fixing RCS tags...
+ grep -RL \$(NetBSD|Id).*\$ work
+ sed -e /\$NetBSD\$/d -e s,\$\(NetBSD[[:>:]].*\)\$,\1, -e
s,\(.*\)\$\(Id[[:>:]].*\)\$\(.*\),\1\2\3 \
\1\$NetBSD\$\3,
sed: -e expression #2, char 29: Invalid character class name
Sadly, I do not know enough about the context of replacements you are trying
to make to feel comfortable editing this myself.
Thanks again for your prompt responses!
-----Original Message-----
From: Iain Hibbert
Sent: Thursday, July 31, 2014 5:20 AM
To: William D. Jones ; Anders Magnusson
Cc: [email protected]
Subject: Re: Building PCC for "tools" is broken (missing symbol __USE)- PCC
bug or NetBSD source tree error?
On 31 July 2014 06:13:00 BST, "William D. Jones" <[email protected]>
wrote:
Sorry for the delay in getting back. Iain sent me an email suggesting a
checkout like you suggested, or using prepare_import.sh in
$NETBSD_ROOT/external/bsd/pcc/. Is prepare_import.sh up to date?
it should be fine for current PCC sources
Should
I
use that script instead, or are there subtle issues to using that
script
right now as opposed to applying the diff directly (I've read that
PCC's
files are kept in multiple parts of the source tree)?
I don't think that is the case, feel free to apply the diff directly
It seems as if
"prepare_import.sh" implements the equivalent of git subtree (track
repository from within repositoty).
I use that script to prepare the PCC sources before import to netbsd tree..
you can use it locally and get the same result as if I had imported a new
version
if you just apply one patch at a time there is always the chance you miss
something
--
William D. Jones
Rowan University | ECE | 2012
Member IEEE
Member Tau Beta Pi
[email protected]
Message sent using 'Windows Live Mail' client.
