Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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/1] package/libdill: fix build with gcc-15.x
Date: Thu, 1 Jan 2026 16:01:19 +0100	[thread overview]
Message-ID: <20260101160119.16a2ec03@windsurf> (raw)
In-Reply-To: <20251026143916.3901096-1-bernd@kuhls.net>

Hello Bernd,

On Sun, 26 Oct 2025 15:39:16 +0100
Bernd Kuhls <bernd@kuhls.net> wrote:

> Updated project URL: https://github.com/sustrik/libdill/pull/228

This should have been a separate commit.

> Adding -std=gnu17 was recommended in upstream PR:
> https://github.com/sustrik/libdill/issues/229#issuecomment-2865524080
> 
> Fixes:
> https://autobuild.buildroot.net/results/1a5/1a5e9d7df6c83a921cae39b4dc4b601be4d18e36/
> 
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>

I wanted to test your patch, but libdill doesn't build for me, even
before the gcc 15.x issue, I get an issue during autoreconf:

configure.ac:59: warning: The macro 'AC_PROG_CC_C99' is obsolete.
configure.ac:59: You should run autoupdate.
./lib/autoconf/c.m4:1662: AC_PROG_CC_C99 is expanded from...
configure.ac:59: the top level
configure.ac:210: warning: AC_OUTPUT should be used without arguments.
configure.ac:210: You should run autoupdate.
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
autoreconf: error: /home/thomas/projets/buildroot/output-dill/host/bin/autoconf failed with exit status: 1
make: *** [package/pkg-generic.mk:262: /home/thomas/projets/buildroot/output-dill/build/libdill-32d0e8b733416208e0412a56490332772bc5c6e1/.stamp_configured] Error 1
make: Leaving directory '/home/thomas/projets/buildroot'

I would suggest to drop the package. Last tag in February 2019, last
commit in Aug 2022 (and it was following a patch submitted by Fabrice
Fontaine), and before that previous commit in 2021. Lots of issues
opened.

So I think dropping the package is the right thing to do. Do you want
to send such a patch?

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

      reply	other threads:[~2026-01-01 15:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-26 14:39 [Buildroot] [PATCH 1/1] package/libdill: fix build with gcc-15.x Bernd Kuhls
2026-01-01 15:01 ` 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=20260101160119.16a2ec03@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