From: Olaf Hering <olaf@aepfle.de>
To: Jan Beulich <jbeulich@suse.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: HAS_CC_CET_IBT misdetected
Date: Tue, 2 May 2023 13:33:13 +0200 [thread overview]
Message-ID: <20230502133313.2192eb99.olaf@aepfle.de> (raw)
In-Reply-To: <43b1c214-4248-a735-6f8c-9e08bdd2eaf6@suse.com>
[-- Attachment #1: Type: text/plain, Size: 869 bytes --]
Tue, 2 May 2023 09:31:56 +0200 Jan Beulich <jbeulich@suse.com>:
> How does 2.37 vs 2.39 matter? CET-IBT support is present in gas as of 2.29.
I have no idea. It turned out, the previous Leap image was based on 15.3, while the current one will be 15.4.
If I run this manually, it appears the error is produced properly:
gcc -Wall -fcf-protection=branch -mmanual-endbr -mindirect-branch=thunk-extern -c -x assembler -o /dev/null - ; echo $?
gcc: error: unrecognized command line option ‘-fcf-protection=branch’; did you mean ‘-fno-protect-parens’?
gcc: error: unrecognized command line option ‘-mmanual-endbr’
1
An for some reason there is no failure with the refreshed image on gitlab:
https://gitlab.com/xen-project/xen/-/jobs/4210269545/artifacts/external_file/build.log
I will investigate why it failed to build for me.
Olaf
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-05-02 11:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 5:48 HAS_CC_CET_IBT misdetected Olaf Hering
2023-05-02 7:31 ` Jan Beulich
2023-05-02 7:34 ` Jan Beulich
2023-05-02 11:33 ` Olaf Hering [this message]
2023-05-02 12:01 ` Andrew Cooper
2023-05-02 12:04 ` Olaf Hering
2023-05-02 13:29 ` Jan Beulich
2023-05-02 13:36 ` Olaf Hering
2023-05-02 13:44 ` Jan Beulich
2023-05-02 13:55 ` Olaf Hering
2023-05-02 13:41 ` Andrew Cooper
2023-05-02 15:17 ` Olaf Hering
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=20230502133313.2192eb99.olaf@aepfle.de \
--to=olaf@aepfle.de \
--cc=jbeulich@suse.com \
--cc=xen-devel@lists.xenproject.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 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.