Files4ecr
- Finished up files4ecr
- PPC toolchain build W/23084 is failing
files4ecr
From the gnu.cvs.help newsgroup I learned that doing a cvs log of everything then grepping through that is much faster than interrogating each file with cvs log. I then reorganized files4ecr to work in the following manner:
It occurred to me that often we wish to know, or pull, the file revision associated with an ECR #. I've created a script called files4ecr that accomplishes this:
saturn:files4ecr-u
Usage: files4ecr [-v] [-d] [-l] [-x] [-u] <ecr>
Where:
-v: Turn on verbose mode (Default: off)
-d: Turn on debug mode (Default: off)
-l: Local directory only, no recursion
-x: Turn on execute mode (Default: off)
-u: Dsplay usage
ecr ECR number to search for
The performance for this script is pretty good, depending on the amount of information in the CVS logs. Here's an example of it's usage:
saturn:files4ecr 20505 SETUP.csh: 10.2 - Out of date etc/tconfig: 10.2 - Already up to date SETUP.bash: 10.6 - Out of date etc/ttys-arm: 1.1 - Already up to date Makefile: 10.13 - Out of date
In noexecute mode it just displays the file and the revision of the file associated with that ECR. The -l option is similar to cvs' -l option:
saturn:files4ecr -l 20505 SETUP.csh: 10.2 - Out of date SETUP.bash: 10.6 - Out of date Makefile: 10.13 - Out of date
Also, like cvs, files4ecr operates in the current context and current working directory.
With -x turned on files4ecr will perform the cvs update commands necessary to "pull" the versions for the ECR:
saturn:files4ecr -x 20505 cvs update -r10.2 SETUP.csh - Updated cvs update -r10.2 etc/tconfig - Already up to date cvs update -r10.6 SETUP.bash - Updated cvs update -r1.1 etc/ttys-arm - Already up to date cvs update -r10.13 Makefile - Updated
And we can see that the update has taken place:
saturn:files4ecr 20505 SETUP.csh: 10.2 - Already up to date etc/tconfig: 10.2 - Already up to date SETUP.bash: 10.6 - Already up to date etc/ttys-arm: 1.1 - Already up to date Makefile: 10.13 - Already up to date
Anybody interested in such a script?
Note: I've noticed that "ECR Number:" is not necessarily a consistent indicator of an ECR number. I search for several strings:
/^ECR Number: (\d*)$/ or /^ECR# (\d*)$/ or /^ECR # (\d*)$/ or /^\s*ECR (\d*)/
I've also noticed that a single ECR number may be attached to several revisions. files4ecr takes the latest revision in such cases.
PPC toolchain build W/23084 is failing
Preliminary investigation shows that while attempting to configure libiberty the build process is unable to use gcc to compile things. It seems to be lacking a crt1.o