Swap Gentoo-arm64-chroot to @NeddySeagoon or lest look at the emu's for use.

[necrose99]

@NeddySeagoon http://bloodnoc.org/~roy/Pi3_64bit/aarch_chroot.bz2 or get the stock gentoo arm64-stage to overlay improvements , thus far getting emulation is vexing.

inject more @sakaki- packages into defacto stage3 or other tinderbox URL for bins.

[NeddySeagoon]

The stage3 is pretty much the @system set. Lets not add to it, it will cause confusion. Taking a stage3 and adding things, then calling it a stage4 is fine. Generating a stage4 backup is already well documented in this context too.

Taking a stock gentoo arm64-stage3 and adding a static-user QEMU built with -mtune=generic, would provide a arm64-stage3 that could be chrooted into on any amd64. The chroot in that link is built for a Phenom II

[necrose99]

mainly my use of the emulators in docker from Debian , etc is epidemically/epicly failing , so least that. anyhow docker make a convenient chroot , as it reverts... to initial state... , getting stage3 from Gentoo and getting an emulator to fire more so ... also vexing.. in the cloud for QA , RUN uname -a or bash something... however no emu of workable value... fail.. to run QEMU-arm64 in docker has been HELL ... to say the least. however if it dose.. Gentoo might have more stage 3 options... I figured I could poke at you chroot , in a Gentoo/Sabayon virtual-box , and see if I cant compose a docker of it. cavet's is I may.. need to stip the tarball of Gentoo meta etc just > @ / to install ... via ADD pkg.tar / docker will unpack it for me.

the quem wrapper .c fails...

anyhow I had mind to pull SAKAKi's RPI docker freshly made. https://quay.io/repository/necrose99/gentoo-on-rpi3-64bit https://github.com/necrose99/gentoo-on-rpi3-64bit
however my methods of emulation fail greatly. :-(

nicety of docker though is I can take your Phenom II @ Gentoo-arm64-Phenom2 the via emerge world..... rebake into a new container...

From Gentoo-arm64-Phenom2  ## @NeddySeagoon Phenom 2 container 

RUN CP makefile.conf ./make.conf.orig   .... 
ADD make file   with use case changes... 
( -mtune=generic ) or also in other containers. ( -mtune= coretex a53 (pi3 values here)
Volume /usr/portage , /usr/portage/packages  /var/log/portage  /var/tmp/portage 
### docker dies ephemeral...  this will at least keep the packages and or save ebuilds etc..
ADD # insert lots of cursing here getting QEMU to run on amd64 to emulate arm64 has been hell
Proot from debian dev .... sometimes works on chroot , but prone to crash. 

# {good news if a docker crashes it re-spawns.  (so for @mudler of gentoo/sabayon /bow before the venerable CI devops wisdom... ) me just getting lazier have too much not to try to automate what i can.} 
ADD https://busybox.net/downloads/binaries/1.26.2-defconfig-multiarch/busybox-x86_64 /busybox/busybox-x86_64 
# (side note thiers a busybox packer for multi-cpu-arch mega-fat binary. 
# as often I cant get bash to run in docker...  provides an init sh ("bootstap") , bb-sh qemu  /bin/bash)
### 
## Add emulation tools.
ADD https://github.com/multiarch/qemu-user-static/releases/download/v2.9.1/qemu-aarch64-static.tar.gz /qemu-static-arm64
ADD https://github.com/mickael-guene/umeq/releases/download/1.7.5/umeq-arm64 /
ADD https://github.com/mickael-guene/proot-static-build/raw/master/static/proot-x86_64 /
# ENTRYPOINT ["./qemu-static-arm64", "-execve", "-0", "bash", "/bin/bash"] 
# may need busybox sh in multiple arch to get qemu to fire bash and from then be in the arm64 chroot. 
#https://hub.docker.com/r/mickaelguene/arm64-debian/~/dockerfile/
#RUN ["/usr/bin/umeq-arm64", "-execve", "-0", "bash", "/bin/bash"]

RUN  emerge --newuse -v --deep --with-bdeps y --buildpkg @world 

[necrose99]

![screen capture] (http://i.imgur.com/2ffs83M.png "Screenshot") of proot-static https://pastebin.com/FAzQAJ5T , proot rigged from Debian dev , tends to be frail and segfault or crack...up . anyhow I wanted to pickapart your chroot setup for a more workable docker. Luck of it running in docker 0...

as the image can be thus forked , emerge @ world for more specific CPU tuning. not to mention less stale official arm64 stages might come of it.

if your (@NeddySeagoon) P2-arm64 containerizes and runs, it would be extremely easy to have it re-bake on quay.io to any other arm64 targets or builders. as you call in the pre-built container ... much like a stack of Russian nesting dolls. you can fork and fork , build base , next emerge kodi snes9x etc ...

@ https://github.com/Sabayon/docker-armhfp

[necrose99]

so far emu fails , Chroot aline arm64 as builder wont do in dockerhub forced to build on local host.