Problem with archiver (/usr/bin/ar)

I am having a strange problem with /usr/bin/ar on Mac-OSX 10.3.1.

On a local filesystem on the Mac it works fine:
[360spider:~/temp] epics% cc -c -o hello.o hello.c
[360spider:~/temp] epics% ar -rc hello.a hello.o

The archiver created hello.a with no problems.

However, now I go to a remote Linux NFS filesystem:
[360spider:~/temp] epics% cd /corvette/home/epics/scratch/
/corvette/home/epics/scratch
[360spider:home/epics/scratch] epics% cc -c -o hello.o hello.c
[360spider:home/epics/scratch] epics% ar -rc hello.a hello.o
^C

It compiles fine. However, the "ar" command just hangs up, it never
returns to the shell. I had to type ^C to kill it.

This file system is otherwise working fine. The UID/GID for the Mac
account have write permissions on the Linux system (otherwise the cc
command would fail).

Any idea what could be wrong? "man ar" says that it creates temporary
files in /tmp and uses the TMPDIR environment variable. That should
not be a problem, /tmp is writeable, and TMPDIR points to /tmp.

Thanks,
Mark Rivers

In article <62c206f3.0311221458.55a61fa7.DeleteThis@posting.google.com>,
rivers.DeleteThis@cars.uchicago.edu (Mark Rivers) wrote:

 > I am having a strange problem with /usr/bin/ar on Mac-OSX 10.3.1.
 >
 > On a local filesystem on the Mac it works fine:
 > [360spider:~/temp] epics% cc -c -o hello.o hello.c
 > [360spider:~/temp] epics% ar -rc hello.a hello.o
 >
 > The archiver created hello.a with no problems.
 >
 > However, now I go to a remote Linux NFS filesystem:
 > [360spider:~/temp] epics% cd /corvette/home/epics/scratch/
 > /corvette/home/epics/scratch
 > [360spider:home/epics/scratch] epics% cc -c -o hello.o hello.c
 > [360spider:home/epics/scratch] epics% ar -rc hello.a hello.o
 > ^C
 >
 > It compiles fine. However, the "ar" command just hangs up, it never
 > returns to the shell. I had to type ^C to kill it.
 >
 > This file system is otherwise working fine. The UID/GID for the Mac
 > account have write permissions on the Linux system (otherwise the cc
 > command would fail).

I wonder if you're running into Linux's problems with Panther's NFS file
locking. See
<http://www.macosxhints.com/article.php?story=20031028005216891&query=nfs
+lock> and
<http://nic.phys.ethz.ch/news/1067501462/1068541682/addPostingForm>
for details.

Hope this helps,
Eric

--
Eric Albert ejalbert.DeleteThis@stanford.edu
<a style='text-decoration: underline;' href="http://rescomp.stanford.edu/~ejalbert/" target="_blank">http://rescomp.stanford.edu/~ejalbert/</a><!-- ~MESSAGE_AFTER~ -->