-
Notifications
You must be signed in to change notification settings - Fork 294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ROOTFS problems #28
Comments
The error message means that the BusyBox build process fails at some point, most probably due to earlier error with "glibc". Please execute the scripts individually and observe the output for any discrepancies. You can also take a look at the simplified project which is called "Minimal Linux Script": |
fyl sh and time where reversed in build_minimal_linux_live.sh fixed :)
|
Regarding (2) - you need to run the scripts one by one and analyse the result. Start from the very beginning. Also take a look at the project's website and make sure you have installed all the prerequisite software. |
Busybox is failing to compile. I believe that is causing the rootfs error. Log below. can a prebuilt BB binary be used?
|
Please take closer look at this particular log message:
Like I said earlier, this suggests that the GLIBC build/preparation process has failed at some point. Or maybe the generation of the kernel headers has failed (this is even earlier in the build chain). I can't assist you more because it seems like a local issue on your machine. My best advice for you - please take some free time and learn how to use GCC (especially the C compiler) in order to track down and fix the root cause. Regarding your last question - you can use any pre-built BusyBox binary but you'll also need to adjust the build scripts accordingly. This means that you should be familiar with the internal structure of the build scripts. Have you tried any of the previously published scripts of MLL? Perhaps it will be best if you start from the first published version and see if you can build the OS. Then move to the next MLL version, do the same procedure and so on. |
I'm closing the issue since it is not directly related with the scripts. Refer to my previous comments. |
During the build the following errors happen:
*** GENERATE ROOTFS BEGIN *** Preparing initramfs work area... cp: cannot stat ‘/home/jeff/minimal/src/work/busybox/busybox_installed’: No such file or directory cp: target ‘rootfs’ is not a directory 09_generate_rootfs.sh: 24: cd: can't cd to rootfs cp: cannot stat ‘../src’: No such file or directory Source files and folders have been copied to '/src'. cp: cannot stat ‘/home/jeff/minimal/src/work/glibc/glibc_prepared/lib/ld-linux*’: No such file or directory Dynamic loader is accessed via '/lib'. cp: cannot stat ‘/home/jeff/minimal/src/work/glibc/glibc_prepared/lib/libm.so.6’: No such file or directory cp: cannot stat ‘/home/jeff/minimal/src/work/glibc/glibc_prepared/lib/libc.so.6’: No such file or directory cp: cannot stat ‘/home/jeff/minimal/src/work/glibc/glibc_prepared/lib/libresolv.so.2’: No such file or directory cp: cannot stat ‘/home/jeff/minimal/src/work/glibc/glibc_prepared/lib/libnss_dns.so.2’: No such file or directory Reduced the size of libraries and executables. The initramfs area has been generated. *** GENERATE ROOTFS END *** 0.00user 0.00system 0:00.07elapsed 0%CPU (0avgtext+0avgdata 2764maxresident)k 0inputs+0outputs (0major+2016minor)pagefaults 0swaps *** PACK ROOTFS BEGIN *** Packing initramfs. This may take a while... 10_pack_rootfs.sh: 14: cd: can't cd to rootfs
The text was updated successfully, but these errors were encountered: