From: "H.J. Lu" <hjl.tools@gmail.com>
To: Florian Weimer <fweimer@redhat.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Build failure with --disable-tunables on x86-64
Date: Thu, 24 Dec 2020 14:53:40 -0800 [thread overview]
Message-ID: <CAMe9rOrJ8ORGuhE07J+L_YUB54Ge5O+Oo-i-jb9TauE4JuAJNQ@mail.gmail.com> (raw)
I got
In file included from ../sysdeps/x86/include/cpu-features.h:33,
from ../sysdeps/x86_64/dl-hwcaps-subdirs.c:20:
../sysdeps/x86_64/dl-hwcaps-subdirs.c: In function ‘_dl_hwcaps_subdirs_active’:
../sysdeps/x86/include/cpu-features.h:159:41: error: implicit
declaration of function ‘GLRO’ [-Werror=implicit-function-declaration]
159 | # define __x86_get_cpu_features(max) (&GLRO(dl_x86_cpu_features))
| ^~~~
../sysdeps/x86/sys/platform/x86.h:79:5: note: in definition of macro
‘CPU_FEATURE_CHECK_P’
79 | ((ptr->features[index_cpu_##name].check.reg_##name \
| ^~~
../sysdeps/x86/include/cpu-features.h:68:3: note: in expansion of
macro ‘CPU_FEATURE_USABLE_P’
68 | CPU_FEATURE_USABLE_P (__x86_get_cpu_features (0), name)
| ^~~~~~~~~~~~~~~~~~~~
../sysdeps/x86/include/cpu-features.h:68:25: note: in expansion of
macro ‘__x86_get_cpu_features’
68 | CPU_FEATURE_USABLE_P (__x86_get_cpu_features (0), name)
| ^~~~~~~~~~~~~~~~~~~~~~
../sysdeps/x86_64/dl-hwcaps-subdirs.c:33:9: note: in expansion of
macro ‘CPU_FEATURE_USABLE’
33 | if (!(CPU_FEATURE_USABLE (CMPXCHG16B)
| ^~~~~~~~~~~~~~~~~~
../sysdeps/x86/include/cpu-features.h:159:46: error:
‘dl_x86_cpu_features’ undeclared (first use in this function); did you
mean ‘_dl_x86_init_cpu_features’?
159 | # define __x86_get_cpu_features(max) (&GLRO(dl_x86_cpu_features))
| ^~~~~~~~~~~~~~~~~~~
--
H.J.
reply other threads:[~2020-12-24 22:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAMe9rOrJ8ORGuhE07J+L_YUB54Ge5O+Oo-i-jb9TauE4JuAJNQ@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
/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).