Closed guoqinglei closed 5 years ago
I'll try it out on my machine.
But in any case, please don't use sudo
with these scripts! :-)
Hmmm, I cloned master at 6aa375df2ad3ce2e7d741d09b378503c25547df1 but ./build --download-dependencies gem5-buildroot
worked for me on my Ubuntu 19.04.
Can you try to nuke everything and restart from scratch at that commit, without sudo?
If that doesn't work still, give the Docker setup a try: https://github.com/cirosantilli/linux-kernel-module-cheat/tree/6aa375df2ad3ce2e7d741d09b378503c25547df1#docker
I'll try it out on my machine.
But in any case, please don't use
sudo
with these scripts! :-)
I have pulled the master at 6aa3754 and run "./build --download-dependencies gem5-buildroot" without nuking everything from scratch, the error still exist. One thing should be mentioned that the command "./build --help" works normly. Is there any way to verify whether buildroot has been installed well ?
My ubuntu is 18.04 LTS, do I need to clean the build directory generated under "sudo ./build ***" ? and do the ./build from the scratch ?
Yes, I recommend trying to completely remove the whole linux-kernel-module-cheat/ directory, then clone again and rebuild without sudo. I did a full clean build and it "worked on my machine" :-)
You can try to see the state of the buildroot build, but I don't think it is worth it at this point, just too much complication. If the clean build fails, then try it.
You have to understand why that happened:
out/buildroot/build/default/x86_64/build/glibc-custom/configure: No such file or directory
Most likely candidate was that the submodule/glibc was not cloned properly. But ./build
should do that automatically.
You can try to see the state of the buildroot build, but I don't think it is worth it at this point, just too much complication. If the clean build fails, then try it.
You have to understand why that happened:
out/buildroot/build/default/x86_64/build/glibc-custom/configure: No such file or directory
Most likely candidate was that the submodule/glibc was not cloned properly. But
./build
should do that automatically.
i am so happy that the clean build has succeeded. Although it took a long time to go. the tail info is as follows:
Creating regular file /home/tom/git/linux-kernel-module-cheat/out/buildroot/build/default/x86_64/images/rootfs.ext2 Creating filesystem with 131072 4k blocks and 32768 inodes Filesystem UUID: 454214f4-002e-45aa-91a9-7d62fbc26396 Superblock backups stored on blocks: 32768, 98304
Allocating group tables: done
Writing inode tables: done
Copying files into the device: done
Writing superblocks and filesystem accounting information: done
time 03:44:15
Thanks a lot.
Great!
Yes, the build is a bit slow, I get 30 minutes from scratch on my high end 2018 laptop: https://cirosantilli.com/linux-kernel-module-cheat/#benchmark-builds I don't think there is much alternative in systems programming.
tom@tom-pc:~/git/linux-kernel-module-cheat$ sudo -H ./build --download-dependencies gem5-buildroot
the detailed error info is as follows:
anyone knows why this error happens ?