All of lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@uclibc.org
Subject: Re: [Buildroot] [PATCH 1/1] package/php: bump version to 8.4.13
Date: Tue, 7 Oct 2025 09:16:03 +0200	[thread overview]
Message-ID: <aOS-M2IBT-EF9hS8@waldemar-brodkorb.de> (raw)
In-Reply-To: <pan$d032e$b4c1c5e8$51757159$7a37b176@ID-313208.user.individual.net>

Hi,
Bernd Kuhls wrote,

> Am Tue, 07 Oct 2025 00:01:41 +0200 schrieb Julien Olivain via buildroot:
> 
> > This new version introduces build failures in test-pkg. See:
> > https://gitlab.com/jolivain/buildroot/-/pipelines/2084355487
> 
> Hi Julien,
> 
> the build error is caused by this upstream commit
> https://github.com/php/php-src/commit/
> ea4e8d513cdd87c8ac28cd1ae06f7e814c83ae28
> 
> which changes the detection of copy_file_range.
> 
> Both failing toolchains are uclibc-based but other uclibc defconfigs work 
> so I am unsure how to fix the problem.
> 
> The php configure check for copy_file_range with the bootlin-x86-64-uclibc 
> defconfig fails with
> 
> conftest.c:201:9: error: implicit declaration of function 
> 'copy_file_range' [-Wimplicit-function-declaration]
>   201 |   (void)copy_file_range(-1, 0, -1, 0, 0, 0);
> 
> and produces a successful build while br-arm-full-nothread has only a 
> warning, and assumes that copy_file_range is present, most likely due to 
> older gcc being used:
> 
> conftest.c:191:9: warning: implicit declaration of function 
> 'copy_file_range' [-Wimplicit-function-declaration]
>   191 |   (void)copy_file_range(-1, 0, -1, 0, 0, 0);
> 
> Is it save to assume that I can add php_cv_func_copy_file_range=no to 
> _CONF_ENV whenever uclibc is used?

Yes, I think so.
best regards
 Waldemar
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2025-10-07  7:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-05 18:01 [Buildroot] [PATCH 1/1] package/php: bump version to 8.4.13 Bernd Kuhls
2025-10-06 22:01 ` Julien Olivain via buildroot
     [not found] ` <123144d001a2c85418ec7f0c25ac45ea__32414.81567254$1759788128$gmane$org@free.fr>
2025-10-07  6:34   ` Bernd Kuhls
2025-10-07  7:16     ` Waldemar Brodkorb [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=aOS-M2IBT-EF9hS8@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --cc=bernd@kuhls.net \
    --cc=buildroot@uclibc.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.