As the title suggests, I am porting lineageOS and keep getting this error
/home/zane/Lineage/out/target/product/suzuran/obj/SHARED_LIBRARIES/libqdutils_intermediates/export_includes', needed by '/home/zane/Lineage/out/target/product/suzuran/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/import_includes', missing and no known rule to make it
here is the full log https://paste.myself5.de/JfHg5EA2Je.sql
I have tried re syncing the repo and re downloading the source trees. nothing seems to be fixing this.. :/
Is this problem solved?
How did u solved this issue? @nzzane
Appears I didn't have the right proprietary blobs - and had SonyLOS repo running alongside, the two seemed to clash
So if you are getting this error make sure you have the right vendor files and not two different repos trying to do the same thing
nzzane said:
Appears I didn't have the right proprietary blobs - and had SonyLOS repo running alongside, the two seemed to clash
So if you are getting this error make sure you have the right vendor files and not two different repos trying to do the same thing
Click to expand...
Click to collapse
Sry i didnt get u. What do u mean two different repos?
Sent from my AO5510 using Tapatalk
Raja_12 said:
What do u mean two different repos?
Click to expand...
Click to collapse
If there is a repo named abc at github that supports i.e. FMRadio and another named xyz, that also supports FMRadio, it is neccessary that depending files are coming from the same repo. Actually the repo from LineageOS clashes with the one from SonyLOS and vice versa.
That's, what nzzane wanted to say IMHO...
Yea - so had two different repos conflicting
Lineage repo was trying to build from stock blobs, and SonyLOS repo was trying to build from just device sources (which my device tree wasn't set-up for)
nzzane said:
Yea - so had two different repos conflicting
Lineage repo was trying to build from stock blobs, and SonyLOS repo was trying to build from just device sources (which my device tree wasn't set-up for)
Click to expand...
Click to collapse
I get it. so how to overcome it. Do i have to remove one repo directory. currently im having 3 repos.
Raja_12 said:
I get it. so how to overcome it. Do i have to remove one repo directory. currently im having 3 repos.
Click to expand...
Click to collapse
It depends what each repo does, and how you want to build it (stock blobs or all device tree)
nzzane said:
It depends what each repo does, and how you want to build it (stock blobs or all device tree)
Click to expand...
Click to collapse
all device tree
Raja_12 said:
all device tree
Click to expand...
Click to collapse
Then one of the repos must be conflicting somewhere :S
nzzane said:
Then one of the repos must be conflicting somewhere :S
Click to expand...
Click to collapse
Yea sometimes I can't make clean or clobber. With one repo it works with other it didn't. So I have to maintain only one repo at a time.
I ran into another issue. Can u help
target arm C: audio.primary.msm8916_32 <= hardware/qcom/audio/hal/voice.c
In file included from hardware/qcom/audio/hal/voice.c:32:
hardware/qcom/audio/hal/voice_extn/voice_extn.h:194:71: error: unused parameter 'adev' [-Werror,-Wunused-parameter]
static int voice_extn_compress_voip_set_mic_mute(struct audio_device *adev, bool state __unused)
Sent from my AO5510 using Tapatalk
Related
Hey, I realized that there aren't many CM 10.2 ROMs out there yet, so I made one of my own. This is my first published ROM, so expect a buggy, unsupported experience. I am using fat-tire's repos for the time being. For now, I recommend the GAPPS posted here. I will attempt to post a new build everyday, but no promises.
I don't do support, but I will try to answer questions, and I would appreciate bug reports. Note that CM 10.2 is very much in development right now.
Download/ Changelog
07/31/13 (mirror) - Just a new sync, there should be no real changes.
07/30/13 (mirror) - Initial build, uses fat-tire's repos for device and kernel
For detailed changes see the gerrit page.
Bugs
Focal doesn't work
Two Clock apps, one from Google, one from Android.
Sweet. Been waiting for this. Thanks
the only reason that there are two clocks is because there is one in the cm10.2 zip and the 4.3 gapps.
Can I get a mirror, please? The download always fails at 144MB for me.
Why not use CMs repo? Just edit the manifests default.xml to include the cm10.2 tag, and enter the proper lines to grab the device and vendor file(s) for Grouper?
MBQ_ said:
Why not use CMs repo? Just edit the manifests default.xml to include the cm10.2 tag, and enter the proper lines to grab the device and vendor file(s) for Grouper?
Click to expand...
Click to collapse
I would, but grouper's device and kernel don't as of yet have 10.2 branches. I use fattire's because I believe they are the best I can do until we have official.
fattire said:
* The /device tree is basically 10.1's device plus a bunch of cherry-picked stuff from AOSP 4.3, plus newer SELinux rules, plus my own minor changes.
* The /kernel tree is currently AOSP 4.3 stock with a cyanogenmod_android_defconfig added. None of the customization from 10.1 are here yet.
Click to expand...
Click to collapse
sgt. meow said:
Can I get a mirror, please? The download always fails at 144MB for me.
Click to expand...
Click to collapse
Done
Hi all,
Following advices from the site I successfully compiled a custom kernel from sources, rebuilt boot.img and the ramdisk and flashed it on my S3: it works.
Now I want incrementally upgrade the Linux part using git and the sources at kernel.org, let say to patch the kernel on the disk with the linux online versions 3.0.50, 3.0.51 and so on up to the latest 3.0.100. Never used git before unfortunately
Can someone please point me to an example of the correct command-line to do that? From then on I'll sort the rest by myself, I promise, that would save me a lot of time and unnecessary troubles. Thank you very much.
PU
Look up "git-cherry-pick".
reS28raM said:
Hi all,
Following advices from the site I successfully compiled a custom kernel from sources, rebuilt boot.img and the ramdisk and flashed it on my S3: it works.
Now I want incrementally upgrade the Linux part using git and the sources at kernel.org, let say to patch the kernel on the disk with the linux online versions 3.0.50, 3.0.51 and so on up to the latest 3.0.100. Never used git before unfortunately
Can someone please point me to an example of the correct command-line to do that? From then on I'll sort the rest by myself, I promise, that would save me a lot of time and unnecessary troubles. Thank you very much.
PU
Click to expand...
Click to collapse
Look up "git merge". Also you have to add the tree from kernel.org.
Mine looks like such.
git merge linux/linux-3.4.y
CNexus said:
Look up "git-cherry-pick".
Click to expand...
Click to collapse
Hi mate, I am using your tools to build the images, thanks for that. I'll do
PwnCakes193 said:
Look up "git merge". Also you have to add the tree from kernel.org.
Mine looks like such.
git merge linux/linux-3.4.y
Click to expand...
Click to collapse
Thanks, I'll investigate both of your suggestions! Today it'll be a busy day.
reS28raM said:
Hi mate, I am using your tools to build the images, thanks for that. I'll do that
Thanks, I'll investigate both of your suggestions! Today it'll be a busy day.
Click to expand...
Click to collapse
No problem
You'll probably go with the suggestion after mine, git-cherry-pick is more to add one or a couple commits, rather than a whole mass of commits
Git-merge is for adding larger chunks of commits/merging branches, etc
Hello everyone, I am new to compiling and building roms.. I have learned and read many compiling guides for basic knowledge..
My problem is syncing repo and downloading source code takes a lot to download..like near about 20 GB..!
Is there any trick or any option to minimize the download size..Because, I dont have a good internet connection.!
OJ said:
Hello everyone, I am new to compiling and building roms.. I have learned and read many compiling guides for basic knowledge..
My problem is syncing repo and downloading source code takes a lot to download..like near about 20 GB..!
Is there any trick or any option to minimize the download size..Because, I dont have a good internet connection.!
Click to expand...
Click to collapse
Edit the manifest, look in .repo/manifest.xml, there for example remove the prebuilt toolchains that do not match your system. (for example remove all darwin entries if you are not using a Mac) This saves you like a GB or so. other then that there are not many things you can remove that make a difference, as git is already compressed by itself in the first place.
and the source is not 20gb.. it's more like 6-9gb and unpacked (checked out) like 20gb
It's just very big, and there is not much that can be done about it actually.
broodplank1337 said:
Edit the manifest, look in .repo/manifest.xml, there for example remove the prebuilt toolchains that do not match your system. (for example remove all darwin entries if you are not using a Mac) This saves you like a GB or so. other then that there are not many things you can remove that make a difference, as git is already compressed by itself in the first place.
and the source is not 20gb.. it's more like 6-9gb and unpacked (checked out) like 20gb
It's just very big, and there is not much that can be done about it actually.
Click to expand...
Click to collapse
Ohh ok.. Thanks.. I will try.
OJ said:
Ohh ok.. Thanks.. I will try.
Click to expand...
Click to collapse
Plus, it's mainly going to be the first sync that's gonna use a lot of bandwidth/time/resources
after this you just sync the changes..
have a look at @reddevil's tutorial here in xda university..
shows you exactly what you need!
Since yesterday I'm downloading lineageos 15.1 https://wiki.lineageos.org using repo sync command
It has crossed 30GB and still downloading.
Edit:
2018 April 19th : Downloading has completed at 31GB Today.
Will the download of source resume if i terminate the download (ctrl+c) ?
ps: i'm using repo sync command. (initialized by lineage 14.1)
Because I don't have stable internet connection & power for the laptop.
Still Downloading
Currently downloaded 51 GB and is still downloading...
I was wondering when does it stop?!
UPDATE:
Took about 90 GB
SuperUs8r said:
Currently downloaded 51 GB and is still downloading...
I was wondering when does it stop?!
Click to expand...
Click to collapse
It has been known to take days to complete, depending on the system.
Sent from my SM-S767VL using Tapatalk
I am currently pulling the lineage os 15.1 repository and it is now over 26 GB so the source code is huge and you cannot change it
almost compiled but one error????
make[1]: Nothing to be done for 'dtbs'
any solution...
and
zImage is not there. only "Image" and "Image.gz" present there
is "Image" is zImage? how to check that??
Thank you..
kernel source - Xiaomi mi4i official source
toolchain- NDK version 4.9
Ubuntu 64 bit?
[email protected] said:
OP
Click to expand...
Click to collapse
Change module to be y at defconfig
Also image it's the kernel
Image vs zImage ... You can google it
Also ,micode source code it's full of bugs
faizauthar12 said:
Change module to be y at defconfig
Also image it's the kernel
Image vs zImage ... You can google it
Also ,micode source code it's full of bugs
Click to expand...
Click to collapse
Yeah what he said. Checkout these repos if you need to compile a kernel:
http://gitlab.com/webhaikal/SenseiFerrari
http://github.com/Ferrari-Dev-Team/android_kernel_xiaomi_ferrari
haikalizz said:
Yeah what he said. Checkout these repos if you need to compile a kernel:
[url]http://gitlab.com/webhaikal/SenseiFerrari[/URL]
[url]http://github.com/Ferrari-Dev-Team/android_kernel_xiaomi_ferrari[/URL]
Click to expand...
Click to collapse
yeah i gone through your sensie kernel repo and found that i have to use dtbToolCM to make boot.img so i did it and stuck here...
DTB combiner:
Input directory: '/home/rushabh/KernelDevelopment/Xiaomi_Kernel_OpenSource-ferrari-l-oss/arch/arm64/boot/dts/'
Output file: '/home/rushabh/KernelDevelopment/Xiaomi_Kernel_OpenSource-ferrari-l-oss/arch/arm64/boot/dt.img'
Searching subdir: /home/rushabh/KernelDevelopment/Xiaomi_Kernel_OpenSource-ferrari-l-oss/arch/arm64/boot/dts/include/ ...
=> Found 0 unique DTB(s)
as i have read various threads but can not able to fix this. i have used dtbToolCm and dtbtool (version -3 and -2) also same result..
Really i should had not start making my first kernel with MI...
or it will make me learn more and more..
hahahaha:silly:
the easy steps to make a new kernel
use the entirely CM source code
then just type "make bootimage"
Hi all, I'm trying to build DU on walleye, however I keep running into this error
[ 99% 1439/1440] glob vendor/*/*/*/*/*/*/Android.bp
ninja: error: 'INSTALLED_KERNEL_HEADERS', needed by '/home/everett/~du/out/target/product/walleye/obj/STATIC_LIBRARIES/libgptutils_intermediates/gpt-utils.o', missing and no known rule to make it
17:57:10 ninja failed with: exit status 1
build/core/main.mk:21: recipe for target 'run_soong_ui' failed
make: *** [run_soong_ui] Error 1
Wondering if anyone has a fix, thanks
What kernel source are you using?
providing the log before that would also help.
gbmasterdoctor said:
What kernel source are you using?
Click to expand...
Click to collapse
I'm using Nathan's Kernel Source based on Linux Stable
munchy_cool said:
providing the log before that would also help.
Click to expand...
Click to collapse
Sorry about that, when I get home i'll provide the full logs from the build
munchy_cool said:
providing the log before that would also help.
Click to expand...
Click to collapse
https://pastebin.com/3ybqZEq4
There are the full logs, sorry for not providing them before.
EDIT: Slightly different failure occurs when renaming Kernel source to wahoo and compiling
https://pastebin.com/bRFEBTTj
TCUofficial said:
https://pastebin.com/3ybqZEq4
There are the full logs, sorry for not providing them before.
EDIT: Slightly different failure occurs when renaming Kernel source to wahoo and compiling
https://pastebin.com/bRFEBTTj
Click to expand...
Click to collapse
the one below
Code:
ninja: error: 'kernel/google/wahoo/arch/arm64/configs/flash-walleye_defconfig', needed by '/home/everett/~du/out/target/product/walleye/obj/KERNEL_OBJ/.config', missing and no known rule to make it
17:59:08 ninja failed with: exit status 1
is because the kernel configuration you want to use is not there. you can check in kernel/google/wahoo/arch/arm64/configs
this one
Code:
ninja: error: 'INSTALLED_KERNEL_HEADERS', needed by '/home/everett/~du/out/target/product/walleye/obj/STATIC_LIBRARIES/libgptutils_intermediates/gpt-utils.o', missing and no known rule to make it
17:47:56 ninja failed with: exit status 1
build/core/main.mk:21: recipe for target 'run_soong_ui' failed
is because its not able to find that file.
if you can point me to your device, kernel, vendor trees i can have a look.
munchy_cool said:
if you can point me to your device, kernel, vendor trees i can have a look.
Click to expand...
Click to collapse
Device tree was modified from AICP, I have it here: https://github.com/TCU14/device_google_walleye
The proprietary vendors are also from AICP, here: https://github.com/AICP/proprietary_vendor_google
The kernel source is here: https://github.com/android-linux-stable/wahoo
Thanks for the help, I'm doing my best to fix things on my own and am trying to improve. Unfortunately errors are not my forte
TCUofficial said:
Device tree was modified from AICP, I have it here: https://github.com/TCU14/device_google_walleye
The proprietary vendors are also from AICP, here: https://github.com/AICP/proprietary_vendor_google
The kernel source is here: https://github.com/android-linux-stable/wahoo
Thanks for the help, I'm doing my best to fix things on my own and am trying to improve. Unfortunately errors are not my forte
Click to expand...
Click to collapse
so we need to do it right.
1. fork the repo, then clone it. dont clone and push as a new repo because it's going to be hard to track changes if you get serious about this.
this line below
Code:
TARGET_KERNEL_CONFIG := flash-walleye_defconfig
specifies what kernel config the build is looking for.
https://github.com/TCU14/device_google_walleye/blob/master/walleye/BoardConfig.mk
where does it look for those configs?
well it looks for those configs here
https://github.com/android-linux-stable/wahoo/tree/android-msm-wahoo-4.4-oreo-m2/arch/arm64/configs
so as you can see you dont have that config. so you can use wahoo_defconfig.
Even I am new to this, so i might not be the best guide but i will try my best.
munchy_cool said:
so we need to do it right.
1. fork the repo, then clone it. dont clone and push as a new repo because it's going to be hard to track changes if you get serious about this.
this line below
Code:
TARGET_KERNEL_CONFIG := flash-walleye_defconfig
specifies what kernel config the build is looking for.
https://github.com/TCU14/device_google_walleye/blob/master/walleye/BoardConfig.mk
where does it look for those configs?
well it looks for those configs here
https://github.com/android-linux-stable/wahoo/tree/android-msm-wahoo-4.4-oreo-m2/arch/arm64/configs
so as you can see you dont have that config. so you can use wahoo_defconfig.
Even I am new to this, so i might not be the best guide but i will try my best.
Click to expand...
Click to collapse
Thanks for that, just forked AICP and made my changes, new tree is here: https://github.com/TCU14/device_google_walleye-1
I'll see if I can build or if another error pops up, again thanks for the help
EDIT: Nvm, I am stupid. Back to the kernel headers issue :/
TCUofficial said:
EDIT: Nvm, I am stupid. Back to the kernel headers issue :/
Click to expand...
Click to collapse
make sure to do
Code:
make clean
after a build fails.
Doesn't that do the same thing as make clobber?
TCUofficial said:
Doesn't that do the same thing as make clobber?
Click to expand...
Click to collapse
yes.
munchy_cool said:
yes.
Click to expand...
Click to collapse
Thanks for the help, it's currently building. Fixed some of the issues, haven't updated my repos yet though
TCUofficial said:
Thanks for the help, it's currently building. Fixed some of the issues, haven't updated my repos yet though
Click to expand...
Click to collapse
good luck let us know how it goes.
Ok, the touchscreen appears to have shat itself. Other then that, it booted fine with no hiccups.
Idk what's after the setup because of the touch issue. Grabbing a logcat now, seeing if I can possibly fix it.
EDIT: Can't get logcat because I can't allow debugging... this is ****ing hilarious to me
EDIT: Flashing FlashKernel fixed the touchscreen issue, however Google Services Framework is now force closing. constantly. Going to rebuild with FlashKernel if I can, and use different GAPPS in the build
TCUofficial said:
EDIT: Flashing FlashKernel fixed the touchscreen issue, however Google Services Framework is now force closing. constantly. Going to rebuild with FlashKernel if I can, and use different GAPPS in the build
Click to expand...
Click to collapse
glad you are having more success than i did initially Enjoy
UPDATE: Flash gives me the Kernel headers issue, however I still need to flash the zip for touch. Google Services Framework is still acting stupid, so I'm going to try and build without the PixelGapps vendor. If successful, it should work fine if we flash the Gapps after the first initial boot of the ROM. I'll test MindTheGapps, OpenGapps, BeansGapps, etc and find the most stable out of all of them for the ROM. If the rom works and is stable(Nothing obviously broken) I'll add a Google Plus link in my signature and post another update. For now, I cannot post on XDA as DU is thoroughly against it.
TCUofficial said:
For now, I cannot post on XDA as DU is thoroughly against it.
Click to expand...
Click to collapse
why is DU against posting builds on xda?
munchy_cool said:
why is DU against posting builds on xda?
Click to expand...
Click to collapse
No clue, the closest they have gotten to actually posting was announcing builds were available for Taimen and having users from XDA test the builds. Other then that, they are strongly against it for reasons unknown