From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org,
Angelo Compagnucci <angelo.compagnucci@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/3] package/libdill: autoreconf needs host-pkgconf
Date: Thu, 1 Jan 2026 23:32:18 +0100 [thread overview]
Message-ID: <20260101233218.0c991340@windsurf> (raw)
In-Reply-To: <20260101180045.247057-1-bernd@kuhls.net>
On Thu, 1 Jan 2026 19:00:43 +0100
Bernd Kuhls <bernd@kuhls.net> wrote:
> Fixes error during autoreconf when openssl is not selected:
>
> configure.ac:119: error: possibly undefined macro: AC_CHECK_LIB
> If this token and others are legitimate, please use m4_pattern_allow.
> See the Autoconf documentation.
> configure.ac:127: error: possibly undefined macro: AC_MSG_ERROR
>
> As it turns out adding host-pkgconf as mandatory dependency fixes the
> problem.
Ah indeed, host-pkgconf! Thanks for coming up so quickly with an
improved patch.
However, since when this problem is happening? Again, need to
understand if this needs to be backported to LTS or not.
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-01-01 22:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-01 18:00 [Buildroot] [PATCH 1/3] package/libdill: autoreconf needs host-pkgconf Bernd Kuhls
2026-01-01 18:00 ` [Buildroot] [PATCH 2/3] package/libdill: update project URL Bernd Kuhls
2026-01-01 22:32 ` Thomas Petazzoni via buildroot
2026-01-13 19:47 ` Arnout Vandecappelle via buildroot
2026-01-01 18:00 ` [Buildroot] [PATCH 3/3] package/libdill: fix build with gcc-15.x Bernd Kuhls
2026-01-01 22:32 ` Thomas Petazzoni via buildroot [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=20260101233218.0c991340@windsurf \
--to=buildroot@buildroot.org \
--cc=angelo.compagnucci@gmail.com \
--cc=bernd@kuhls.net \
--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