From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mark Hatle <mark.hatle@kernel.crashing.org>,
Adrian Bunk <bunk@stusta.de>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/3] sanity: Add check for tar older than 1.28
Date: Thu, 21 Nov 2019 19:33:08 +0000 [thread overview]
Message-ID: <a41449c79577ce3dd1442d8c4cdefcc04bb74f05.camel@linuxfoundation.org> (raw)
In-Reply-To: <38e95272-cef4-e80a-456d-eb365a81e393@kernel.crashing.org>
On Thu, 2019-11-21 at 13:14 -0600, Mark Hatle wrote:
> On 11/21/19 12:09 PM, Richard Purdie wrote:
> > On Thu, 2019-11-21 at 19:09 +0200, Adrian Bunk wrote:
> > > On Thu, Nov 21, 2019 at 04:54:12PM +0000, Richard Purdie wrote:
> > > > Any suggestions on how we fix it?
> > >
> > > My preferred solution would be to replace CentOS 7 with CentOS 8
> > > as supported distribution, which would also allow to drop hacks
> > > for two major releases of gcc in various places.
> >
> > We are working towards that, equally the older version support is
> > useful to a significant portion of our userbase so its a balancing
> > act.
>
> RHEL 7 is still heavily used. But if we can provide a buildtools-
> tarball that includes a new enough tar, that should be able to
> workaround the issue.
After some discussion, this is the direction we've gone. Debian 8 also
has the issue. On the autobuilder we've installed buildtools-tarball on
that and the Centos7 workers.
> > > If all other supported distribution already ship 1.28 this would
> > > solve your problem.
> >
> > I believe that is now the case, yes.
> >
> > > > (We could make opkg-utils-native depend on tar-native but for
> > > > most
> > > > people that isn't necessary so it seems a shame).
> > >
> > > Building tar-native is not something that would strike me as
> > > problematic.
> >
> > Its an extra build dependency and extra build time, just
> > complicates
> > things. "tar-native" is in ASSUME_PROVIDED and gives bootstrap
> > issues
> > although we have the "tar-replacement-native" mechanism to account
> > for
> > this already. So possible but not entirely straightforward.
For fun I tried this. It exploded in circular dependency problems :(.
> Requiring a newer version, and suggesting to the user to use a
> buildtools-tarball (SDK) I think is a reasonable compromise.
Agreed, we reached the same conclusion. I'll tweak the patch to improve
the error message to the user.
Cheers,
Richard
next prev parent reply other threads:[~2019-11-21 19:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 15:02 [PATCH 1/3] opkg: Add upstream fixes Richard Purdie
2019-11-21 15:02 ` [PATCH 2/3] opkg-utils: Fix silent empty/broken opkg package creation Richard Purdie
2019-11-21 15:02 ` [PATCH 3/3] sanity: Add check for tar older than 1.28 Richard Purdie
2019-11-21 15:50 ` Adrian Bunk
2019-11-21 16:54 ` Richard Purdie
2019-11-21 17:02 ` Alexander Kanavin
2019-11-21 17:09 ` Adrian Bunk
2019-11-21 18:09 ` Richard Purdie
2019-11-21 19:14 ` Mark Hatle
2019-11-21 19:33 ` Richard Purdie [this message]
2019-11-22 0:27 ` [PATCH 1/3] opkg: Add upstream fixes Khem Raj
2019-11-22 8:58 ` Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a41449c79577ce3dd1442d8c4cdefcc04bb74f05.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bunk@stusta.de \
--cc=mark.hatle@kernel.crashing.org \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox