This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
File permissions in GCC-3.3.3 second prerelease
- From: John Marshall <johnm at opera dot no>
- To: gcc at gcc dot gnu dot org
- Cc: Gabriel Dos Reis <gdr at cs dot tamu dot edu>
- Date: Wed, 11 Feb 2004 21:05:33 +0100
- Subject: File permissions in GCC-3.3.3 second prerelease
Gabriel Dos Reis wrote:
> The second prerelease of GCC-3.3.3 tarballs are available at
> ftp://gcc.gnu.org/pub/gcc/prerelease-3.3.3-20040210/
Here is something (fairly trivial) that I've been meaning to report
for several releases now. There are a few files in the archive with
inconsistent permissions:
$ tar tvfj gcc-3.3.3-20040210.tar.bz2|awk '{print $1}'|sort|uniq -c|sort -rn
15842 -rw-r--r--
457 drwxrwxrwx
81 -rwxr-xr-x
7 -rwxr-xr--
The first three categories are what you would expect, but the final
seven files are unusual: other users can't execute them. This causes
build failures if you have pristine world-readable source owned by one
ordinary user and build from it as another ordinary user. Admittedly
this is a unusual thing to do :-), but some of my autobuilders are
arranged like this.
The seven files in question are
-rwxr-xr-- gcc/config.guess
-rwxr-xr-- gcc/configure
-rwxr-xr-- gcc/fixproto
-rwxr-xr-- gcc/move-if-change
-rwxr-xr-- gcc/scan-types.sh
-rwxr-xr-- gcc/sort-protos
-rwxr-xr-- gcc/config/m88k/m88k-move.sh
I had an idea that a well-timed umask in the gcc_release script might
be relevant here, but perhaps just chmodding these few files,v on the
CVS server would be sufficient.
John "not a CVS expert"