From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/exim: do not build perl-based utilities
Date: Thu, 28 Dec 2023 10:02:57 +0100 [thread overview]
Message-ID: <20231228100257.20128a04@booty> (raw)
In-Reply-To: <20231227181756.156827-2-bernd@kuhls.net>
Hello Bernd,
[+Cc Yann]
On Wed, 27 Dec 2023 19:17:56 +0100
Bernd Kuhls <bernd@kuhls.net> wrote:
> Upstream added various utilities, for example exim_id_update
> with commit https://github.com/Exim/exim/commit/46a36afae41f63de654269c8a0b7cf5852a85a14
> which is a "Utility for one-time upgrage/downgrade between exim message-
> id formats, around the 4.97 transition" which would add a dependency to
> host-perl/perl so we build only the exim binary.
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> ---
> package/exim/exim.mk | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/package/exim/exim.mk b/package/exim/exim.mk
> index 30b0d78c94..1b3295697e 100644
> --- a/package/exim/exim.mk
> +++ b/package/exim/exim.mk
> @@ -146,16 +146,15 @@ define EXIM_BUILD_CMDS
> CFLAGS="-std=c99 $(HOST_CFLAGS)" \
> LFLAGS="-fPIC $(HOST_LDFLAGS)"
> $(TARGET_MAKE_ENV) build=br $(MAKE) -C $(@D) $(EXIM_STATIC_FLAGS) \
> - CFLAGS="-std=c99 $(TARGET_CFLAGS) $(EXIM_C_FLAGS)"
> + CFLAGS="-std=c99 $(TARGET_CFLAGS) $(EXIM_C_FLAGS)" exim
> endef
>
> # Need to replicate the LFLAGS in install, as exim still wants to build
> # something when installing...
> define EXIM_INSTALL_TARGET_CMDS
> - DESTDIR=$(TARGET_DIR) INSTALL_ARG="-no_chown -no_symlink" build=br \
> - $(MAKE) -C $(@D) $(EXIM_STATIC_FLAGS) \
> - CFLAGS="-std=c99 $(TARGET_CFLAGS)" \
> - install
> + cd $(@D)/build-br; \
> + DESTDIR=$(TARGET_DIR) build=br \
> + ../scripts/exim_install -no_chown -no_symlink exim
> chmod u+s $(TARGET_DIR)/usr/sbin/exim
> endef
I like this complete rewrite of the install commands, which get rid of
the utterly complex installation step currently in place. However I'd
have mentioned this in the commit log, including a mention of the
checks done to ensure this is still installing whatever is
actually needed.
Also, the comment about the LFLAGS, added by Yann in [0], should be
removed as it it does not apply anymore.
[0]
https://git.busybox.net/buildroot/commit/?id=bf22cea53fa2af48bde3010673d3babee1ae6873
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-12-28 9:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 18:17 [Buildroot] [PATCH 1/2] package/exim: fix build with libexecinfo Bernd Kuhls
2023-12-27 18:17 ` [Buildroot] [PATCH 2/2] package/exim: do not build perl-based utilities Bernd Kuhls
2023-12-28 9:02 ` Luca Ceresoli via buildroot [this message]
2023-12-28 8:51 ` [Buildroot] [PATCH 1/2] package/exim: fix build with libexecinfo Luca Ceresoli via buildroot
2023-12-29 21:56 ` Yann E. MORIN
2024-01-02 7:13 ` Luca Ceresoli 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=20231228100257.20128a04@booty \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=luca.ceresoli@bootlin.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox