public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Manuel Lauss via Libc-help <libc-help@sourceware.org>
Cc: Manuel Lauss <manuel.lauss@gmail.com>
Subject: Re: How to set x86 ISA needed property?
Date: Wed, 27 Jan 2021 16:26:31 +0100	[thread overview]
Message-ID: <87im7i4d08.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAOLZvyHJjO0NeA4+FDC4yJag7JNvWcgp=+mb0sP83xKdQf_UYw@mail.gmail.com> (Manuel Lauss via Libc-help's message of "Wed, 27 Jan 2021 16:04:53 +0100")

* Manuel Lauss via Libc-help:

> I've been building a userland for an AMD E-450 (gcc march=btver1) on
> a much more modern and faster x86 host.
> Now, the machione does not boot because up-to-date  glibc devel says this:
>
> /lib64/libc.so.6: CPU ISA level is lower than required
>
> readelf libc.so.6 says:
> Displaying notes found in: .note.gnu.property
>  Owner                Data size        Description
>  GNU                  0x00000010       NT_GNU_PROPERTY_TYPE_0
>      Properties: x86 ISA needed: x86-64-baseline, x86-64-v2, x86-64-v3
>
> x86-64-v3 is supported by the build machine, but the btver1 is at most -v2.
> This used to work in the past; is there a way to force glibc to a certain level?
> (binutils-2.35.1, gcc-10.2.1, glibc master as of 27.01.2021).

What does “gcc -v”?  What are you glibc configure/build flags?

This is expected to happen only if you use something like
-march=x86-64-v3 to build glibc, and only with recent toolchain
version.  I'm surprised you are hitting this with GCC 10, which does not
implement -march=x86-64-v3.

Thanks,
Florian
-- 
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill


  reply	other threads:[~2021-01-27 15:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27 15:04 Manuel Lauss
2021-01-27 15:26 ` Florian Weimer [this message]
2021-01-27 16:06   ` Manuel Lauss
2021-01-27 16:14     ` Florian Weimer

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=87im7i4d08.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=libc-help@sourceware.org \
    --cc=manuel.lauss@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 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).