public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: qemu-user-static build of other architectures
Date: Sun, 27 Nov 2022 12:09:23 +0000	[thread overview]
Message-ID: <B62ACB3E-9439-4EDA-BAEE-F95283B3100D@ipfire.org> (raw)
In-Reply-To: <d11ff8c3-ddc2-4a4b-a689-933f70a7e38d@ipfire.org>

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

Hello Adolf,

> On 26 Nov 2022, at 22:24, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Hi All,
> 
> I tried to run a aarch64 build of samba so that I could get the correct rootfile but I had a few problems.
> 
> I installed qemu-user-static on Arch Linux but when I tried to run the gettoolchain command I got an error message about not finding the binfmt_misc helper.
> 
> Figured out that I needed to also install qemu-user-static-binfmt as well. Then the error message changed to the fact that it could not find /usr/bin/qemu-aarch64-static but it was in that directory.
> 
> Eventually used the find static command from ./make.sh and found that on Arch Linux it does not have "statically linked" but "static-pie linked". Changing the ./make.sh find static command to look for "static-pie linked" then allowed the build for aarch64 to proceed.

It is required that QEMU is statically linked.

The reason for that is that we copy the binary into the build environment where it has no access to any libraries of the host - and to make those available, they need to be compiled into the binary.

PIE does not have anything to do with a statically linked binary (well kind of, but I wouldn’t know why that is relevant in this context).

So what did you change exactly for this to work on your system? make.sh would normally automatically try to find the correct binary.

> Of course having changed ./make.sh means that it now shows up as a modified file in the git status. I will look at changing the find static command to look for either "statically linked" or "static-pie linked" and submit it as a patch for consideration.

> Regards,
> 
> Adolf.
> 

-Michael

  reply	other threads:[~2022-11-27 12:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-26 22:24 Adolf Belka
2022-11-27 12:09 ` Michael Tremer [this message]
2022-11-27 12:26   ` Adolf Belka
2022-11-27 12:49     ` Michael Tremer
2022-11-28 10:21       ` Adolf Belka

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=B62ACB3E-9439-4EDA-BAEE-F95283B3100D@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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