Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/php: remove CFLAGS for OPcache extension
Date: Sat, 01 Aug 2026 14:49:14 +0200	[thread overview]
Message-ID: <f71c404342fb5d24ebfb6e709d5edb79@free.fr> (raw)
In-Reply-To: <20260730183524.1145030-1-bernd@kuhls.net>

On 30/07/2026 20:35, Bernd Kuhls wrote:
> Buildroot commit aedf131da66d2f2ebce64788deab07be17ce33eb bumped the
> package to 8.5.0 which made opcache a mandatory dependency but kept the
> CFLAGS added in 2015 with buildroot commit
> e05476491720f96fcbeb926b4599d111efb598a6.
> 
> As it turns out we need to remove the CFLAGS to fix the build with the
> bootlin-aarch64-glibc-old defconfig as detected by the Gitlab 
> pipelines:
> 
> ext/opcache/shared_alloc_posix.o: In function `create_segments':
> shared_alloc_posix.c:(.text+0xcc): undefined reference to `shm_open'
> shared_alloc_posix.c:(.text+0x11c): undefined reference to `shm_unlink'
> shared_alloc_posix.c:(.text+0x19c): undefined reference to `shm_unlink'
> shared_alloc_posix.c:(.text+0x1b8): undefined reference to `shm_unlink'
> 
> as they seem to disturb the detection of librt.
> 
> It is unclear which upstream commits added since 2015 fixed the 
> original
> problem so a backport to LTS branches is not advised.
> 
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>

Series applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2026-08-01 12:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30 18:35 [Buildroot] [PATCH 1/2] package/php: remove CFLAGS for OPcache extension Bernd Kuhls
2026-07-30 18:35 ` [Buildroot] [PATCH 2/2] package/php: security bump version to 8.5.9 Bernd Kuhls
2026-08-01 12:49 ` Julien Olivain 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=f71c404342fb5d24ebfb6e709d5edb79@free.fr \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=ju.o@free.fr \
    /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