Linux / MacOS tar incompatibility - tarballs created on MacOS give errors when untarred in Linux

Question

When I tar up files on my Macbook and untar them in Linux, I repeatedly get the following warnings/errors:

 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: Error exit delayed from previous errors

Fortunately, this does NOT affect the files stored in the archive, which are restored perfectly. However, it does cause problems in a number of scenarios, especially when dealing with build processes where the non-zero failure code returned by 'tar' causes builds and installs to stop unnecessarily.

How can I get MacOS to build tar files that play nicely with the rest of the Linux world??

Also, for bonus points, there exists a publicly distributed tar file with these issues. Is there any way to get Linux to handle the tar file gracefully without changing the way it was originally compressed?

Answer 1

I googled for the error message and it seems like a BSD tar vs. GNU tar issue.

Install gnu tar if you can on MacOS and use that to create the tar.

Answer 2

okay, I used Google search, but top three link confirmed what I suspected
1. Bug in your tar AND/OR
2. Incompatibility between the two tar utilities
See this link. There someone reports that "Using "bsdtar -xvf" worked."
Edit : You are on Mac system, I thought other way round.
You will need to use gnutar, it should be installed already, if not get it installed.
Of course, you can look at other links by searching yourself :)