On 04/27/12 02:29 AM, Dr. Stephen Henson wrote:
Hmm never seen any error messages myself, using GNU tar 1.25.
The distribution tarballs are always created by doing:
make -f Makefile.org dist
from any source tree. As you can see from the files this makes use of "tar"
and "tardy". The tar version I used was GNU tar 1.25 and tardy version
1.20.D001. If someone can sugest alternative versions or options that will
avoid this in future I'll incorporate them into the distrubution.
Steve.
I know GNU tar sometimes produces archives the Sun version of tar can't open.
The GNU tar documentation
http://www.gnu.org/software/tar/manual/tar.html#SEC130
makes for interesting reading. Note this bit.
"The default format for GNU tar is defined at compilation time. You may check it
by running tar --help, and examining the last lines of its output. Usually, GNU
tar is configured to create archives in ‘gnu’ format, however, future version
will switch to ‘posix’."
See also
http://www.gnu.org/software/tar/manual/html_section/Portability.html
I also know that Joerg Schilling
http://en.wikipedia.org/wiki/J%C3%B6rg_Schilling
the author of cdrecord and mkisofs has been very critical of GNU tar. See for
ftp://ftp.berlios.de/pub/star/README.otherbugs
He has developed "star"
http://developer.berlios.de/projects/star
which he has said produces POSIX compliant tar files.
So if someone is running a non Linux system, it does not surprise me the GNU tar
is not working for them.
Given the POSIX standard has been out over a decade, perhaps you using the
option for posix, which GNU apparently intends using one day, might help.
But this topic does seem a bit of a can of worms.
Dave
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
