Closed GlaireDaggers closed 1 year ago
I'm seeing reference to the fact that this could happen if I somehow had the wrong glibc version checked out, but I'm not sure how that could be the case if I cloned this repo directly from master. Just in case I tried to update the glibc submodule, which had no effect. I'm currently doing a full submodule update --init --recursive
as a last ditch effort to see if that helps, but ofc it's going to take a little while.
Possibly a red flag that according to one of those I'm supposed to be seeing some kind of checking for sysdeps preconfigure fragments...
line, but I see nothing of the sort in the log.
I did this on a WSL2/Ubuntu 22.04.3 installation on which I have done several toolchain builds recently:
git clone https://github.com/riscv-collab/riscv-gnu-toolchain
cd riscv-gnu-toolchain
./configure --prefix=`pwd`/installed-tools --with-arch=rv32em --with-abi=ilp32e
and I got this config.log without the error that you mention: config.log
Can you try with a new/clean Virtual Machine or other installation?
In the meantime, I've kicked off a build here:
git clone https://github.com/riscv-collab/riscv-gnu-toolchain
cd riscv-gnu-toolchain
./configure --prefix=`pwd`/installed-tools --with-arch=rv32em --with-abi=ilp32e
make linux 2>&1 | tee build.log
Possibly a red flag that according to one of those I'm supposed to be seeing some kind of checking for sysdeps preconfigure fragments... line, but I see nothing of the sort in the log.
I don't get that either so it may be outdated info.
Hmm, strange. I guess I can try deleting it and checking it out from scratch, and then trying the same steps on my Windows box in WSL. If the latter works I guess I'll chalk it up to Linux Mint being weird.
I can try a Linux Mint installation/build but it might be tomorrow morning (Irish time) at this stage...
Linux toolchain does not support rv32e, only bare metal toolchain support that
Linux toolchain does not support rv32e, only bare metal toolchain support that
Ok - but the "riscv32 is not supported" issue is arising at configuration and not make/build time.
Ah - I misunderstood this:
The problem I'm running into is that this is failing in build-glibc-linux-rv32em-ilp32e, printing "checking sysdep dirs" before displaying the error "The riscv32 is not supported". The outputs of the config.log in this folder are as follows:
I assumed that this meant the "top level" config.log
.
But it seems to be a lower level config.log
for glibc?
In that case @kito-cheng's comment is apposite.
The Linux toolchain does not suport rv32e and also requires the A (Atomic) extension.
oooh, I see! I think I misunderstood the instructions, I do believe what I actually want is a baremetal toolchain. Sorry for the misunderstanding!
I tried a bare-metal toolchain build and it succeeded.
git clone https://github.com/riscv-collab/riscv-gnu-toolchain issue-1312
cd issue-1312
./configure --prefix=`pwd`/installed-tools --with-arch=rv32em --with-abi=ilp32e
make 2>&1 | tee build.log
So for reference, I am attempting to build this toolchain on Linux Mint 21.1
I have followed the steps outlined in the readme. I first cloned the repository to my secondary drive, fetched the packages as given for Ubuntu, ran the following configure:
And then did:
The problem I'm running into is that this is failing in build-glibc-linux-rv32em-ilp32e, printing "checking sysdep dirs" before displaying the error "The riscv32 is not supported". The outputs of the config.log in this folder are as follows:
I'm really not sure what I'm missing here, is there some step I skipped? Any help would be appreciated.