[PATCH] build: Use Python tarfile instead of pax

[Joel Sherrill]

On Wed, Aug 19, 2020 at 8:38 AM Sebastian Huber <
sebastian.huber at embedded-brains.de> wrote:

> On 19/08/2020 14:44, Joel Sherrill wrote:
>
> > On Tue, Aug 18, 2020 at 5:52 PM Chris Johns <chrisj at rtems.org
> > <mailto:chrisj at rtems.org>> wrote:
> >
> >     On 18/8/20 9:16 pm, Sebastian Huber wrote:
> >     > This patch is for the new build system.
> >
> >     <stand><clap><clap><clap>
> >
> >     Looking forward to this change.
> >
> >
> > Me too.
> >
> > We determined that the Python tar defaulted to " POSIX.1-2001 (pax)
> > format"
> > which is newer than the "IEEE Std 1003.2 (“POSIX.2”)" from the pax man
> > page as ustar as best I can tell.
>
> I was not really sure which format we need. The
>
> +            tar = tarfile.TarFile(
> +                task.outputs[0].abspath(), "w",
> format=tarfile.USTAR_FORMAT
> +            )
>
> seems to work.
>

And that is my concern. If you switched to Python tar but didn't change
the format from the 1988 USTAR to the 2001 PAX tar, then we didn't
fix the bug. I think the RTEMS side has to be updated to understand
the 2001 header also.

--joel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20200819/b539b0ab/attachment-0001.html>