A newbie who wants to build /e/ Pie, possible?

andrelam · April 30, 2020, 5:38pm

Do you have a lineage_j5nlte.mk in your device tree? I think you have a naming issue, the script searches for something like lineage_j5nlte, you tree has PRODUCT_NAME := omni_j5nlte

Chimpthepimp · April 30, 2020, 5:41pm

at least the LOS-16.0 sources have both omni as lineage_j5nlte.mk

andrelam · April 30, 2020, 5:42pm

Indeed, i did not notice that, go for the Pie build!

Anonyme · April 30, 2020, 5:49pm

All right then, didn’t really and deeply understand what was the issue with Oreo but I go for Pie

Results tomorrow since it will take 4-5h to download the 120 GB (or more) needed for Pie, and I don’t know how many times the build will take (if it starts), my laptop isn’t the best.

Thank you for keeping my hope alive

Anonyme · April 30, 2020, 7:56pm

So, just after launching the build process I have one issue (seems a little issue), here is the log file in /srv/e/logs :

>> [Thu Apr 30 19:38:47 UTC 2020] (Re)initializing branch repository
Downloading manifest from https://gitlab.e.foundation/e/os/android.git
Invalid clone.bundle file; ignoring.

repo has been initialized in /srv/src/PIE
>> [Thu Apr 30 19:38:56 UTC 2020] Syncing branch repository
fatal: remove-project element specifies non-existent project: LineageOS/android_hardware_qcom_audio

Looks like this is about something in the roomservice.xml (which is exactly this one), here is the problematic part :

 <!-- Qcom audio  -->
  <remove-project name="LineageOS/android_hardware_qcom_audio"/>
  <project path="hardware/qcom/audio-caf/msm8916" name="Galaxy-MSM8916/android_hardware_qcom_audio" groups="qcom,qcom_audio,pdk" revision="lineage-16.0-caf-8916" />

I don’t know if I have to delete all this part from the roomservice file or only the part or something else.

andrelam · April 30, 2020, 7:58pm

Yes, delete the line. It wants to delete something that is not there.

Anonyme · April 30, 2020, 8:00pm

I removed all this part and now it works, the process is running

andrelam · April 30, 2020, 8:07pm

Good for you! Nothing more exiting then your own working build

harvey186 · April 30, 2020, 8:07pm

good luck. A lot if issues are coming between 75 and 99%

In the moment a lot of build stuck at 99% with ‘out of space’ error. And no way the solve that issue. The e-dev’s must clean the sources to get a smaller system.img

Anonyme · May 1, 2020, 12:04pm

After 2h30 of repository syncing and 13h of building, it failed at 99% !! I slept on the coach to stay next to Ethernet for nothing.

Here is the end of the log file :

[ 99% 69228/69566] //art/compiler:libart-compiler link libart-compiler.so
Warning: request a ThreadPool with 1 threads, but LLVM_ENABLE_THREADS has been turned off
[ 99% 69229/69566] Docs droiddoc: /srv/src/PIE/out/target/common/docs/test-api-stubs
javadoc: warning - The old Doclet and Taglet APIs in the packages
com.sun.javadoc, com.sun.tools.doclets and their implementations
are planned to be removed in a future JDK release. These
components have been superseded by the new APIs in jdk.javadoc.doclet.
Users are strongly recommended to migrate to the new APIs.
DroidDoc took 213 sec. to write docs to /srv/src/PIE/out/target/common/docs/test-api-stubs
[ 99% 69230/69566] Docs droiddoc: /srv/src/PIE/out/target/common/docs/api-stubs
javadoc: warning - The old Doclet and Taglet APIs in the packages
com.sun.javadoc, com.sun.tools.doclets and their implementations
are planned to be removed in a future JDK release. These
components have been superseded by the new APIs in jdk.javadoc.doclet.
Users are strongly recommended to migrate to the new APIs.
DroidDoc took 205 sec. to write docs to /srv/src/PIE/out/target/common/docs/api-stubs
ninja: build stopped: subcommand failed.
11:39:02 ninja failed with: exit status 1

#### failed to build some targets (12:53:08 (hh:mm:ss)) ####

>> [Fri May  1 11:39:07 UTC 2020] Failed build for j5nlte
>> [Fri May  1 11:39:07 UTC 2020] Finishing build for j5nlte
>> [Fri May  1 11:39:07 UTC 2020] Cleaning source dir for device j5nlte
11:45:21 Entire build directory removed.

#### build completed successfully (06:13 (mm:ss)) ####

harvey186 · May 1, 2020, 1:05pm

yeah, that’s the ‘funny site’ of building

Could you please post more from the log ? Best you will past it here http://del.dog

and pls check your java version https://www.digitalocean.com/community/tutorials/how-to-install-java-with-apt-on-ubuntu-18-04

Anonyme · May 1, 2020, 4:39pm

https://del.dog/ePieBuildFail1

Looks like java isn’t installed (I guess it’s not positive).

harvey186 · May 1, 2020, 5:30pm

That’s a must have. So first install openJDK 8

Best have a look here. There you will find everything for los building https://wiki.lineageos.org/devices/whyred/build

Anonyme · May 1, 2020, 7:00pm

Thanks, I will install the following elements then :

sudo apt install bc bison build-essential ccache curl flex g+±multilib gcc-multilib git gnupg gperf imagemagick lib32ncurses5-dev lib32readline-dev lib32z1-dev liblz4-tool libncurses5 libncurses5-dev libsdl1.2-dev libssl-dev libxml2 libxml2-utils lzop pngcrush rsync schedtool squashfs-tools xsltproc zip zlib1g-dev

sudo apt install default-jre
sudo apt install default-jdk
sudo apt install openjdk-11-jdk

(I guess the 11 is better than the 8 but might be wrong)

harvey186 · May 1, 2020, 7:05pm

LineageOS 16.0: OpenJDK 1.9

harvey186 · May 1, 2020, 7:07pm

Only the last one …

Anonyme · May 2, 2020, 7:39am

New failure : https://del.dog/ePieBuildFail2.

I pasted the last line on Startpage which is “Target Java: /srv/src/PIE/out/target/common/obj/APPS/SystemUI_intermediates/classes-full-debug.jar” and the fisrt two results were topics on this forum.

Like the author of those two topics, openjdk-9-jdk isn’t available by a simple “apt install openjdk-9-jdk” and I read a comment somewhere that says openjdk-11-jdk replaced the 9 and could be used instead.

So I installed openjdk-11-jdk. Though openjdk-9-jdk is manually downloadable https://jdk.java.net/archive/. I will uninstall the 11 and try to manually install the 9 in case it’s the problem.

The big good news is that now it takes 4h to reach 98% instead of 13h !! I guess it’s due to the 11 GB in ccache (and maybe to the fact I added the line “vm.swappiness=30” in /etc/sysctl.conf to change the default “60” value).

Quick question, once the repositories have been synced and the build process is running, the internet connection can be shut, right ?

EDIT : actually no I won’t because looks like the 11 really replace the 9 and can’t be the issue.

Chimpthepimp · May 2, 2020, 7:42am

Yes that should not be okay

Anonyme · May 2, 2020, 8:11am

I guess it means that it should be okay

Finally I changed my mind and won’t uninstall the 11 for the 9 because it seems weird, it’s not a normal behaviour to install an archived thing with “don’t use that” warning on top of the download page and it’s too tricky. So I don’t know what I should do or what’s wrong exactly.

The only tiny clue I have is that it says “Using OpenJDK 8” in the terminal (I think everyone has this line no matter the Android version the person try to build) :

>> [Thu Apr 30 16:24:13 UTC 2020] Adding OTA URL overlay (for custom URL https://ota.ecloud.global/api)
>> [Thu Apr 30 16:24:13 UTC 2020] Using OpenJDK 8
>> [Thu Apr 30 16:24:13 UTC 2020] Preparing build environment

OpenJDK 8 wasn’t install, only the 11. What I could try is use OpenJDK 8 instead of 11 but like Harvey said :

Though it’s probably not the solution.
Thank you all.

Chimpthepimp · May 2, 2020, 8:34am

Oh yes sorry i guess it s to early in the morning… I was stuck in between its okay and should not be a problem xD just to verify that your roomservice is working, i made a build for it yesterday evening and it worked if you want i can check for my jdk version, but that is why we suggested to build for a supported device the same android version as you aim to build for the unsupported device, that way you would have noticed the missing jdk package before building…