From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
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: add missing BR2_OPTIMIZE_FAST
Date: Thu, 2 Nov 2023 19:05:40 +0100 [thread overview]
Message-ID: <20231102190540.5e8114ad@windsurf> (raw)
In-Reply-To: <20231015212242.1600362-1-fontaine.fabrice@gmail.com>
On Sun, 15 Oct 2023 23:22:42 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Add missing BR2_OPTIMIZE_FAST dependency to BR2_PACKAGE_ZABBIX_SERVER
> to avoid the following build failure raised since commit
> e702a05d8998a1f2416225eb62b43b6585738fe9:
>
> checking for Zabbix server/proxy database selection... error
> configure: error: No database selected for Zabbix server/proxy. Use --with-mysql or --with-oracle or --with-postgresql or --with-sqlite3.
>
> Fixes:
> - http://autobuild.buildroot.org/results/ab403b45761c82f49a9380564bf10d3e7ae935f2
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/zabbix/Config.in | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Good catch, applied to master. I must say I really hate the fact that
these dependencies must be duplicated between the main
BR2_PACKAGE_ZABBIX_SERVER option and the sub-options to select
mysql/postgresql backends.
Thanks!
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
next prev parent reply other threads:[~2023-11-02 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-15 21:22 [Buildroot] [PATCH 1/1] package/zabbix: add missing BR2_OPTIMIZE_FAST Fabrice Fontaine
2023-11-02 18:05 ` Thomas Petazzoni via buildroot [this message]
2023-11-08 13:41 ` Peter Korsgaard
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=20231102190540.5e8114ad@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=skif@skif-web.ru \
--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