From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Bernd Kuhls <bernd@kuhls.net>,
Luca Ceresoli <luca.ceresoli@bootlin.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH v2 1/2] package/exim: fix build with libexecinfo
Date: Sat, 13 Jan 2024 16:11:00 +0100 [thread overview]
Message-ID: <87cyu5tgjf.fsf@48ers.dk> (raw)
In-Reply-To: <20240106111236.6269f39d@windsurf> (Thomas Petazzoni via buildroot's message of "Sat, 6 Jan 2024 11:12:36 +0100")
>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:
> Hello,
> On Wed, 3 Jan 2024 20:11:50 +0100
> Bernd Kuhls <bernd@kuhls.net> wrote:
>> diff --git a/package/exim/exim.mk b/package/exim/exim.mk
>> index fb9eecd71b..25d171875d 100644
>> --- a/package/exim/exim.mk
>> +++ b/package/exim/exim.mk
>> @@ -104,6 +104,7 @@ define EXIM_CONFIGURE_TOOLCHAIN
>> $(call exim-config-add,HOSTCC,$(HOSTCC))
>> $(call exim-config-add,HOSTCFLAGS,$(HOSTCFLAGS))
>> $(EXIM_FIX_IP_OPTIONS_FOR_MUSL)
>> + $(EXIM_EXTRALIBS)
> I've changed this to:
> + $(call exim-config-add,EXTRALIBS,$(EXIM_EXTRALIBS))
>> +ifeq ($(BR2_PACKAGE_LIBEXECINFO),y)
>> +EXIM_DEPENDENCIES += libexecinfo
>> +define EXIM_EXTRALIBS
>> +$(call exim-config-add,EXTRALIBS,-lexecinfo)
>> +endef
>> +else ifneq ($(BR2_TOOLCHAIN_USES_GLIBC),y)
>> +EXIM_C_FLAGS = -DNO_EXECINFO
>> +endif
> And changed this to:
> +ifeq ($(BR2_PACKAGE_LIBEXECINFO),y)
> +EXIM_DEPENDENCIES += libexecinfo
> +EXIM_EXTRALIBS += -lexecinfo
> +else ifeq ($(BR2_TOOLCHAIN_USES_GLIBC),)
> +EXIM_CFLAGS = -DNO_EXECINFO
> +endif
> so EXIM_EXTRALIBS becomes really the list of extra libraries, and the
> exim-config-add call is inside EXIM_CONFIGURE_TOOLCHAIN. This means
> that we can add more things to EXIM_EXTRALIBS for other reasons if
> needed in the future.
> Also, I've used EXIM_CFLAGS instead of EXIM_C_FLAGS, and used a
> slightly different construct for the glibc condition.
> Applied with those changes, thanks a lot!
Committed to 2023.02.x and 2023.11.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-01-13 15:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 19:11 [Buildroot] [PATCH v2 1/2] package/exim: fix build with libexecinfo Bernd Kuhls
2024-01-03 19:11 ` [Buildroot] [PATCH v2 2/2] package/exim: do not build perl-based utilities Bernd Kuhls
2024-01-06 10:12 ` Thomas Petazzoni via buildroot
2024-01-13 15:10 ` Peter Korsgaard
2024-01-06 10:12 ` [Buildroot] [PATCH v2 1/2] package/exim: fix build with libexecinfo Thomas Petazzoni via buildroot
2024-01-13 15:11 ` 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=87cyu5tgjf.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=bernd@kuhls.net \
--cc=buildroot@buildroot.org \
--cc=luca.ceresoli@bootlin.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