I got one reply - from Jon Reeves <reeves_at_zk3.dec.com>:
> Do you have the sources to libfaxserver.a? We've seen ar seg fault in the
> past when one of the .o files in an archive is corrupted; one common cause
> of corruption is using NFS filesystems in soft (known to some of our NFS
> engineers as "corrupt") mode. If you don't have the sources, you might also
> try using ar x to extract all the .o files, then rebuild, possibly isolating
> the bad file.
ar can core dump if an archive is corrupted.
I tried ar x and other options, but all core dumped. I then deleted
the archive and objects and tried to rebuild. Turns out the /tmp
file system was too small, and that the .a file wasn't created successfully.
Using a bigger /tmp (using mfs) the build completed successfully.
Thanks a lot, Jon!
Regards,
Terje
--
Terje Sten Bjerkseth <tsb_at_admintec.no>, AdminTec a.s, Postboks 241,
N-3201 Sandefjord, Norway, +47 33 47 03 20, faks +47 33 47 05 45.
Vi har levert AT-systemer siden 1978! For informasjon: info_at_admintec.no.
Received on Tue Apr 18 1995 - 05:30:02 NZST