android-x86.github.io icon indicating copy to clipboard operation
android-x86.github.io copied to clipboard

fail to build los-7.1-r5 iso

Open promeneur opened this issue 4 years ago • 5 comments

Hello

i tried to compile and lake an iso for los-7.1-r5

i get los-7.1-r5 with

mkdir android-x86 cd android-x86 repo init -u git://git.osdn.net/gitroot/android-x86/manifest -b android-x86-7.1-r5 -m cm.xml repo sync --no-tags --no-clone-bundle I build los-7.1-r5 with cd android-x86 source build/envsetup.sh lunch cm_android_x86_64-user make -j4 iso_img TARGET_PRODUCT=cm_android_x86_64

at the end the job fails because it can't find the command "mkdosfs"

With openSuse all dosfs tools are root's tools see the log compile.log

promeneur avatar Feb 24 '21 12:02 promeneur

Try sudo apt-get install -y dosfstools to install dosfstools with mkdosfs command, and execute your build command again.

utzcoz avatar Feb 24 '21 14:02 utzcoz

i did not well explain. Dosfs tools are installed but they are root's tools. You must be root user to use them.

And i use openSuse then apt-get is not an openSuse tool

promeneur avatar Feb 24 '21 16:02 promeneur

Looks like the missing mkdosfs doesn't need in Ubuntu. The Google recommends to use Ubuntu to build the AOSP based source code, because they only test and ensure tool chains on Ubuntu. So I recommend you use Ubuntu to build. If you want to use your openSUSE to do it, maybe you can try docker.

utzcoz avatar Feb 24 '21 16:02 utzcoz

Can i use this

sudo -E make -j4 iso_img TARGET_PRODUCT=cm_android_x86_64

promeneur avatar Feb 24 '21 16:02 promeneur

Can i use this

sudo -E make -j4 iso_img TARGET_PRODUCT=cm_android_x86_64

Actually I don't recommend to use sudo to build system, because it will cause running problem, because generated files will get wrong user info. The docker is my recommendation for you.

utzcoz avatar Feb 25 '21 04:02 utzcoz