Re: Building v1.6

[Pat Villani <patv@unx.dec.com> writes:]

>I'm having some trouble with the latest release. Aside from a missing
>mkall, it looks like gcc always fails with a perm error. This error occurs
>in the lib directory.

Hmmm... could you "stat /vsta/src/lib" and see what it says?

>Permissions seem ok and relative directories are in place, i.e.,
>../../include exists. If I copy a small, stand alone file to /vsta/src/lib
>and compile it there, it compiles fine yet if I try to compile any VSTa
>file through the makefile or by hand I get the perm error.

Can you use "gcc -v" and see more about exactly where it's dying?

I've now reproduced a misbehavior where "tar" somehow ends up with a
unwritable chmod mask when creating directories. I hadn't brought along
the sources to tar on the laptop at hand, so I'll nail this now that I'm
back from vacation.

For now you might cd to /vsta and do a "rh -e '((mode & IFMT) == IFDIR) &&
!(mode & 0222)' to see what directories have no write access, then do
a chmod 777 <list> to make them writable.

                                                        Andy
Received on Sun Oct 19 09:28:51 1997