From: Richard Henderson <richard.henderson@linaro.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
michael@amarulasolutions.com, linux-amarula@amarulasolutions.com
Subject: Re: [PATCH 1/1] tests/fp/meson: don't build fp-bench test if fenv.h is missing
Date: Wed, 1 May 2024 06:31:12 -0700 [thread overview]
Message-ID: <4ad368ae-74d0-4a38-b4d9-d907c1b8dc7c@linaro.org> (raw)
In-Reply-To: <CABGWkvrCNoWDB=V5f_7qwCd97dAfOC3XT2ukXYt-FsxuUKK-KQ@mail.gmail.com>
On 5/1/24 05:18, Dario Binacchi wrote:
> Hello Richard,
>
> On Tue, Apr 30, 2024 at 8:15 PM Richard Henderson
> <richard.henderson@linaro.org> wrote:
>>
>> On 4/30/24 09:47, Dario Binacchi wrote:
>>> The fp-bench test (i. e. tests/fp/fp-bench.c) use fenv.h that is not
>>> always provided by the libc (uClibc). The patch disables its compilation
>>> in case the header is not available.
>>
>> Since uclibc has had fenv.h since 2008, are you sure this isn't simply a case of a corrupt
>> installation?
>
>>
>>
>> r~
>
> It's not an issue of corrupted installation but rather of compilation:
Installation of your cross-compiler or buildroot, I mean.
>
> ../tests/fp/fp-bench.c:15:10: fatal error: fenv.h: No such file or directory
> 15 | #include <fenv.h>
> | ^~~~~~~~
> compilation terminated.
Yes, yes. However, <fenv.h> is present in uclibc-ng, and has been since 2008.
So *why* is fenv.h not present?
r~
next prev parent reply other threads:[~2024-05-01 13:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 16:47 [PATCH 1/1] tests/fp/meson: don't build fp-bench test if fenv.h is missing Dario Binacchi
2024-04-30 17:02 ` Alex Bennée
2024-04-30 18:15 ` Richard Henderson
2024-05-01 12:18 ` Dario Binacchi
2024-05-01 13:31 ` Richard Henderson [this message]
2024-05-01 14:17 ` Dario Binacchi
2024-05-11 10:11 ` Dario Binacchi
2024-05-11 10:25 ` Richard Henderson
2024-05-11 11:09 ` Dario Binacchi
2024-05-13 10:10 ` Thomas Huth
2024-05-13 12:21 ` Alex Bennée
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=4ad368ae-74d0-4a38-b4d9-d907c1b8dc7c@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=dario.binacchi@amarulasolutions.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=michael@amarulasolutions.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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;
as well as URLs for NNTP newsgroup(s).