From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [git commit] package/nettle: add missing dependency on host-m4
Date: Tue, 07 Nov 2023 22:48:28 +0100 [thread overview]
Message-ID: <87ttpxuteb.fsf@48ers.dk> (raw)
In-Reply-To: <20231101112613.2C68686320@busybox.osuosl.org> (Thomas Petazzoni via buildroot's message of "Wed, 1 Nov 2023 12:25:54 +0100")
>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:
> commit: https://git.buildroot.net/buildroot/commit/?id=d4ca1b03c0d6f34d10d10cab06ca28c24a7d296d
> branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
> nettle uses m4 during its build process. Without it, the build fails
> with:
> m4 ./m4-utils.m4 ./asm.m4 config.m4 machine.m4 aes-decrypt-internal.asm >aes-decrypt-internal.s
> /bin/sh: 1: m4: not found
> For the target package this is not visible, as the existing gmp
> dependency pulls in host-m4. But technically speaking, nettle needs
> host-m4 directly, so it makes sense to have this dependency.
> For the host package, it clearly fails to build, but probably isn't
> very visible as most systems have m4 installed system-wide: this was
> noticed when building inside Buildroot's minimal Docker
> container. There are no recorded autobuilder failures for this issue.
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Committed to 2023.02.x and 2023.08.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-11-07 21:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 11:25 [Buildroot] [git commit] package/nettle: add missing dependency on host-m4 Thomas Petazzoni via buildroot
2023-11-07 21:48 ` Peter Korsgaard [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=87ttpxuteb.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--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 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.