From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/ccrypt: fix build with GCC 15 on musl
Date: Mon, 26 Oct 2026 22:51:02 +0100 [thread overview]
Message-ID: <at_LGuRSbDPCUp60@windsurf> (raw)
In-Reply-To: <20261026135226.1614907-1-yegorslists@googlemail.com>
On Mon, Oct 26, 2026 at 02:52:26PM +0100, Yegor Yefremov via buildroot wrote:
> When cross-compiling, ccrypt's configure can't run its getopt_long
> test and always falls back to the bundled getopt. Its getopt.h only
> prototypes getopt() when __GNU_LIBRARY__ is defined (glibc, uClibc),
> so on musl it declares "extern int getopt ();", and getopt.c declares
> "extern char *getenv ();". GCC 15 defaults to C23, where an empty
> parameter list means (void), so the build fails:
>
> unistd.h:127:5: error: conflicting types for 'getopt'; have 'int(int, char * const*, const char *)'
> ./include/getopt/getopt.h:150:12: note: previous declaration of 'getopt' with type 'int(void)'
> getopt.c:404:21: error: too many arguments to function 'getenv'; expected 0, have 1
>
> Add a patch that always uses the full POSIX prototype for getopt()
> and gives getenv() its standard prototype.
>
> This issue has been present since commit 75891397abe6 ("package/gcc:
> add support for GCC 15.x"), which made a C23-by-default compiler
> available. It therefore affects 2025.08 and later, including the
> 2026.02.x LTS branch.
>
> Fixes:
> https://autobuild.buildroot.org/results/dd2b362542488a306a523fa05dedc859dfb0cf7e
>
> Fixes: 75891397abe60dbe3d82a1ec39654ff81d1b1406 ("package/gcc: add support for GCC 15.x")
> Assisted-by: Claude:claude-opus-5-5
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
Applied to master, thanks! To be honest, I'm not sure we should keep
ccrypt. No release since 2018... for a crypto related program. That
doesn't smell like a very active/maintained project.
Best regards,
Thomas Petazzoni
--
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
next prev parent reply other threads:[~2026-10-26 21:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 13:52 [Buildroot] [PATCH] package/ccrypt: fix build with GCC 15 on musl Yegor Yefremov via buildroot
2026-10-26 21:51 ` Thomas Petazzoni via buildroot [this message]
2026-10-27 11:42 ` Yegor Yefremov via buildroot
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=at_LGuRSbDPCUp60@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=yegorslists@googlemail.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