The original article is included at the end of this message.
I received replies from:
Neil Dyce <nd_at_siva.bris.ac.uk>
Dave Golden <golden_at_falcon.invincible.com>
Winfried Huber <win_at_tukan.ffb.eunet.de>
Tim Mooney <mooney_at_dogbert.cc.ndsu.NoDak.edu>
Serge Munhoven <munhoven_at_olive.msm.ulg.ac.be>
Dave Newbold <phdmn_at_siva.bris.ac.uk>
Juerg Staub <jst_at_atb.ch>
Thanks to these people.
The problem was that there was insuffient space on /tmp. The workaround
was to set TMPDIR to point to an area with more space.
DEC have been informed of the cryptic error message and its cause.
Other notes on this problem:
1. An alternative to defining TMPDIR is to use the -l switch to
place temporary files in the local directory. However,
if that directory is NFS-mounted, it may increase
the archiving time considerably.
2. The GNU binutils comes with a new improved version of ar
available at prep.ai.mit.edu. We didn't try this.
3. There is a patch (OSF350-049) that patches ar, nm and odump.
It doesn't mention this problem, but we haven't applied
it to find out if the error message has become less elusive.
Cheers,
Michael
Original article:
We're running release V3.2 148 of OSF. We are having problems creating
an archive of 207 object files to link against. The command and output
we get is:
ar -rc test.a *.o
ar: error writing archive member contents: Bad file number
If the files are added 10 at a time, there are no problems until there
are 60, then adding the next 10 we get the error:
ar: error writing archive member contents: No such file or directory
After trying to add all 207, an ar -t test.a lists 160 files.
Is this a known problem or are we doing something wrong? Is there a
workaround?
Thanks in advance,
Michael
Received on Tue May 14 1996 - 03:56:19 NZST