From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Ruschival <thomas@ruschival.de>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/pistache: enable on uClibc
Date: Sat, 6 Aug 2022 15:45:13 +0200 [thread overview]
Message-ID: <20220806154513.221975be@windsurf> (raw)
In-Reply-To: <20220805162906.GC3621445@scaer>
Hello,
On Fri, 5 Aug 2022 18:29:06 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> As I understand, this patch is not really upstreamable, or at least not
> in this state.
>
> However, this means we will have to carry over and over, because
> existing uclibc-based toolchains will still be usad in the future, even
> when newer uclibc-ng contains the new definitions, so we can't drop this
> patch because it may always needed when using external toolchains...
No, we will not have to carry it over and over. Regarding uClibc-ng, we
require using a reasonably recent version of uClibc-ng. So my plan
would be to keep this hack for a few months, until at least the Bootlin
uClibc toolchains are rebuilt with a recent enough uClibc-ng, and then
drop this hack.
So no, the goal is not to keep this hack patch forever.
What I'm proposing to do for pistache is exactly the same as I did in
commit fa4dba4aa202de20e3821eace5513aad81c23275, for openswan. Waldemar
was simply proposing to re-enable openswan for uClibc, because
uClibc-ng 1.0.41 has the necessary definitions. But in the immediate
term, that would have caused build break with Bootlin toolchains. So
until they are re-generated, I have added a hack patch that avoids the
uClibc build issue entirely, also with the goal of dropping the patch
when the toolchains are rebuilt.
> So, I think a version that is upstreamable would be nice...
I'm not sure it's worth the effort to introduce more complexity
upstream for this missing definition in uClibc. We should just fix it
in uClibc (I have already reported the issue), and that's it.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-08-06 13:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 20:35 [Buildroot] [PATCH 1/2] package/pistache: fix dependency on rapidjson Thomas Petazzoni via buildroot
2022-08-04 20:35 ` [Buildroot] [PATCH 2/2] package/pistache: enable on uClibc Thomas Petazzoni via buildroot
2022-08-05 16:29 ` Yann E. MORIN
2022-08-06 13:45 ` Thomas Petazzoni via buildroot [this message]
2022-08-06 14:15 ` Yann E. MORIN
2022-08-05 16:29 ` [Buildroot] [PATCH 1/2] package/pistache: fix dependency on rapidjson Yann E. MORIN
2022-09-14 9:46 ` Peter Korsgaard
2022-09-14 9:47 ` Peter Korsgaard
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=20220806154513.221975be@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=thomas@ruschival.de \
--cc=yann.morin.1998@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.