From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Khem Raj" <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] apr: Cache configure tests which use AC_TRY_RUN
Date: Thu, 25 Aug 2022 22:35:21 +0200 [thread overview]
Message-ID: <20220825223521.04c7284d@booty> (raw)
In-Reply-To: <20220825072103.641291-1-raj.khem@gmail.com>
Hi Khem,
On Thu, 25 Aug 2022 00:21:03 -0700
"Khem Raj" <raj.khem@gmail.com> wrote:
> AC_TRY_RUN macro means the test needs to run to find the result and we
> are cross compiling so this will always get wrong results, this results
> in miscompiling apache2 on musl because it disables rlimit
> (ac_cv_struct_rlimit) wrongly.
>
> All these variables are determined with AC_TRY_RUN checks
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
There are several failures with this patch applied:
| locks/unix/proc_mutex.c: In function 'proc_mutex_choose_method':
| locks/unix/proc_mutex.c:1494:28: error: 'mutex_proc_pthread_methods' undeclared (first use in this function); did you mean 'mutex_posixsem_methods'?
| 1494 | new_mutex->meth = &mutex_proc_pthread_methods;
| | ^~~~~~~~~~~~~~~~~~~~~~~~~~
| | mutex_posixsem_methods
and other undeclared mutex-related symbols.
https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/1446/steps/12/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/3720/steps/11/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/37/builds/5767/steps/11/logs/stdio
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2022-08-25 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 7:21 [PATCH] apr: Cache configure tests which use AC_TRY_RUN Khem Raj
2022-08-25 20:35 ` Luca Ceresoli [this message]
2022-08-25 21:06 ` [OE-core] " Khem Raj
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=20220825223521.04c7284d@booty \
--to=luca.ceresoli@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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 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.