From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH/next 1/1] package/pppd: bump to version 2.4.9
Date: Sun, 14 Nov 2021 14:33:53 +0100 [thread overview]
Message-ID: <20211114143353.0dfd4592@windsurf> (raw)
In-Reply-To: <20211114113310.1304245-1-fontaine.fabrice@gmail.com>
On Sun, 14 Nov 2021 12:33:10 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> - Drop patch (already in version)
> - Update hash of bsd-comp.c, ccp.c and passprompt.c (no change in
> license)
> - rp-pppoe has been renamed to pppoe since
> https://github.com/paulusmack/ppp/commit/b2c36e6c0e1655aea9b1b0a03a8160f42a26c884
> - Manage EAP-TLS which depends on openssl and has been added and is
> enabled by default since
> https://github.com/paulusmack/ppp/commit/e87fe1bbd37a1486c5223f110e9ce3ef75971f93
I am rather confused by this, especially since you're changing pppd.mk,
but not the Config.in that has some funky logic:
select BR2_PACKAGE_OPENSSL if BR2_TOOLCHAIN_USES_GLIBC
select BR2_PACKAGE_LIBOPENSSL_ENABLE_DES if BR2_PACKAGE_LIBOPENSSL \
&& BR2_TOOLCHAIN_USES_GLIBC
Could you explain a bit more how this is intended to work, and what is
the logic/rationale ?
Also, I've tested and this 2.4.9 version of pppd build fine with musl,
so:
depends on !BR2_TOOLCHAIN_USES_MUSL # Use __P() macro all over the tree
could be dropped.
Thanks,
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:[~2021-11-14 13:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 11:33 [Buildroot] [PATCH/next 1/1] package/pppd: bump to version 2.4.9 Fabrice Fontaine
2021-11-14 13:33 ` Thomas Petazzoni [this message]
2021-11-14 16:20 ` Fabrice Fontaine
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=20211114143353.0dfd4592@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
/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.