yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] knaik95:
I can't seem to get 'make bison' to work. This is the error message I'm getting

FAILED: /root/LOS/out/soong/build.ninja
/root/LOS/out/soong/.bootstrap/bin/soong_build -t -l /root/LOS/out/.module_paths/Android.bp.list -b /root/LOS/out/soong -n /root/LOS/out -d /root/LOS/out/soong/build.ninja.d -o /root/LOS/out/soong/build.ninja Android.bp
error: prebuilts/gradle-plugin/Android.bp:1:1: module "metalava-gradle-plugin-deps" variant "linux_glibc_common": module source path prebuilts/gradle-plugin/com/android/tools/sdk-common/26.2.0-alpha16/sdk-common-26.2.0-alpha16.jar does not exist
error: prebuilts/gradle-plugin/Android.bp:1:1: module "metalava-gradle-plugin-deps" variant "linux_glibc_common": module source path prebuilts/gradle-plugin/com/android/tools/sdklib/26.2.0-alpha16/sdklib-26.2.0-alpha16.jar does not exist
ninja: build stopped: subcommand failed.
20:56:27 soong bootstrap failed with: exit status 1

#### failed to build some targets (11 seconds) ####

I seem to be missing some files but I'm not sure where I'd find them or if this is something on LOS's end
[Android Software/Hacking General [Developers Only]] Uldiniad:
is this 16.0? what's the windows build number you're on? was this a clean sync? or synced 16.0 on top of 15.1?
[Android Software/Hacking General [Developers Only]] knaik95:
I'm on Ubuntu 18.04 LTS. I did a clean sync of 16.0. It's pure 16.0, no mixing and matching with 15.1.
[Android Software/Hacking General [Developers Only]] Uldiniad:
16.0 is WIP on wsl. can't state it enough. and you didn't say what build of windows you're on
[Android Software/Hacking General [Developers Only]] knaik95:
I don't know what build I'm on but I have Windows 8.1, not Windows 10. Does that matter, though? I'm building on Ubuntu. I'm dual-booted, not running on a VM.
[Android Software/Hacking General [Developers Only]] Uldiniad:
Can you read the title of this thread?

why in the world would you execute commands that are specific to wsl on native???
[Android Software/Hacking General [Developers Only]] knaik95:
They're all linux commands. Ubuntu has those too... WSL is running a linux distro as a subsystem on Windows. Ubuntu is one of those linux distros. As far as I know, if it works on WSL, there's no reason it shouldn't work on raw Linux. But as you said, this is a WIP. Maybe it's just not ready yet.
[Android Software/Hacking General [Developers Only]] Uldiniad:
I'm not dumb. I know that they're linux commands. the problem is: why do you come to a WSL thread when you're building on native? it is not the same thing. WSL is much more restrictive (64-bit executables only for example, messed up munmap, etc.) and therefore many commands you launch on WSL do not work as they would on native... which explains the extra steps that are required on wsl which are not on native and the reason why I write a guide. just go to the official aosp or lineageOS website to setup a native build environment... and don't waste your time running wsl specific extra commands on native
[Android Software/Hacking General [Developers Only]] knaik95:
I posted on the official LOS threads and they recommended I come here. I didn't run any of the WSL commands to set up the build env, I only followed this guide where the steps would be the same as on Ubuntu.
[Android Software/Hacking General [Developers Only]] Uldiniad:
lol. can you give me the link to the posts? cause thy're either trolling you and me or you were using wsl
[Android Software/Hacking General [Developers Only]] knaik95:
https://xdaforums.com/showpost.php?p=77512651&postcount=118
[Android Software/Hacking General [Developers Only]] Uldiniad:
ok. so the guy probably didn't look into the details of this thread. what you're looking for is: https://wiki.lineageos.org/devices/ and check the build guide for your device

xda should be among your last resorts, not first. there are official guides for stuff on lineageOS. most things on xda should be classified unofficial or hacks imo.
[Android Software/Hacking General [Developers Only]] KiD3991:
[966/966] including vendor/qcom/opensource/interfaces/wifi/supplicant/1.0/Androi

device/oneplus/oneplus2/camera/QCamera2/Android.mk: error: camera.msm8994 (SHARED_LIBRARIES android-arm) missing libqdMetaData (SHARED_LIBRARIES android-arm)

You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.

device/oneplus/oneplus2/camera/QCamera2/Android.mk: error: camera.msm8994 (SHARED_LIBRARIES android-arm) missing libqdutils (SHARED_LIBRARIES android-arm)

You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.

build/make/core/main.mk:833: error: exiting from previous errors.

15:32:48 ckati failed with: exit status 1

#### failed to build some targets (40 seconds) ####

Any ideas for this error? Has been bugging me for days
[Android Software/Hacking General [Developers Only]] seadersn:
integrate libqdutils.so, either 64bit and 32bit, in your vendor proprietary tree. or try building it from source by adding it to device.mk in your device tree.
[Android Software/Hacking General [Developers Only]] Uldiniad:
I am not responsible for errors that are not related to the build environment. You can check lineage gerrit to see if there are patches you can cherrypick if you can't fix that error yourself. I'm assuming this is 16.0 which is not ready to build for many devices without picking many unmerged patches. I will make an announcement when I have successfully built 16.0 on wsl but at the moment even on Ubuntu 18.04LTS it's not compiling out of the box.
[Android Software/Hacking General [Developers Only]] Uldiniad:
Pie (wsl flavour) is out of the oven

Hey everyone,

TL;DR

It is now possible to build lineage-16.0 on wsl! Just follow the updated guide from start to finish (syncing 16.0 on top of 15.1 is not recommended) and enjoy.

DO NOT COMPLAIN ABOUT ANY ERRORS THAT ARE NOT STRICTLY DUE TO THE BUILD ENVIRONMENT (WSL). Many devices are not ready to build yet!

Also, as always, I recommend building on the latest version of Windows. October Update was released recently: https://www.microsoft.com/en-ca/software-download/windows10

For those still insterested in building 15.1 (ignore the repopick step): https://web.archive.org/web/2018061...ng/guide-how-to-build-lineageos-15-1-t3750175 (as mentioned in my previous announcement, do not report any errors, I will ignore them, since I do not have the means to maintain more than one branch on wsl)

Full version:

It has been some time since the last update. I apologise for the crickets.

I didn't want to write a post until I was able to guarantee I could build lineage-16.0 without issues on wsl. I downloaded the sources as soon as they were released but was unable to complete a full build for my device without cherry-picking lots of patches for it and decided against it since I wanted to reduce the scope of the errors to the build environment alone. I only recently thought of building a generic image instead (which would accomplish what I wanted). Thankfully, wsl had less problems this time cause Google were cool with updating their bison and flex prebuilts (thereby now making them 64-bit) and killed off ijar (hopefully forever). So only dex2oat needed a patch this time around :D

The wsl-compile-lineage-16.0 patches are merged (https://review.lineageos.org/#/q/st...h:lineage-16.0+topic:wsl-compile-lineage-16.0). So no additional steps required there. Otherwise, make sure to install m4 since it spat out an error about it missing.

Thank you for your support,

Uldiniad

P.S. Feel free to ask any questions related to this and check my previous announcements to know my goals and standards for this side-project (https://xdaforums.com/showpost.php?p=77321912&postcount=261 for example)

P.P.S. I am working on making an official wiki page on the LineageOS website which will be more convenient than this thread. I might consider leaving the thread open for feedback once it is open, but I might also consider having feedback reported via official means (JIRA probably).
[Android Software/Hacking General [Developers Only]] riteshrk.aec:
Will lineage 15.0 device tree work with lineage 16.0?
[Android Software/Hacking General [Developers Only]] seadersn:
should, just try it.
[Android Software/Hacking General [Developers Only]] Uldiniad:
nope. if you want to work on 15.1, sync the 15.1 tree. check the web archive link in OP or my last announcement
[Android Software/Hacking General [Developers Only]] riteshrk.aec:
is there any tutorial available for modifying device tree or creating a new one?
[Android Software/Hacking General [Developers Only]] Uldiniad:
as in porting lineage to a new device? or making changes to an existing device tree and uploading them to gerrit? or syncing 15.1 to a folder?
[Android Software/Hacking General [Developers Only]] riteshrk.aec:
make changes in existing 15.1 device tree so that it is compatible with android p.
[Android Software/Hacking General [Developers Only]] Uldiniad:
sounds like "device bringup". what device are you building? it may be already underway. else you should check for device bringup guides. There might be one on LineageOS wiki (the charter is important for standards). Otherwise, you can search for some threads.

It's no simple task. If you're the only maintainer and need help and advice, then you should go on the lineage irc chat.
[Android Software/Hacking General [Developers Only]] oscfd:
Hi, I was wondering how can I build LOS 16.0 with an unofficial tree on GitHub, it's ready for Pie ROMs. Sorry for the noob question :silly:
[Android Software/Hacking General [Developers Only]] Aaronspark777:
Trying to build for my nexus 6 and the command "breakfast shamu" always outputs

** Don't have a product spec for: 'lineage_shamu'

** Do you have the right repo manifest?

I've gone into device/moto/shamu and ran the "./extract-files.sh" command. I've also have edited .repo/local_manifests/roomservice.xml to include:

<project name="TheMuppets/proprietary_vendor_shamu" path="vendor/shamu" remote="github" />

doing a repo sync always stops at 99%
[Android Software/Hacking General [Developers Only]] Uldiniad:
https://github.com/TheMuppets/proprietary_vendor_motorola

motorola being the important word
[Android Software/Hacking General [Developers Only]] Uldiniad:
most likely you can, you will have to configure the environment for it. start by syncing the repo by modifying your roomservice.xml accordingly
[Android Software/Hacking General [Developers Only]] Aaronspark777:
yeah, i realized that mistake and fixed it. still getting the same error with breakfast shamu even after doing a repo sync.
[Android Software/Hacking General [Developers Only]] preethamkmr3:
Stuck!!

stuck at step 10.

i'm getting this error.

thanks in advance.

preetham@DESKTOP-2FIGS0T:~/android/lineage$ source build/envsetup.sh

-bash: build/envsetup.sh: No such file or directory
[Android Software/Hacking General [Developers Only]] Uldiniad:
the error is clear. the file or directory doesn't exist. something probably went wrong in step 9 or before. can you try repo sync again and see if you're still stuck after that?
[Android Software/Hacking General [Developers Only]] preethamkmr3:
passed step 10

but i'm getting this error at step 11 , help me out,thanks.

preethamthallam@instance-1:~/android/lineage$ breakfast titan

including vendor/lineage/vendorsetup.sh

build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_

titan".

13:41:17 dumpvars failed with: exit status 1

Device titan not found. Attempting to retrieve device repository from LineageOS Github (http://git

hub.com/LineageOS).

Found repository: android_device_motorola_titan

Default revision: lineage-16.0

Checking branch info

Default revision lineage-16.0 not found in android_device_motorola_titan. Bailing.

Branches found:

cm-12.0

cm-12.1

cm-13.0

cm-14.0

cm-14.1

stable/cm-12.0-YNG3C

stable/cm-12.0-YNG4N

stable/cm-12.1-YOG4P

stable/cm-12.1-YOG7D

stable/cm-13.0-ZNH0E

stable/cm-13.0-ZNH5Y

Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.

build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_

titan".

13:41:18 dumpvars failed with: exit status 1

build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_

titan".

13:41:19 dumpvars failed with: exit status 1

** Don't have a product spec for: 'lineage_titan'

** Do you have the right repo manifest?
[Android Software/Hacking General [Developers Only]] Uldiniad:
https://github.com/LineageOS/android_device_motorola_titan

your device doesn't have lineage-16.0.
[Android Software/Hacking General [Developers Only]] preethamkmr3:
Amazing work.

Thanks a lot for being patient and answering everything :D
[Android Software/Hacking General [Developers Only]] _JaSoN_:
thanks for the tutorial i did every step but i got a problem at step 11 too

jason@JaSoN:~/android/lineage$ breakfast mido
including vendor/lineage/vendorsetup.sh
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_mido".
18:41:14 dumpvars failed with: exit status 1
Device mido not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Found repository: android_device_xiaomi_mido
Default revision: lineage-16.0
Checking branch info
Default revision lineage-16.0 not found in android_device_xiaomi_mido. Bailing.
Branches found:
cm-14.1
lineage-15.0
lineage-15.1
Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_mido".
18:41:19 dumpvars failed with: exit status 1
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_mido".
18:41:21 dumpvars failed with: exit status 1

** Don't have a product spec for: 'lineage_mido'
** Do you have the right repo manifest?

jason@JaSoN:~/android/lineage$ repo sync
Traceback (most recent call last):
File "/home/jason/android/lineage/.repo/repo/main.py", line 531, in <module>
_Main(sys.argv[1:])
File "/home/jason/android/lineage/.repo/repo/main.py", line 507, in _Main
result = repo._Run(argv) or 0
File "/home/jason/android/lineage/.repo/repo/main.py", line 158, in _Run
copts, cargs = cmd.OptionParser.parse_args(argv)
File "/home/jason/android/lineage/.repo/repo/command.py", line 67, in OptionParser
self._Options(self._optparse)
File "/home/jason/android/lineage/.repo/repo/subcmds/sync.py", line 189, in _Options
self.jobs = self.manifest.default.sync_j
File "/home/jason/android/lineage/.repo/repo/manifest_xml.py", line 360, in default
self._Load()
File "/home/jason/android/lineage/.repo/repo/manifest_xml.py", line 423, in _Load
nodes.append(self._ParseManifestXml(local, self.repodir))
File "/home/jason/android/lineage/.repo/repo/manifest_xml.py", line 443, in _ParseManifestXml
root = xml.dom.minidom.parse(path)
File "/usr/lib/python2.7/xml/dom/minidom.py", line 1918, in parse
return expatbuilder.parse(file)
File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 922, in parse
fp = open(file, 'rb')
IOError: [Errno 13] Permission denied: '/home/jason/android/lineage/.repo/local_manifests/roomservice.xml'
jason@JaSoN:~/android/lineage$ chmod 777 /home/jason/android/lineage/.repo/local_manifests/roomservice.xml
jason@JaSoN:~/android/lineage$ repo sync
fatal: no <manifest> in /home/jason/android/lineage/.repo/local_manifests/roomservice.xml
jason@JaSoN:~/android/lineage$

the roomservice.xml looks like this

<project name="themuppets/proprietary_vendor_xiaomi" path="vendor/mido" remote="github" />

in the vendor/mido there is 16.0 branch and there is already an [ROM][UNOFFICIAL][9.0.0][mido] LineageOS 16.0 rom

i never did that before can u maybe help me how to get that working ? :D
[Android Software/Hacking General [Developers Only]] Uldiniad:
1. https://github.com/LineageOS/android_device_xiaomi_mido

no lineage-16.0 branch

2. you got your first vendor_your_device_brand right, but you messed up the second. why did you go from xiaomi to mido on the second?

3. you malformed your roomservice.xml. it was not generated properly with breakfast and you didn't declare it correctly since it's telling you you're missing <manifest>
[Android Software/Hacking General [Developers Only]] Uldiniad:
I see no reason why it would, there's probably something that wasn't done correctly because shamu has a lineage-16.0 branch.
[Android Software/Hacking General [Developers Only]] lozohcum:
How about the performance of this solution?
[Android Software/Hacking General [Developers Only]] Uldiniad:
https://www.phoronix.com/scan.php?page=article&item=wsl-february-2018&num=1

From my experience, native ubuntu on hdd vs wsl on ssd on my rig are about the same in performance concerning build time. Syncing is faster for me on wsl
[Android Software/Hacking General [Developers Only]] _JaSoN_:
[MENTION=7350242]Uldiniad[/MENTION] thanks for answering :) so this means to

1. there is no chance for me to use los 16 branch ?

2. oh **** i must have had mido copyed before pasting that xiaomi into it :) fixed now sorry

3. there where no roomservice file at all i created 1 in the dir :X and copyed that into it

im brand new to this :( will it work when i first do the 15.1 branch and then the 16 ?

because there is already a rom https://xdaforums.com/redmi-note-4/...ther-development/rom-lineageos-16-0-t3830602/

i just asking because i wanna learn this :) the phone is not used anymore so i thought why not try to learn it with this :)
[Android Software/Hacking General [Developers Only]] Uldiniad:
there is no official 16.0 branch for mido at the moment and I cannot see nor predict the future.

the roomservice file should have been created with breakfast but since there is no 16.0 branch it most likely wasn't. you can declare the manifest manually but it won't help in this scenario since the official branch is nonexistent.

since you can't sync 16.0 officially, syncing 15.1 first will not make any difference. that said you can check the web archive link for how to proceed with 15.1 on wsl if you wish to build 15.1 for mido (that branch does exist).

the existence of unofficial roms doesn't usually have any impact on official branches. the developer is probably syncing his own personal device tree. probably did some bringup based on the 15.1 branch.
[Android Software/Hacking General [Developers Only]] Uldiniad:
what command did you run to get this error?
[Android Software/Hacking General [Developers Only]] seadersn:
looks like . build/envsetup.sh & breakfast lineage_dumpling (or similar, preparing a build). and looks like incomplete fetching of sources.
[Android Software/Hacking General [Developers Only]] hachi1211:
I was running

breakfast dumpling

and using 16.0 branch.

When I checked actual path the directory or file is present but don't know why module finder was failing.
[Android Software/Hacking General [Developers Only]] k4rn8g3:
Can you specify the extra steps needed to build for non official builds..

(For devices not officially supported by Lineage..)

I have all the device sources I need but is not officially supported by LineageOS..
[Android Software/Hacking General [Developers Only]] DSA:
If you have the required source downloaded, just build it...there are no extra steps?
[Android Software/Hacking General [Developers Only]] k4rn8g3:
How to include them for build ??
[Android Software/Hacking General [Developers Only]] GreatGodvin:
Through the local manifests.xml
[Android Software/Hacking General [Developers Only]] k4rn8g3:
Thanks !!

Also I'm kinda new to the roomservice.xml file

Can you explain how to handle that file.. ??

I read the OP but I'm kinda dense to understand that..

PS : I'm trying to build a modded version of LOS 14.1.
[Android Software/Hacking General [Developers Only]] Uldiniad:
you're on your own for 14.1. never supported it myself before
[Android Software/Hacking General [Developers Only]] Uldiniad:
there are many no such file or directory errors. as seadersn suggested, there might be a possibility that the sources didn't sync properly. when you run repo sync it completes successfully (and has done so previously)?
[Android Software/Hacking General [Developers Only]] hachi1211:
Yes repo sync is successful without any error. I tried many times but repo sync never failed.

---------- Post added at 09:22 PM ---------- Previous post was at 09:13 PM ----------

Yes repo sync is successful without any error. I tried many times and repo sync never failed.
[Android Software/Hacking General [Developers Only]] Viggen66:
Just some questions, indeed this is a very interesting topic, as building roms straight from a Windows platform.

Alright, here are my questions.

Does this work also for nougat roms?

On a strong power PC, Intel I7 or Ryzen 7 , 16 gigs of ram, good HDD speed, it takes on a solo linux platform at least 3 hours or more to assemble a Rom, how long does it take, with a Windows 10 running underneath over it?
[Android Software/Hacking General [Developers Only]] krishV:
build/make/core/product_config.mk:234: error: Can not locate config makefile for prod

does it supports for xiaomi mi max hydrogen

please help me

build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_hydrogen".
[Android Software/Hacking General [Developers Only]] Uldiniad:
https://github.com/LineageOS/android_device_xiaomi_hydrogen

no
[Android Software/Hacking General [Developers Only]] Uldiniad:
16.0 is Pie. Nougat is <= 14.1. I have stated that I will only support the latest branch because I am the only one as far as I know that is working on wsl compatibility and do not have the means to support more than one branch at a time.

for your second question

https://xdaforums.com/showpost.php?p=77914691&postcount=358

my rig is https://ca.pcpartpicker.com/user/Uldiniad/saved/#view=J4jBbv
[Android Software/Hacking General [Developers Only]] Uldiniad:
do you mind checking that all the files that module-finder says they don't exist are actually there? I cannot reproduce soon, but will give a try (on native first to see if it is wsl exclusive)
[Android Software/Hacking General [Developers Only]] David_Ozc:
Facing this problem anyone can help

the permission keep on denied
[Android Software/Hacking General [Developers Only]] Uldiniad:
use chmod if needed? but there should be no reason why the permissions got messed up. probably something didn't sync properly
[Android Software/Hacking General [Developers Only]] krishV:
Why it doesn't support
[Android Software/Hacking General [Developers Only]] Mandeep Hundal:
Hi,

I downloaded the source code of lineage 16.0 first time but I can't find envsetup.sh

When ever I run command it shows information of other scripts but in the last show executed script not found.

Is source code incomplete or problem with sync ?
[Android Software/Hacking General [Developers Only]] Jain2vicky@gmail.com:
that means i can't build lineageos 15.1 for my device until it get updated in lineageOS repository...

is there any other way?
[Android Software/Hacking General [Developers Only]] Jain2vicky@gmail.com:
my device doesn't have lineage os 15.1 yet?

what can i do?

is there any other way??
[Android Software/Hacking General [Developers Only]] Uldiniad:
one of the issues is that you're not typing in the correct command. make gemini means nothing. the correct command to debug is:

breakfast gemini && make bacon showcommands