From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Alexey Lukyanchuk <skif@skif-web.ru>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/zabbix: fix BR2_SHARED_STATIC_LIBS
Date: Tue, 7 Feb 2023 23:53:40 +0100 [thread overview]
Message-ID: <20230207225340.GE2817@scaer> (raw)
In-Reply-To: <20220531190702.107175-1-fontaine.fabrice@gmail.com>
Fabrice, All,
This patch has now reached the infamous status of being the oldest patch
in our backlog... Sorry for that. :-(
On 2022-05-31 21:07 +0200, Fabrice Fontaine spake thusly:
> --static is added to pkg-config call with BR2_SHARED_STATIC_LIBS
As already noticed by Thomas, this is not correct.
In fact, zabix uses custom --enable-{stati,shared} options, instead of
usingthe standard libtool directives:
1276 AC_ARG_ENABLE(static,[ --enable-static Build statically linked binaries],
1277 [case "${enableval}" in
1278 yes)
1279 LDFLAGS="${LDFLAGS} -static"
1280 AC_MSG_CHECKING(if static linking is possible)
This is where your -static is coming from, and is causing those issues.
So, your fix is technically correct (but see below), but for the wrong
reasons.
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/zabbix/zabbix.mk | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/package/zabbix/zabbix.mk b/package/zabbix/zabbix.mk
> index adc54028ad..85fd193b4d 100644
> --- a/package/zabbix/zabbix.mk
> +++ b/package/zabbix/zabbix.mk
> @@ -125,6 +125,13 @@ endif
>
> endif # BR2_PACKAGE_ZABBIX_SERVER
>
> +# With BR2_SHARED_STATIC_LIBS=y, the generic infrastructure adds
> +# --static when calling pkg-config resulting in a build failure with
You'll also need to update that comment, of course.
Can you fix the commit log and the comment, and respin, please?
Again, sorry for the ong delay...
Regards,
Yann E. MORIN.
> +# libcurl or openssl. Adding --disable-static reverts this
> +ifeq ($(BR2_SHARED_STATIC_LIBS),y)
> +ZABBIX_CONF_OPTS += --disable-static
> +endif
> +
> define ZABBIX_INSTALL_INIT_SYSTEMD
> $(foreach unit,$(ZABBIX_SYSTEMD_UNITS),\
> $(INSTALL) -D -m 0644 $(ZABBIX_PKGDIR)/$(unit) $(TARGET_DIR)/usr/lib/systemd/system/$(unit) && \
> --
> 2.35.1
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-02-07 22:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 19:07 [Buildroot] [PATCH 1/1] package/zabbix: fix BR2_SHARED_STATIC_LIBS Fabrice Fontaine
2022-06-01 12:27 ` Thomas Petazzoni via buildroot
2022-06-01 19:13 ` Fabrice Fontaine
2023-02-07 22:53 ` Yann E. MORIN [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=20230207225340.GE2817@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=skif@skif-web.ru \
/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