Closed wangzhankun closed 2 years ago
Some questions:
Does the configure file in the path /home/wang/Documents/sel4/seL4test/projects/musllibc/configure
exist?
What does repo manifest
output?
What system are you running on?
Yes, I find the error. Because after I clone the repo, the configure file is changed into CR mode. After I chang it into CRLF mode, it's all right.
Another question is why the file is changed into CR mode? I have to write a code to walk through all the files and change the '\r' into '\r\n'.
Here is my gitconfig:
[core]
autocrlf = true
filemode = false
[color]
ui = auto
[url "https://githubcn.hgnet.workers.dev/google/boringssl.git"]
insteadOf = https://boringssl.googlesource.com/boringssl
[url "https://ghp.quickso.cn/https://github.com"]
insteadof = https://github.com
So what system are you running on?
\r
sounds very strange. It should be all \n
. \r\n
would be Windows which is not supported as build host (you might be able to get it working, but we have not tried).
I'm running on WSL2-ubuntu20.04. I use this command to change the \r
.
sed -i 's/\r$//' $1
This is what happens when you clone/checkout on Windows and then switch into WSL. If you want to avoid this, either do the clone/checkout under WSL to begin with or use core.autocrlf=false
when checking out or cloning under Windows.
@wangzhankun does using the repo tool in WSL work for you? I can confirm that seL4test works for me in Ubuntu 20.04 running in WSL2, if I run all the commands inside WSL.
@wangzhankun does using the repo tool in WSL work for you? I can confirm that seL4test works for me in Ubuntu 20.04 running in WSL2, if I run all the commands inside WSL.
Ooh, that would be very nice to document on the host deps page!
I clone the repo under WSL not on windows. And the repo
tool works well on WSL.
Since a solution has been found, we can close this.
I have successfully executed
repo sync
,and../init-build.sh -DPLATFORM=x86_64 -DSIMULATION=TRUE
executed successfully. But when I doninja
, I get the following error:I try to only execute the
sh command
independently, and I get the error: