Follow a linked NP_LOCATION #76
Conversation
|
Do you know why it fails on Debian and Ubuntu? It seems like the error for the Debian is the build tools are the wrong platform. Looking at other pull requests, it seems this common. Is your HPC (High Performance Computing) cluster on AARCH64? |
The Ubuntu error has to do with it failing to download the qemu image which I reckon is what #80 is solving. The Debian error is more confusing to me, as you said it looks to be a cross compiling issue (failing to build for arm on x86) but I'm not sure what about my change would have broken that.
Nah, it's x86_64. |
|
the aarch64 vm tests run on x86 host with qemu emulation. It should not need to build anything for aarch64, but somehow it does. |
|
That thing is merged now. Could you rebase and see if the pipeline passes now? |
If `$NP_LOCATION` is linked to a location broot will fail to start. This dereferences any link in `$NP_LOCATION`.
|
Whatever, I'll have to debug the pipeline more. This commit is for sure not the reason it breaks |
Aims to fix #75.
If
$NP_LOCATIONis linked to a locationbrootwill fail to start. This dereferences any link in$NP_LOCATION. I have not tested it beyond confirming that it works on my local machine and my HPC cluster.