Build fails at 99% -- Symlink missing -- LOS15 - Xiaomi Mi Max 2 Questions & Answers

My los15- nougat build stops at 99% with this error:
Non-symlink /out/target/product/oxygen/system/vendor detected!
You cannot install files to /out/target/product/oxygen/system/vendor while building a separate vendor.img!
I have tried a lot of sources and searched the web for a solution.
The only thing a have found in web is this:
https://android.googlesource.com/platform/build/+/3e72ed1%5E%21/
But my makefile does have theses lines.
Does anyone knows how to solve this error ?

harvey186 said:
My los15- nougat build stops at 99% with this error:
Non-symlink /out/target/product/oxygen/system/vendor detected!
You cannot install files to /out/target/product/oxygen/system/vendor while building a separate vendor.img!
I have tried a lot of sources and searched the web for a solution.
The only thing a have found in web is this:
https://android.googlesource.com/platform/build/+/3e72ed1^!/
But my makefile does have theses lines.
Does anyone knows how to solve this error ?
Click to expand...
Click to collapse
Have you got a solution for this ? I am facing the same issue.

Related

Compiling Source

Hi all. I'm trying to compile the froyo source on ubuntu 10.4 64-bit. During 'make' I get this error...
build/tools/apriori/prelinkmap.c(168): library 'libc-ext.so' not in prelink map
make: *** [out/target/product/generic/symbols/system/lib/libc-ext.so] Error 1
I've been searching google for answers for a few days now to no avail. Anyone have any ideas?
Thanks!!
If I was going to guess I would say it probably has something to do with being in a x64 environment. Have you tried setting up a x32 chroot and doing the compiling from there?
Check on this page for basic guidance
https://help.ubuntu.com/community/BasicChroot
I was afraid you were going to say that. I'm just going to rebuild with 32-bit.

[Q] Help building CM for Nook HD+

I've been running CM on my HD+ for the last few months and it's been great. I'm working on making some modifications to the VM and to the kernel and it requires building CM from source. I've already done this with several other devices and have had only minor problems. I'm following the instructions and it can't build. I get the following error:
Code:
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.3.1
CM_VERSION=10.2-20140120-UNOFFICIAL-ovation
TARGET_PRODUCT=cm_ovation
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=cortex-a9
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.7.10-1.16-desktop-x86_64-with-SuSE-12.3-x86_64
HOST_BUILD_TYPE=release
BUILD_ID=JLS36I
OUT_DIR=/home/david/Android/system/out
============================================
make: *** /.config: Is a directory. Stop.
I've searched and haven't found a solution but It seems like I'm missing a manifest or something. I'm wondering if this is missing from 10.2 and I should just try building 11 or if there's a way I can build from source.
Thanks to anyone who can help!
No experience building CM but it looks like maybe /.config instead of ./config got invoked?
Sent from HD+ MAG2GA CM 11 from SD
Did you follow this guide? -> http://wiki.cyanogenmod.org/w/Build_for_ovation (repo init for cm11 instead if cm11 is desired)
Its probably just an error that you made. I don't remember seeing it before.
Edit it doesn't like /.config. That much is obvious. So try to rename or move it or fix your problem to avoid it. (if its ~/.config be careful as that is an important dir.)
There is a .config in /out during building process which is the kernel defconfig file. There is also ~/.config. And that's all I know about that. Look around for .config or google your error with "/.config;" removed and see how the "make: *** is a directory. stop" plain version helps you.
I followed the guide in the wiki but it's a no go. I removed and resynced just in case something didn't pull correctly (wouldn't be the first time). I'm grepping the makefiles for .config to try and narrow down the problem but it doesn't seem to be helping. I've compared the structures of the Galaxy Nexus and the Nook build trees and I don't see any huge differences.
<edit>
Found a bunch of config files but no .config, now I'm even more confused.
ddpruitt said:
I followed the guide in the wiki but it's a no go. I removed and resynced just in case something didn't pull correctly (wouldn't be the first time). I'm grepping the makefiles for .config to try and narrow down the problem but it doesn't seem to be helping. I've compared the structures of the Galaxy Nexus and the Nook build trees and I don't see any huge differences.
<edit>
Found a bunch of config files but no .config, now I'm even more confused.
Click to expand...
Click to collapse
It shouldn't be in what you received with the guide as your getting the device repo, but how you did it or something that is not configured correctly on your os.
Its a bit confusing but the error says what it wants and that's the key.
Edit: Tried to get my build to do the same but no go. Out of ideas for you. Sorry
Some other thoughts based on testing:
You get the correct manifest, etc. with the git and repo sync so again its not with what your getting. That all will build it without that weird error.
If there's no .config file in android/system/out/target/product/ovation/obj/KERNEL_OBJ/ then its because it didn't do enough to put one there yet. That shouldn't be the issue as it will rename a .config dir and continue or if it can't then have a different error.
Did you try make clean or make clobber and try building again?
sandsofmyst said:
It shouldn't be in what you received with the guide as your getting the device repo, but how you did it or something that is not configured correctly on your os.
Its a bit confusing but the error says what it wants and that's the key.
Edit: Tried to get my build to do the same but no go. Out of ideas for you. Sorry
Click to expand...
Click to collapse
I had someone else try it on an Ubuntu machine and it has the same issue. I'll try to get the verygreen repos instead of the official CM ones see if that helps
Duplicated! ...
You have a .config directory in /
Exactly as the error says as I get the same error only by creating one there. Or I should say the exact same error line and no building.
sandsofmyst said:
Duplicated! ...
You have a .config directory in /
Exactly as the error says as I get the same error only by creating one there. Or I should say the exact same error line and no building.
Click to expand...
Click to collapse
You're an absolute genius. For some reason I did have a /.config directory, I never even though of looking in the root directories. Must be some strange KDE issue. I deleted it and build kicked off and it's rolling fine now.

[Q] tpToolbox v41 - Issues & Error ..need help

Hello;
I am very new here and was trying to repair my 16 GB HP TP via other JCS post and forums on youtube, rootzwiki etc. but no success get my touchpad repairs.
recently I found JCS new toolbox v41. and downloaded it. it looks very awesome and easy to use. Thanks JCS for making it easy for people with little tech background......
However, when I run new toolbox v41 on my tp. I got following errors.
1) When I tried to use complete data reset option I get following error
Error: Invalid partition info: end-gap greater than 1 percent of mmc
2) When I tried to use Create WebOS Volume option, It failed again with following error:
>>> Obtaining existing Volume size….
Determining volume size….
Problem w/ vgchange –ay
Error: volsize all failed rc=1
I downloaded CWM DM and Non DM ...and copy files on Palm, Inc. Folder and re-run the toolbox again...but got the same error as above.
can someone help, what should I do next? or if someone direct me which thread I should have to follow?
I had read many many thread on rootzwiki ..still no success yet.... thought HP toolbox v41 can assist me... but still need guidance..
mgul said:
Hello;
I am very new here and was trying to repair my 16 GB HP TP via other JCS post and forums on youtube, rootzwiki etc. but no success get my touchpad repairs.
recently I found JCS new toolbox v41. and downloaded it. it looks very awesome and easy to use. Thanks JCS for making it easy for people with little tech background......
However, when I run new toolbox v41 on my tp. I got following errors.
1) When I tried to use complete data reset option I get following error
Error: Invalid partition info: end-gap greater than 1 percent of mmc
2) When I tried to use Create WebOS Volume option, It failed again with following error:
>>> Obtaining existing Volume size….
Determining volume size….
Problem w/ vgchange –ay
Error: volsize all failed rc=1
I downloaded CWM DM and Non DM ...and copy files on Palm, Inc. Folder and re-run the toolbox again...but got the same error as above.
can someone help, what should I do next? or if someone direct me which thread I should have to follow?
I had read many many thread on rootzwiki ..still no success yet.... thought HP toolbox v41 can assist me... but still need guidance..
Click to expand...
Click to collapse
Have you tried v40? I think v41 is still under development.
saidiadude said:
Have you tried v40? I think v41 is still under development.
Click to expand...
Click to collapse
where can I find all the required files for v40.
Also where can I find ROM for latest working Andriod for TP.
2nd post in this thread: http://forum.xda-developers.com/showthread.php?t=2756314
saidiadude said:
2nd post in this thread: http://forum.xda-developers.com/showthread.php?t=2756314
Click to expand...
Click to collapse
Did you get this working? i'm getting the same errors and I've tried with both versions of TPToolbox but can't get anywhere
I'm just going to bump this. I'm having the same issue with v42. I soft bricked my TP and used TPdebrick to get it to boot again but now I'm having all sorts of issues with TPToolbox. I also think my partitions are hosed as /system and /data both show up as 0mb in TWRP.

[Q] [Help] Porting Ubuntu Touch ti Xperia L

While trying to port Ubuntu touch to Xperia L(codename taoshan) using cm source code an compilation error is arising.
$host Executable: aprotoc (phablet/out/host/linux-x86/obj/EXECUTABLES/aprotoc_intermediates/aprotoc)
$phablet/out/host/linux-x86/obj/EXECUTABLES/aprotoc_intermediates/src/google/protobuf/compiler/parser.o: file not recognized: File truncated
$collect2: error: ld returned 1 exit status
$make: *** [phablet/out/host/linux-x86/obj/EXECUTABLES/aprotoc_intermediates/aprotoc] Error 1
After googling for a while, most of what I got is it's some kinda problem relating with OPENCV,although I've no idea what it is.
I've treid setting ANDROID_OPENCV=/media/vihit/227480fc-d7e5-4de2-ac02-18da54b81aac/android-sdk-linux/opencv-2.4.10/ but couldn't do further steps because most of them are related to QT projects. Does anyone have any idea what I can do?

Can anyone help me?

h.tt.p://forum.android.com.pl/f882/port-5-0-x-cm-12-0-na-mini-2-a-492904/ when I try to install i get this error: Error in /storage/sdcard1/cm-12.0-20150103-PORT-jenad.zip (Status 6) Installation aborted.
Could you ask guys from that forum to move here so maybe I can help them. I think that is updater-script error, but without any updater-script files I can't do.
EDIT: tried with my CM11 updater-script and phone actually go to boot up mode, but I can't get any logcat or even kmesg (dmsg) even with latest adb... I would give a try with this by the end of month with my build, so I would se what is real problem with this CM12 "port"
HI,
I found this in that forum maybe it can help.
Seems that version is based on 4.2.2 not 4.4.4 which can get ART support. My testings on personally built CM12 with 4.4.4 kernel/libs/drivers won't get logcat on boot... Now I need to recreate whole VM and start from stratch (maybe there was issue because before trying to port CM12 to Mini 2 I give a try to my NOA device which failed because of MTK drivers source)

Categories

Resources