Unai Martinez-Corral

@Bounz, AFAIK, all the resources provided by this project are for x86_64/amd64 hosts only. Hence, when you provide `qemu=x86_64`, you are asking it to extract `qemu-x86_64-user` from an image meant...

Hi @b1nch0 ! This repository is for amd64/x86_64 hosts only (#77, #111). For other host archs, you can use [dbhi/qus](https://github.com/dbhi/qus): > images are provided for each of seven host architectures...

@Lewiscowles1986 you might want to have a look at (the CI of) [dbhi/qus](https://github.com/dbhi/qus).

See https://github.com/dbhi/docker#building-docker-images-foron-arm-targets: > Building DynamoRIO on an arm32v7 container on a 64 bit host requires to set -DCMAKE_SYSTEM_NAME=Linux -DCMAKE_SYSTEM_PROCESSOR=armv7, as explained at DynamoRIO/dynamorio#3381.

@kutschkem, I tried with version 4.0.0, and those errors seem to be fixed. Still, I get: ``` Unknown QEMU_IFLA_INFO_KIND ipip Unknown QEMU_IFLA_INFO_KIND ip6tnl ```

@martin-g, this seems to be a missing feature upstream. I suggest to open a report in https://bugs.launchpad.net/qemu.

@martin-g, see https://github.com/multiarch/qemu-user-static/blob/master/.travis.yml#L24-L28

@Biswa96: > one of the components of nextpnr-ecp5 needs more that 4GB to be build. Therefore, it cannot be done in a 32 bit memory space.

This PR is now based on #8231.

> (1) Please don't use pacman as means to avoid teaching people how compiling on windows works. I understand that you cater to the average folks, which is perfectly fine....