public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: "Schultschik, Sven" <sven.schultschik@siemens.com>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: edk2 fails with isar 0.10
Date: Fri, 20 Sep 2024 11:46:03 +0300	[thread overview]
Message-ID: <3fe1efb927180d7890d49c0e02cd2e0d32c018bc.camel@ilbers.de> (raw)
In-Reply-To: <b72c98574790394aaf48d236e20dd4abecf778a5.camel@siemens.com>

On Thu, 2024-09-19 at 16:26 +0000, 'Schultschik, Sven' via isar-users
wrote:
> Hi Jan,
> 
> we are back on that topic with GCC5 within ISAR instead of GCC49.
> 
> We are now at the point that the file
> 
> ./edk2/BaseTools/Bin/GccLto/liblto-aarch64.a
> 
> is available in the repository, but seems to get deleted before going
> into dh_auto_build
> 
> > find -iname *to-aarch64*
> > ./edk2/BaseTools/Bin/GccLto/liblto-aarch64.s
> 
> So between prepare build and doing the build the .a files seems to
> get
> deleted. But we couldn't yet find where.
> 
> The files is available in the recepie git folder.
> 
> Sven
> 

Hello Sven.

I remember something similar (e.g., removing original binaries) on a
different project. Newer debhelper was removing any binaries in source
code that had different from target's architecture.

AFAIR, overriding dh_strip (or some different step... dh_shlibdeps?
dh_fixperms?) helped.

```
override_dh_strip:
	@echo Skipping $@
```

BTW, the recipe you attached few messages above, builds well with
recent isar/next (arm64 cross/compile).


> On Thu, 2024-02-01 at 16:35 +0000, 'Schultschik, Sven' via isar-users
> wrote:
> > On Wed, 2024-01-31 at 16:50 +0100, Jan Kiszka wrote:
> > > 
> > > We are on sbuild Isar in meta-iot2050 (currently
> > > 30471bb3f787fb0aa822d15e141ecce2f3b99860), and there the recipe
> > > builds.
> > > Already compared that?
> > > 
> > > Jan
> > > 
> > 
> > Hi Jan,
> > 
> > that's weired. the iot2025 does not have that issue and both
> > recipes
> > are identical, therefor I wrote both of them ^^
> > 
> > No clue right know where the difference is. Three big ??? right now
> > over my head
> > 
> > Sven
> > 
> 

-- 
Best regards,
Uladzimir.

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/3fe1efb927180d7890d49c0e02cd2e0d32c018bc.camel%40ilbers.de.

      parent reply	other threads:[~2024-09-20  8:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 10:09 Schultschik, Sven
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 [this message]

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=3fe1efb927180d7890d49c0e02cd2e0d32c018bc.camel@ilbers.de \
    --to=ubely@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=sven.schultschik@siemens.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