Faile build because of tar incompatibility

157 views
Skip to first unread message

Boris Vinarsky

unread,
Feb 2, 2015, 9:09:27 PM2/2/15
to sage-s...@googlegroups.com
I tried to compile source 6.4.1 on RHEL 5.8. Compile failed because it could not untar  file sage-6.4.1/upstream/sagenb-0.11.1.tar
Here are error messages:

==========Start of Error Messages=====================

Found local metadata for sagenb-0.11.1

Found local sources at

/nfs/downloads/XFER/Sage/source/sage-6.4.1/upstream/sagenb-0.11.1.tar

Checksum: eb4fd89c8c907171a098fa6f06891bd8 vs

eb4fd89c8c907171a098fa6f06891bd8

sagenb-0.11.1

====================================================

Setting up build directory for sagenb-0.11.1

tar: Ignoring unknown extended header keyword `LIBARCHIVE.creationtime'

tar: Ignoring unknown extended header keyword `SCHILY.dev'

tar: Ignoring unknown extended header keyword `SCHILY.ino'

tar: Ignoring unknown extended header keyword `SCHILY.nlink'

tar: Ignoring unknown extended header keyword `LIBARCHIVE.creationtime'

tar: Ignoring unknown extended header keyword `SCHILY.dev'

tar: Ignoring unknown extended header keyword `SCHILY.ino'

tar: Ignoring unknown extended header keyword `SCHILY.nlink'

tar: Ignoring unknown extended header keyword `LIBARCHIVE.creationtime'

tar: Ignoring unknown extended header keyword `SCHILY.dev'

tar: Ignoring unknown extended header keyword `SCHILY.ino'

tar: Ignoring unknown extended header keyword `SCHILY.nlink'

tar: Ignoring unknown extended header keyword `SCHILY.dev'

tar: Ignoring unknown extended header keyword `SCHILY.ino'

tar: Ignoring unknown extended header keyword `SCHILY.nlink'

tar: Ignoring unknown extended header keyword `SCHILY.dev'

tar: Ignoring unknown extended header keyword `SCHILY.ino'

tar: Ignoring unknown extended header keyword `SCHILY.nlink'

tar: Ignoring unknown extended header keyword `SCHILY.dev'

tar: Ignoring unknown extended header keyword `SCHILY.ino'

tar: Ignoring unknown extended header keyword `SCHILY.nlink'

tar: Ignoring unknown extended header keyword `SCHILY.dev'

tar: Ignoring unknown extended header keyword `SCHILY.ino'

tar: Ignoring unknown extended header keyword `SCHILY.nlink'

tar: Ignoring unknown extended header keyword `SCHILY.dev'

tar: Ignoring unknown extended header keyword `SCHILY.ino'

tar: Ignoring unknown extended header keyword `SCHILY.nlink'

tar: Ignoring unknown extended header keyword `LIBARCHIVE.creationtime'

tar: Ignoring unknown extended header keyword `SCHILY.dev'

tar: Ignoring unknown extended header keyword `SCHILY.ino'

tar: Ignoring unknown extended header keyword `SCHILY.nlink'

tar: Ignoring unknown extended header keyword `SCHILY.dev'

tar: Ignoring unknown extended header keyword `SCHILY.ino'

tar: Ignoring unknown extended header keyword `SCHILY.nlink'

tar: Ignoring unknown extended header keyword `SCHILY.dev'

tar: Ignoring unknown extended header keyword `SCHILY.ino'

tar: Ignoring unknown extended header keyword `SCHILY.nlink'

tar: Ignoring unknown extended header keyword `LIBARCHIVE.creationtime'

tar: Ignoring unknown extended header keyword `SCHILY.dev'

tar: Ignoring unknown extended header keyword `SCHILY.ino'

tar: Ignoring unknown extended header keyword `SCHILY.nlink'

tar: Ignoring unknown extended header keyword `LIBARCHIVE.creationtime'

tar: Ignoring unknown extended header keyword `SCHILY.dev'

tar: Ignoring unknown extended header keyword `SCHILY.ino'

tar: Ignoring unknown extended header keyword `SCHILY.nlink'

tar: Ignoring unknown extended header keyword `SCHILY.dev'

tar: Ignoring unknown extended header keyword `SCHILY.ino'

tar: Ignoring unknown extended header keyword `SCHILY.nlink'

tar: Ignoring unknown extended header keyword `LIBARCHIVE.creationtime'

tar: Ignoring unknown extended header keyword `SCHILY.dev'

tar: Ignoring unknown extended header keyword `SCHILY.ino'

tar: Ignoring unknown extended header keyword `SCHILY.nlink'

tar: Ignoring unknown extended header keyword `LIBARCHIVE.creationtime'

tar: Ignoring unknown extended header keyword `SCHILY.dev'

tar: Ignoring unknown extended header keyword `SCHILY.ino'

tar: Ignoring unknown extended header keyword `SCHILY.nlink'

tar: Ignoring unknown extended header keyword `LIBARCHIVE.creationtime'

tar: Ignoring unknown extended header keyword `SCHILY.dev'

tar: Ignoring unknown extended header keyword `SCHILY.ino'

tar: Ignoring unknown extended header keyword `SCHILY.nlink'

tar: Ignoring unknown extended header keyword `LIBARCHIVE.creationtime'

tar: Ignoring unknown extended header keyword `SCHILY.dev'

tar: Ignoring unknown extended header keyword `SCHILY.ino'

tar: Ignoring unknown extended header keyword `SCHILY.nlink'

tar: Error exit delayed from previous errors

Error: failed to extract

/nfs/downloads/XFER/Sage/source/sage-6.4.1/upstream/sagenb-0.11.1.tar

make[2]: ***

[/nfs/downloads/XFER/Sage/source/sage-6.4.1/local/var/lib/sage/installed/sagenb-0.11.1]

Error 1

make[2]: Leaving directory

`/nfs/downloads/XFER/Sage/source/sage-6.4.1/build'

make[1]: *** [all] Error 2

make[1]: Leaving directory

`/nfs/downloads/XFER/Sage/source/sage-6.4.1/build'

 

real    210m7.185s

user    173m19.083s

sys     18m48.202s

***************************************************************

Error building Sage.

 

The following package(s) may have failed to build:

 

package: sagenb-0.11.1

log file:

/nfs/downloads/XFER/Sage/source/sage-6.4.1/logs/pkgs/sagenb-0.11.1.log

build directory:

/nfs/downloads/XFER/Sage/source/sage-6.4.1/local/var/tmp/sage/build/sagenb-0.11.1

 

The build directory may contain configuration files and other potentially helpful information. WARNING: if you now run 'make' again, the build directory will, by default, be deleted. Set the environment variable SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.

 

make: *** [build] Error 1

==========End of Error Massages================

Note that these are tar errors.

I untarred that file using Windows Subsystem for UNIX-based applications, transferred to RHEL, tarred there, replaced offending file along with md5sum, and pushed forward.


I wonder if it possible to use more commonly available tar command when forming source package.


Boris Vinarsky


kcrisman

unread,
Feb 2, 2015, 11:02:45 PM2/2/15
to sage-s...@googlegroups.com
I untarred that file using Windows Subsystem for UNIX-based applications, transferred to RHEL, tarred there, replaced offending file along with md5sum, and pushed forward.


I wonder if it possible to use more commonly available tar command when forming source package.


This should be fixed in Sage 6.5 by http://trac.sagemath.org/ticket/17490 and all future sagenb packages - instructions for sagenb release explicitly now include request for gnu tar not bsd tar.  Thanks for the report!
Reply all
Reply to author
Forward
0 new messages