From: Joseph Myers <joseph@codesourcery.com>
To: Szabolcs Nagy <szabolcs.nagy@arm.com>
Cc: Joe Ramsay <Joe.Ramsay@arm.com>, <libc-alpha@sourceware.org>
Subject: Re: [PATCH v5 2/2] Enable libmvec support for AArch64
Date: Wed, 3 May 2023 16:50:05 +0000 [thread overview]
Message-ID: <59eac67e-2ad2-c583-624e-bb1086a32081@codesourcery.com> (raw)
In-Reply-To: <ZFI5RZZJDC5pehro@arm.com>
This has broken configuring glibc for AArch64 in a bootstrap configuration
(e.g. "compilers" build from build-many-glibcs.py).
checking for availability of SVE ACLE... In file included from /scratch/jmyers/glibc-bot/install/compilers/aarch64-linux-gnu/lib/gcc/aarch64-glibc-linux-gnu/14.0.0/include/arm_sve.h:28,
from conftest.c:1:
/scratch/jmyers/glibc-bot/install/compilers/aarch64-linux-gnu/lib/gcc/aarch64-glibc-linux-gnu/14.0.0/include/stdint.h:9:16: fatal error: stdint.h: No such file or directory
9 | # include_next <stdint.h>
| ^~~~~~~~~~
compilation terminated.
configure: error: mathvec is enabled but compiler does not have SVE ACLE. Either use a compatible compiler or configure with --disable-mathvec (this results in incomplete ABI).
https://sourceware.org/pipermail/libc-testresults/2023q2/011207.html
It's possible using -ffreestanding in the configure test would avoid that
dependence on having glibc headers already installed.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2023-05-03 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 13:37 Joe Ramsay
2023-05-03 10:36 ` Szabolcs Nagy
2023-05-03 16:50 ` Joseph Myers [this message]
2023-05-04 9:41 ` [COMMITTED] aarch64: fix SVE ACLE check for bootstrap glibc builds Szabolcs Nagy
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=59eac67e-2ad2-c583-624e-bb1086a32081@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=Joe.Ramsay@arm.com \
--cc=libc-alpha@sourceware.org \
--cc=szabolcs.nagy@arm.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 read-only IMAP folder(s) and NNTP newsgroup(s).