Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 22 Aug 2017 07:40:33 +0200
From:      Andrea Venturoli <>
To:        Jan Beich <>
Subject:   Re: qemu-aarch64-static
Message-ID:  <>
In-Reply-To: <>
References:  <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On 08/17/17 21:22, Jan Beich wrote:

> Yep. Link the binary (i.e. "date") statically or run it inside jail/chroot.
> Otherwise, /libexec/ references the host system, which on amd64
> wouldn't recognize aarch64 shared libraries.

Thanks a lot.
Now it seems so obvious to me, but I really wouldn't have thought about 
this little detail :)

> That page is a bit out of date. Nowadays building for aarch64 is as simple as
>    $ pkg install poudriere qemu-user-static
>    $ service qemu_user_static onestart
>    $ poudriere jail -cj 111aarch64 -a arm64.aarch64 -v 11.1-RELEASE
>    $ poudriere bulk -j 111aarch64 category/port

I can confirm this is working.

> To speed up port builds you may want to consider using native
> cross-toolchain by creating a jail with -x flag.

Do you have any more info on this?
Except from poudriere's man page's description I could find no other 
docs. Is there any more elaborate description on what this does and how?

I built the jail with -x, but how do I check it's using "native-xtools"?

I tried building ports-mgmt/pkg and it requires ten times more than 
native build (i.e. 24 minutes for aarch64 vs. less than 3 minutes for 
amd64). Is this normal?

  bye & Thanks

Want to link to this message? Use this URL: <>