public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Schultschik, Sven" <sven.schultschik@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: edk2 fails with isar 0.10
Date: Wed, 31 Jan 2024 10:09:24 +0000	[thread overview]
Message-ID: <3549ee8a0f89934080bdfad50aebd75283b9d8dd.camel@siemens.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 908 bytes --]

Hi everyone,

we updated https://github.com/ilbers/isar
in our setup from 

From 0.9
213b8f62fa74e87321f927fb6b4ed9db93e5cb37
to 0.10 dev
51f5b0dbecb4a7271540793e13c54fac69b42da0


With this update edk2 standalonemm rpmb build started to faile because
of 

/usr/lib/gcc-cross/aarch64-linux-gnu/10/../../../../aarch64-linux-
gnu/bin/ld: cannot find -llto-aarch64
 
the same error, if we deactivate cross build

if we go back to 0.9 the error does not apear

It doesn't matter if we are using edk2 202302 oder 202311 version of
edk2.

we normaly build with GCC5 toolchain flag (GCC for 202311 an newer)

If we switch to edk2 toolchain GCC49 (GCCNOLTO for 202311 and newer) it
compiles without any further errors.

So something in that update to 0.10 seems to prevent LTO to be not
available anymore.

Did someone see similar already, or already knows the reason?

br Sven 


[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 10057 bytes --]

             reply	other threads:[~2024-01-31 10:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 10:09 Schultschik, Sven [this message]
2024-01-31 11:21 ` Anton Mikanovich
2024-01-31 13:07   ` Schultschik, Sven
2024-01-31 15:50     ` Jan Kiszka
2024-02-01 16:35       ` Schultschik, Sven
2024-09-19 16:26         ` 'Schultschik, Sven' via isar-users
2024-09-19 18:23           ` Baurzhan Ismagulov
2024-09-20  9:23             ` 'Schultschik, Sven' via isar-users
2024-09-20  8:46           ` Uladzimir Bely

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=3549ee8a0f89934080bdfad50aebd75283b9d8dd.camel@siemens.com \
    --to=sven.schultschik@siemens.com \
    --cc=isar-users@googlegroups.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