From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/apache: fix build
Date: Mon, 28 Oct 2024 21:23:29 +0100 [thread overview]
Message-ID: <20241028212329.297e61dd@windsurf> (raw)
In-Reply-To: <20241028192609.459318-1-bernd@kuhls.net>
On Mon, 28 Oct 2024 20:26:09 +0100
Bernd Kuhls <bernd@kuhls.net> wrote:
> diff --git a/package/apache/apache.mk b/package/apache/apache.mk
> index 0a0a0b3de4..d081bbce89 100644
> --- a/package/apache/apache.mk
> +++ b/package/apache/apache.mk
> @@ -21,6 +21,7 @@ APACHE_DEPENDENCIES = host-pkgconf apr apr-util pcre2
>
> APACHE_CONF_ENV= \
> ap_cv_void_ptr_lt_long=no \
> + ac_cv_func_gettid=no \
I'm afraid this is not the proper fix. You're pointing to a build issue
on glibc, which does provide gettid(), which is why the test
successfully detects it. The issue comes from the fact that the apache
code forgets to include <unistd.h> with _GNU_SOURCE defined, which is
needed to access gettid().
See https://man7.org/linux/man-pages/man2/gettid.2.html.
Could you have a look into this, and submit a patch to upstream Apache?
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:[~2024-10-28 20:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 19:26 [Buildroot] [PATCH 1/1] package/apache: fix build Bernd Kuhls
2024-10-28 20:23 ` 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=20241028212329.297e61dd@windsurf \
--to=buildroot@buildroot.org \
--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