[Bug 9686] New: x64+arm64 fatbinary
bugzilla at busybox.net
bugzilla at busybox.net
Thu Mar 2 15:43:47 UTC 2017
https://bugs.busybox.net/show_bug.cgi?id=9686
Bug ID: 9686
Summary: x64+arm64 fatbinary
Product: Busybox
Version: unspecified
Hardware: Other
OS: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: Other
Assignee: unassigned at busybox.net
Reporter: mike at michaellawrenceit.com
CC: busybox-cvs at busybox.net
Target Milestone: ---
Blocker for me , as the docker-build collapses..
anyhow is thier a way to build amd64+arm64 binary..
qemu and proot static in their would be also nice to haves , however have good
static source. for overall emulation ie gentoo-arm64 emerge package on amd64
docker hosts...
bash dies in docker from the initial base , so scripts die... not fun, but via
busy box i could continue to run them ie bb-bash , then invoke emulator. etc.
set as entry point.. etc..
/busybox/bash run ./proot -R /... -q umeq /bin/bash (Debian dev has umeq a
hacked qemu static build on github and a hacked proot static. )
for now if you can I was hoping for some info to build a fat bin for
amd64-arm64 for cross building... via docker container.
I can build on my local machine etc.
also might be a plus to having a multi-arch-fat-binary docker container aimed
at cross builders. thus can run a native bash on host mode cpu if docker build
dies to soon. quay.io is far more patient. however , dockerhub is less...
I just get stiffed by about 30-40 seconds ... before i can set up a few more
scripts and symlinks using from scratch...
https://github.com/gentoo/gentoo-docker-images/blob/master/amd64/
uses busybox to set up for now been using scratch , however more work and
upkeep. but ruining the build.sh , means as the base tarball updates , so too
dose the build.
A: use emulation (for now far more likely)
B: if lucky has arm64 server with docker etc...
busybox base , and /busyboy to call native bash latter , failsafe buys time..
add a few symlinks add a few binfmt files etc.
anyhow , any tips one could have I'll take, on making a fat binary.. to cover
multiple use scenarios ...
if they added qemu static proot binfmt misc etc to busybox that would be
dead-sexy in the future.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the busybox-cvs
mailing list