On Fri, Apr 27, 2012, Dr. David Kirkby wrote: > 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?." >
Hmm... the puzzle continues. The versions of tar and tardy match those on the OpenSSL development machine and have tghe same default but those seem fine with the version of tar on Solaris whereas those produced on my setup (Ubuntu 11.10) produce an unexpected EOF message. Investigations continue... Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
