Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Guillaume Chaye <guillaume.chaye@zeetim.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCHv4 1/1] package/heimdal: upgrade package and add target support
Date: Sun, 18 May 2025 18:47:56 +0200	[thread overview]
Message-ID: <20250518184756.4a084524@windsurf> (raw)
In-Reply-To: <20250428154055.1402438-1-guillaume.chaye@zeetim.com>

Hello Guillaume,

On Mon, 28 Apr 2025 11:40:55 -0400
Guillaume Chaye <guillaume.chaye@zeetim.com> wrote:

> This patch does several things, so I will try to explain clearly what has been modified.
> 
> First, it bumps Heimdal to the latest commit (16/04/2025).
> The current version was more than 3 years old and had known CVEs (see CVE-2023-36328).
> This upgrade allows the removal of the two patches currently applied:
> - The commit 1b57b62, which fixes the build with autoconf 2.72, is already included upstream.
> - We no longer need to use the JSON-PP module, as it is now optional (commit 13d3bcf).
> 
> Heimdal was previously a host-only package. This patch adds target support.
> This requires cross-compiling the project, which was not possible without additional patches.
> After some research, I found this pull request (https://github.com/heimdal/heimdal/pull/1174)
> created by a well-known Heimdal contributor (Nico Williams).
> This pull request contains 29 commits, which is quite large, so I have tried to keep things simple
> by selecting only the minimal set of changes required for cross-compilation.
> 
> After extensive testing, I have successfully built the target version of Heimdal by applying 3 commits
> picked from the pull request:
> - The first one adds the AX_PROG_CC_FOR_BUILD macro to the project.
>   This macro, from the GNU project (https://www.gnu.org/software/autoconf-archive/ax_prog_cc_for_build.html),
>   allows detecting a C compiler that produces native executables.
> - The second commit integrates the AX_PROG_CC_FOR_BUILD macro into Heimdal's autoconf scripts,
>   enabling proper compiler selection during the build.
> - Finally, a patch was needed to fix header errors when cross-compiling libroken.
> 
> Additionally, I have added two patches I wrote and submitted upstream:
> - The first removes a hardcoded path from a script.
> - The second fixes an error generated by the 'ar' utility during the build process.
> 
> Finally, since the latest version of Heimdal no longer depends on e2fsprogs,
> the host-e2fsprogs dependency has been removed.
> 
> Signed-off-by: Guillaume Chaye <guillaume.chaye@zeetim.com>

Thanks for this new iteration. There is still too much in there, mixing
the bump and the addition of the target package.

Since the version bump made sense on its own, I extracted just this
aspect from your patch, and merged it:

  https://gitlab.com/buildroot.org/buildroot/-/commit/573ecbd44cd16b2ca4ce71b40459bcecf8c8e98c

For the rest, could you please:

- Provide a new patch with a commit message that's wrapped at 80
  columns and doesn't use first person sentence like "I have..."

- Justify why heimdal for the target is useful, i.e what will use it.

- Double check that the AX_PROG_CC_FOR_BUILD function in
  autoconf-archive really doesn't work? This would allow to avoid
  having another copy of it.

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2025-05-18 16:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-28 15:40 [Buildroot] [PATCHv4 1/1] package/heimdal: upgrade package and add target support Guillaume Chaye
2025-05-18 16:47 ` Thomas Petazzoni via buildroot [this message]

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=20250518184756.4a084524@windsurf \
    --to=buildroot@buildroot.org \
    --cc=guillaume.chaye@zeetim.com \
    --cc=thomas.petazzoni@bootlin.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