Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer via buildroot <buildroot@buildroot.org>
To: yann.morin@orange.com
Cc: buildroot@busybox.net, Samuel Martin <s.martin49@gmail.com>
Subject: Re: [Buildroot] [PATCH v2 5/5] package/xz: convert to cmake build
Date: Wed, 26 Jun 2024 10:36:23 +0200	[thread overview]
Message-ID: <20240626103623.7d7412c0@gmx.net> (raw)
In-Reply-To: <Znql0FCAPG8jP+Lx@tl-lnx-nyma7486-2>

Hello Yann,

On Tue, 25 Jun 2024 13:11:12 +0200, yann.morin@orange.com wrote:

> Peter, All,
>
> On 2024-06-25 11:56 +0200, MORIN Yann INNOV/IT-S spake thusly:
> > On 2024-06-12 15:57 +0200, Peter Seiderer via buildroot spake thusly:
> > > Convert to cmake build with the following autoconf options without
> > > direct equivalent cmake option:
>
> The autotools build system is still operational, and still works. So,
> what was the rationale behind that change?
>
> Was that a defence against another backdooring attempt? If so, I think
> it should have been stated clearly in the commit log. Also, we can be as
> paranoid as we want, but it is possible to inject a similar backdoor
> in cmake as was injected in autotools, so switching to cmake just for
> this reason is not rally sufficient...

No, as the first suggestion ([1], marked as RFC - missed the RFC marking in
patch set version v2) predates the backdoor detection (but migrating away from
autoconf/automake was discusses as one measure for backdoor avoidance),
my motivation was the following passage from the NEWS file ([2]):

        - The CMake-based build is now close to feature parity with the
          Autotools-based build. Most importantly a few tests aren't
          run yet. Testing the CMake-based build on different operating
          systems would be welcome now. See the comment at the top of
          CMakeLists.txt.

And the amount of work done for the cmake build system seems to hint
that xz is moving away from autoconf/automake towards the cmake system...

>
> Note: the issue I hit can be solved by passing ENABLE_NLS=OFF in the
> host variant; we don't really require translations, so we can
> unconditionally turn it off.

Seems my intermediate step from 'package/xz: determine all autoconf options'
and '--enable-nls' unconditionally for the host variant was wrong...,
care to send a patch (as you can reproduce the failure)?

>
> However, we might hit a similar issue in target builds, and there, I am
> not sure what would be the best solution...

Already handled(?) in package/xz/xz.mk:

ifeq ($(BR2_SYSTEM_ENABLE_NLS),y)
XZ_CONF_OPTS += -DENABLE_NLS=ON
else
XZ_CONF_OPTS += -DENABLE_NLS=OFF
endif

Regards,
Peter

[1] https://lore.kernel.org/all/20240307165218.10027-4-ps.report@gmx.net/
[2] https://github.com/tukaani-project/xz/blob/master/NEWS

>
> Regards,
> Yann E. MORIN.
>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-06-26  8:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12 13:57 [Buildroot] [PATCH v2 1/5] package/xz: bump version to 5.4.7 Peter Seiderer via buildroot
2024-06-12 13:57 ` [Buildroot] [PATCH v2 2/5] package/xz: bump version to 5.6.2 Peter Seiderer via buildroot
2024-06-12 15:48   ` Julien Olivain
2024-06-24 13:42   ` Arnout Vandecappelle via buildroot
2024-06-12 13:57 ` [Buildroot] [PATCH v2 3/5] package/xz: determine all autoconf options Peter Seiderer via buildroot
2024-06-24 13:44   ` Arnout Vandecappelle via buildroot
2024-06-12 13:57 ` [Buildroot] [PATCH v2 4/5] package/xz: enable year2038 option Peter Seiderer via buildroot
2024-06-24 13:46   ` Arnout Vandecappelle via buildroot
2024-06-12 13:57 ` [Buildroot] [PATCH v2 5/5] package/xz: convert to cmake build Peter Seiderer via buildroot
2024-06-24 13:52   ` Arnout Vandecappelle via buildroot
2024-06-25  9:56   ` yann.morin
2024-06-25 11:11     ` yann.morin
2024-06-26  8:36       ` Peter Seiderer via buildroot [this message]
2024-06-26 19:32         ` Yann E. MORIN
2024-06-27  7:50           ` Peter Seiderer via buildroot
2024-06-27  7:57             ` Peter Seiderer via buildroot
2024-06-27  8:26             ` Peter Seiderer via buildroot
2024-06-27 11:16               ` yann.morin
2024-07-02 12:47                 ` Peter Seiderer via buildroot
2024-06-24 13:41 ` [Buildroot] [PATCH v2 1/5] package/xz: bump version to 5.4.7 Arnout Vandecappelle via buildroot
2024-07-08 10:04   ` Peter Korsgaard
2024-07-08 12:54     ` Peter Seiderer via buildroot
2024-07-08 12:57       ` Peter Seiderer via buildroot

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=20240626103623.7d7412c0@gmx.net \
    --to=buildroot@buildroot.org \
    --cc=buildroot@busybox.net \
    --cc=ps.report@gmx.net \
    --cc=s.martin49@gmail.com \
    --cc=yann.morin@orange.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox