I'm trying to add koush's superuser to my aosp build, the build is finally going fine after following the directions on his github readme. I added the local_manifests, which gave errors at first saying no remote fetch defined. I went ahead and defined my remote in the local_manifest.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote fetch="git://github.com" name="github" />
<project name="koush/Superuser" path="external/koush/Superuser" remote="github" revision="master" />
<project name="koush/Widgets" path="external/koush/Widgets" remote="github" revision="master" />
</manifest>
I edited the device/lge/mako/device.mk to redefine the
Code:
SUPERUSER_PACKAGE := com.mypackagename.superuser
as described in the readme as well, the build comes out without errors and I seem to have no built superuser anywhere inside the zip or in the rom after it boots.
Am I just missing something simple that I'm not aware of? any advice or ideas? I'm aware that I could just drop a precompiled apk and binary into the otapackage that I build, I'd rather learn to do it this way though..
Thanks!
VoiD_Dweller said:
I'm trying to add koush's superuser to my aosp build, the build is finally going fine after following the directions on his github readme. I added the local_manifests, which gave errors at first saying no remote fetch defined. I went ahead and defined my remote in the local_manifest.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote fetch="git://github.com" name="github" />
<project name="koush/Superuser" path="external/koush/Superuser" remote="github" revision="master" />
<project name="koush/Widgets" path="external/koush/Widgets" remote="github" revision="master" />
</manifest>
I edited the vendor/lge/mako/boardconfigvendor.mk to redefine the
Code:
SUPERUSER_PACKAGE := com.mypackagename.superuser
as described in the readme as well, the build comes out without errors and I seem to have no built superuser anywhere in the room after it boots.
Am I just missing something simple that I'm not aware of? any advice or ideas? I'm aware that I could just drop a precompiled apk and binary into the otapackage that I build, I'd rather learn to do it this way though..
Thanks!
Click to expand...
Click to collapse
Why don`t you PM a rom dev. Most users cannot help you i guess. Just an idea
gee2012 said:
Why don`t you PM a rom dev. Most users cannot help you i guess. Just an idea
Click to expand...
Click to collapse
Public forum, someone else might find it useful also, if it gets figured out..
err nvm question still stands....
Alright so I've got the whole repo synced, now I need to get the blobs for my device right? I'm building on the evo lte codenamed Jewel
Made an xml file in android/omni/.repo/local_manifest called roomservice.xml
This is what I put inside:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Jewel/proprietary_vendor_HTC" path="vendor/HTC" remote="github" revision="cm-10.2" />
</manifest>
Am I doing everything correctly thus far? Miss anything inbetween repo sync and extracting the proprietary blobs?
numel007 said:
Alright so I've got the whole repo synced, now I need to get the blobs for my device right? I'm building on the evo lte codenamed Jewel
Made an xml file in android/omni/.repo/local_manifest called roomservice.xml
This is what I put inside:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Jewel/proprietary_vendor_HTC" path="vendor/HTC" remote="github" revision="cm-10.2" />
</manifest>
Am I doing everything correctly thus far? Miss anything inbetween repo sync and extracting the proprietary blobs?
Click to expand...
Click to collapse
Not sure what's required for HTC, but I would recommend AGAINST making any manual edits to roomservice.xml - use a different XML file in local_manifests for your own stuff
Entropy512 said:
Not sure what's required for HTC, but I would recommend AGAINST making any manual edits to roomservice.xml - use a different XML file in local_manifests for your own stuff
Click to expand...
Click to collapse
Actually when I checked the file after repo sync, the file didn't even exist. Come to think of it local_manifest wasn't there, so I made it manually. Did I miss something?
Sent from a non-i****
numel007 said:
Actually when I checked the file after repo sync, the file didn't even exist. Come to think of it local_manifest wasn't there, so I made it manually. Did I miss something?
Sent from a non-i****
Click to expand...
Click to collapse
Nope. Although I would change roomservice.xml to your_device_name.xml to stop any potential conflicts. And Entropy512 probably thought you were editing the roomservice.xml referenced here: https://github.com/omnirom/android_build/blob/android-4.3/tools/roomservice.py#L161
numel007 said:
Alright so I've got the whole repo synced, now I need to get the blobs for my device right? I'm building on the evo lte codenamed Jewel
Made an xml file in android/omni/.repo/local_manifest called roomservice.xml
This is what I put inside:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Jewel/proprietary_vendor_HTC" path="vendor/HTC" remote="github" revision="cm-10.2" />
</manifest>
Am I doing everything correctly thus far? Miss anything inbetween repo sync and extracting the proprietary blobs?
Click to expand...
Click to collapse
In order to build an unofficial device, as I have gathered it:
First(after setting up the build environment, of course, which is easily demonstrated with a quick google search), you must create a local_manifest. Basically, when you repo sync, it downloads all of the files included in the manifest, which you received when you did repo init. However, your device files are not included in the manifest because it's unofficial (not supported). In order to get your device files to download with the repo sync, you create the local_manifest. To create a local_manifest,
in cmd,
cd omni (so you get into your rom directory)
mkdir .repo/local_manifests (creates a folder to put your local manifest in)
touch .repo/local_manifests/local_manifest.xml (creates the local manifest.xml)
Now go to your file explorer. open omni directory. there should be nothing, unless you've already repo synced. If you have already repo synced, no worries. press control+h. a hidden folder called .repo will appear. double click it. then >local_manifests> open local_manifest.xml. In this xml, you will need to put your device tree, your kernel tree, and your vendor tree. Additionally, you will need trees that contain common files with other devices. These are all able to be found by looking on your device forum. It looks as though you may have the vendor tree in your local_manifest right now. I have found the items that you need to add to your local_manifest. simply add this:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="github"
fetch="git://github.com/" />
<!-- CyanogenMod -->
<project name="CyanogenMod/android_device_htc_jewel" path="device/htc/jewel" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_device_htc_s4-common" path="device/htc/s4-common" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_device_htc_msm8960-common" path="device/htc/msm8960-common" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_kernel_htc_msm8960" path="kernel/htc/msm8960" remote="github" revision="cm-10.2" />
<!-- Add HTC Proprietary Files -->
<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="cm-10.2" />
<!-- Add qcom-caf source for our phone -->
<project path="hardware/qcom/media-caf" name="SlimRoms/hardware_qcom_media-caf" remote="github" revision="jb4.3" />
<project path="hardware/qcom/display-caf" name="SlimRoms/hardware_qcom_display-caf" remote="github" revision="jb4.3" />
<project path="hardware/qcom/audio-caf" name="SlimRoms/hardware_qcom_audio-caf" remote="github" revision="jb4.3" />
</manifest>
(end)
Save.
Now you repo sync. If you have never repo synced, it'll take a while. If you've already repo synced and just added the local_manifest, it shouldn't take long at all.
Next you have to edit the device tree in order to get it to build and add a line to vendorsetup.sh. However, I have not been able to look at what changes need to be made in order to get it to work. I was gonna take a look at it all on sunday. Maybe someone else can step in here to tell him what he needs to do?
Sent from my TF300T using xda app-developers app
andrewnelson23 said:
In order to build an unofficial device, as I have gathered it:
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
Well gee thanks!
Sent from a non-i****
Alright repo sync with the new local_manifest.xml comes up with this error:
remote: Counting objects: 8, done.
remote: Compressing objects: 100% (3/3), done.
remote: Total 6 (delta 2), reused 5 (delta 1)
Unpacking objects: 100% (6/6), done.
From https://github.com/omnirom/android
4a32d1c..f246d15 android-4.3 -> origin/android-4.3
project .repo/manifests/
Updating 4a32d1c..f246d15
Fast-forward
default.xml | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
fatal: remote github already exists with different attributes
andrewnelson23 said:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="github"
fetch="git://github.com/" />
<!-- CyanogenMod -->
<project name="CyanogenMod/android_device_htc_jewel" path="device/htc/jewel" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_device_htc_s4-common" path="device/htc/s4-common" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_device_htc_msm8960-common" path="device/htc/msm8960-common" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_kernel_htc_msm8960" path="kernel/htc/msm8960" remote="github" revision="cm-10.2" />
<!-- Add HTC Proprietary Files -->
<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="cm-10.2" />
<!-- Add qcom-caf source for our phone -->
<project path="hardware/qcom/media-caf" name="SlimRoms/hardware_qcom_media-caf" remote="github" revision="jb4.3" />
<project path="hardware/qcom/display-caf" name="SlimRoms/hardware_qcom_display-caf" remote="github" revision="jb4.3" />
<project path="hardware/qcom/audio-caf" name="SlimRoms/hardware_qcom_audio-caf" remote="github" revision="jb4.3" />
</manifest>
Click to expand...
Click to collapse
Why SlimRoms qcom-caf when all those projects exist at OmniRom Github? The same goes for android_device_htc_msm8960-common.
These projects should be OmnRom's, because he's going to have enough problems as it is setting up the correct device and vendor trees.
numel007 said:
Alright repo sync with the new local_manifest.xml comes up with this error:
remote: Counting objects: 8, done.
remote: Compressing objects: 100% (3/3), done.
remote: Total 6 (delta 2), reused 5 (delta 1)
Unpacking objects: 100% (6/6), done.
From https://github.com/omnirom/android
4a32d1c..f246d15 android-4.3 -> origin/android-4.3
project .repo/manifests/
Updating 4a32d1c..f246d15
Fast-forward
default.xml | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
fatal: remote github already exists with different attributes
Click to expand...
Click to collapse
Hmm so this either means that you edited something in the default.XML, but that error talks about the remote github existing with different attributes. So when you defined the remote in the local manifest, might be clashing with the manifest remote for github. Hopefully to fix you can just rrmove the <remote> line in the local manifest. I think. I'm not terribly experienced with all of this. Perhaps chasmodo can shed some light on that I know he's much more experience with all of this.
chasmodo said:
Why SlimRoms qcom-caf when all those projects exist at OmniRom Github? The same goes for android_device_htc_msm8960-common.
These projects should be OmnRom's, because he's going to have enough problems as it is setting up the correct device and vendor trees.
Click to expand...
Click to collapse
Oh I wasnt aware of that. I just found the sources of a ROM on his forums and put those in there, didn't even think about looking for the same trees on the omni GH. Again I'm not super experienced. So numel007, if there is a git in the omni GH matching any of the ones listed in the local manifest, put the omni one in instead. So as chasmodo said all of the qcom caf stuff and the device-msm8960.
Sent from my SGH-T999 using xda app-developers app
andrewnelson23 said:
Hmm so this either means that you edited something in the default.XML, but that error talks about the remote github existing with different attributes.
Click to expand...
Click to collapse
It doesn't mean he edited anything in the default.xml or manifest.xml. It probably means that the same qcom projects etc are already defined in the default/manifest, but he has added the different ones with the same attributes (project name and path) to his local_manifest.xm following your advice.
andrewnelson23 said:
Oh I wasnt aware of that.
Click to expand...
Click to collapse
Always check the target Rom Github before offering porting advice.
andrewnelson23 said:
In order to build an unofficial device, as I have gathered it:
First(after setting up the build environment, of course, which is easily demonstrated with a quick google search), you must create a local_manifest. Basically, when you repo sync, it downloads all of the files included in the manifest, which you received when you did repo init. However, your device files are not included in the manifest because it's unofficial (not supported). In order to get your device files to download with the repo sync, you create the local_manifest. To create a local_manifest,
in cmd,
cd omni (so you get into your rom directory)
mkdir .repo/local_manifests (creates a folder to put your local manifest in)
touch .repo/local_manifests/local_manifest.xml (creates the local manifest.xml)
Now go to your file explorer. open omni directory. there should be nothing, unless you've already repo synced. If you have already repo synced, no worries. press control+h. a hidden folder called .repo will appear. double click it. then >local_manifests> open local_manifest.xml. In this xml, you will need to put your device tree, your kernel tree, and your vendor tree. Additionally, you will need trees that contain common files with other devices. These are all able to be found by looking on your device forum. It looks as though you may have the vendor tree in your local_manifest right now. I have found the items that you need to add to your local_manifest. simply add this:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="github"
fetch="git://github.com/" />
<!-- CyanogenMod -->
<project name="CyanogenMod/android_device_htc_jewel" path="device/htc/jewel" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_device_htc_s4-common" path="device/htc/s4-common" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_device_htc_msm8960-common" path="device/htc/msm8960-common" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_kernel_htc_msm8960" path="kernel/htc/msm8960" remote="github" revision="cm-10.2" />
<!-- Add HTC Proprietary Files -->
<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="cm-10.2" />
<!-- Add qcom-caf source for our phone -->
<project path="hardware/qcom/media-caf" name="SlimRoms/hardware_qcom_media-caf" remote="github" revision="jb4.3" />
<project path="hardware/qcom/display-caf" name="SlimRoms/hardware_qcom_display-caf" remote="github" revision="jb4.3" />
<project path="hardware/qcom/audio-caf" name="SlimRoms/hardware_qcom_audio-caf" remote="github" revision="jb4.3" />
</manifest>
(end)
Save.
Now you repo sync. If you have never repo synced, it'll take a while. If you've already repo synced and just added the local_manifest, it shouldn't take long at all.
Next you have to edit the device tree in order to get it to build and add a line to vendorsetup.sh. However, I have not been able to look at what changes need to be made in order to get it to work. I was gonna take a look at it all on sunday. Maybe someone else can step in here to tell him what he needs to do?
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
Hey Thanks for working on this I am going through trying to get a build out for the One S and running into all sorts of build errors when I have some time over the weekend I will compare local_manifests and see what I missed.
numel007 said:
Alright repo sync with the new local_manifest.xml comes up with this error:
remote: Counting objects: 8, done.
remote: Compressing objects: 100% (3/3), done.
remote: Total 6 (delta 2), reused 5 (delta 1)
Unpacking objects: 100% (6/6), done.
From https://github.com/omnirom/android
4a32d1c..f246d15 android-4.3 -> origin/android-4.3
project .repo/manifests/
Updating 4a32d1c..f246d15
Fast-forward
default.xml | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
fatal: remote github already exists with different attributes
Click to expand...
Click to collapse
Remove
<remote name="github"
fetch="https://github.com/" />
From all your local manifests. (Or rename it from github to something else)
1. these steps, I can follow them for my lg g2 to hookup cm10.2 source with Omnirom?
2. Also I got propriatory blobs from the cm10.2 rom, However I notice many more on stock rom, anybody know if I can use all of these or explicitly the ones from the cm10.2 rom?
3. There are also more in the cm rom, can I use all the blobs in the folders or only the ones on the propriatory blob txt?
4. what about the symlinked propriatary files in stock rom folders? Ignore those?
Sent from my LG-D802
This is what I get guess I will have to go through it and sort out the missing things....
Which would you like? [aosp_arm-eng] 16
build/core/product_config.mk:222: *** Can not locate config makefile for product "omni_ville". Stop.
Traceback (most recent call last):
File "build/tools/roomservice.py", line 287, in
fetch_device(device)
File "build/tools/roomservice.py", line 255, in fetch_device
git_data = search_github_for_device(device)
File "build/tools/roomservice.py", line 68, in search_github_for_device
check_repo_exists(git_data)
File "build/tools/roomservice.py", line 52, in check_repo_exists
"roomservice".format(device, android_team))
Exception: ville not found in omnirom Github, exiting roomservice
build/core/product_config.mk:222: *** Can not locate config makefile for product "omni_ville". Stop.
** Don't have a product spec for: 'omni_ville'
** Do you have the right repo manifest?
mo976 said:
This is what I get guess I will have to go through it and sort out the missing things....
Which would you like? [aosp_arm-eng] 16
build/core/product_config.mk:222: *** Can not locate config makefile for product "omni_ville". Stop.
Traceback (most recent call last):
File "build/tools/roomservice.py", line 287, in
fetch_device(device)
File "build/tools/roomservice.py", line 255, in fetch_device
git_data = search_github_for_device(device)
File "build/tools/roomservice.py", line 68, in search_github_for_device
check_repo_exists(git_data)
File "build/tools/roomservice.py", line 52, in check_repo_exists
"roomservice".format(device, android_team))
Exception: ville not found in omnirom Github, exiting roomservice
build/core/product_config.mk:222: *** Can not locate config makefile for product "omni_ville". Stop.
** Don't have a product spec for: 'omni_ville'
** Do you have the right repo manifest?
Click to expand...
Click to collapse
Sounds like you have not added the omni_ville.mk in the vendor/omini/products folder. Add it by copying one that is already in their and edit it for your device
Sent from my Blade III using xda app-developers app
robt77 said:
Sounds like you have not added the omni_ville.mk in the vendor/omini/products folder. Add it by copying one that is already in their and edit it for your device
Click to expand...
Click to collapse
Vendor/omni/products folder does not exist. Device.mk files belong in /device/manufacturer/device folder.
chasmodo said:
Vendor/omni/products folder does not exist. Device.mk files belong in /device/manufacturer/device folder.
Click to expand...
Click to collapse
Do i need to create the above path? For me no manifacturer folder under device
matrixzone said:
Do i need to create the above path? For me no manifacturer folder under device
Click to expand...
Click to collapse
It SHOULD create it when you brunch your device. Mine auto-downloaded and created grouper, tilapia, and manta.
dibblebill said:
It SHOULD create it when you brunch your device. Mine auto-downloaded and created grouper, tilapia, and manta.
Click to expand...
Click to collapse
I am creating for d2att which is not currently supported
Sent from my SAMSUNG-SGH-I747 using Tapatalk
I am trying to build cm11 for my device (samsung a500fu) but Im struggling to create the local manifest file in repo.
I am a newbie, please help me.
I tried to build the rom using this local manifest:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="MSM8916-Samsung/android_device_samsung_a5ultexx" path="device/samsung/a5ulte" remote="github" revision="cm-12.1"/>
<project name="MSM8916-Samsung/android_device_samsung_a5ultexx" path="vendor/samsung/a5ulte" remote="github" revision="cm-12.1"/>
<project name="moonbutt74/kernel_samsung_sm-a500fu.git" path="kernel/samsung/a5ulte" remote="github" revision="master"/>
</manifest>
But I get this error:
brunch a5ulte
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/samsung/a5ulte/cm.mk]]: "device/samsung/a5ultexx/full_a5ultexx.mk" does not exist. Stop.
Device a5ulte not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Traceback (most recent call last):
File "build/tools/roomservice.py", line 76, in <module>
result = json.loads(urllib.request.urlopen(githubreq).read().decode())
File "/usr/lib/python2.7/urllib2.py", line 127, in urlopen
return _opener.open(url, data, timeout)
File "/usr/lib/python2.7/urllib2.py", line 410, in open
response = meth(req, response)
File "/usr/lib/python2.7/urllib2.py", line 523, in http_response
'http', request, response, code, msg, hdrs)
File "/usr/lib/python2.7/urllib2.py", line 448, in error
return self._call_chain(*args)
File "/usr/lib/python2.7/urllib2.py", line 382, in _call_chain
result = func(*args)
File "/usr/lib/python2.7/urllib2.py", line 531, in http_error_default
raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
urllib2.HTTPError: HTTP Error 403: Forbidden
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/samsung/a5ulte/cm.mk]]: "device/samsung/a5ultexx/full_a5ultexx.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_a5ulte
I am using this guide to build:
http://forum.xda-developers.com/nexu...od-11-t2515305
And these are the github sources I could find:
https://github.com/search?utf8=✓&q=a500fu
Edit: IMPORTANT !
Latest version of glibc, the entire C library (2.22-3 on Arch Linux), seems to brakes things for android build: as reported in this other thread by @Poesini (and many others in same thread), previous version of glibc should be right, but the newest isn't OK on Arch. So please, when you updating your system, DO NOT UPDATE GLIBC!. (Downgrading still possible, but isn't the funniest part: -> https://bbs.archlinux.org/viewtopic.php?id=200845). Others Linux Distros (like Ubuntu for example) should be good, as they have not update glibc yet, but PLEASE be aware about this problem!
Thanks @Trafalgar Square for taking the time to help me !
HI all!
Well, have a little problem over here. I'm trying to compile from sources Temasek (6.0.1) for OnePlus Two, with this repo:
Code:
repo init -u https://github.com/temasek/android.git -b cm-13.0
(thanks @temasek)
and this roomservice.xml :
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Trafalgar-Square/android_device_oneplus_oneplus2" path="device/oneplus/oneplus2" remote="github" revision="temasek-mm6.0" />
<project name="benschhold/android_vendor_oneplus" path="vendor/oneplus" remote="github" revision="cm-13.0" />
<project name="benschhold/android_kernel_oneplus_msm8994" path="kernel/oneplus/msm8994" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_external_sony_boringssl-compat" path="external/sony/boringssl-compat" remote="github" revision="cm-13.0" />
<project name="benschhold/android_device_oppo_common" path="device/oppo/common" remote="github" revision="cm-13.0" />
</manifest>
(Thanks @Trafalgar Square by the way).
Well, every time I execute "lunch cm_oneplus2-userdebug" followed by "breakfast cm_oneplus2-userdebug", it's end in:
Code:
flex-2.5.39: loadlocale.c:131: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_COLLATE) / sizeof (_nl_value_type_LC_COLLATE[0]))' failed.
touch /home/bertac_t/android/temasek/out/host/linux-x86/obj/EXECUTABLES/checkpolicy_intermediates/policy_parse.hpp
build/core/binary.mk:662: recipe for target '/home/bertac_t/android/temasek/out/host/linux-x86/obj/EXECUTABLES/checkpolicy_intermediates/policy_scan.cpp' failed
[COLOR="Red"]make: *** [/home/bertac_t/android/temasek/out/host/linux-x86/obj/EXECUTABLES/checkpolicy_intermediates/policy_scan.cpp] Aborted (core dumped)[/COLOR]
make: *** Waiting for unfinished jobs....
echo '#ifndef 'policy_parse_h > /home/bertac_t/android/temasek/out/host/linux-x86/obj/EXECUTABLES/checkpolicy_intermediates/policy_parse.h
Lex: libsepol <= external/selinux/libsepol/cil/src/cil_lexer.l
echo '#define 'policy_parse_h >> /home/bertac_t/android/temasek/out/host/linux-x86/obj/EXECUTABLES/checkpolicy_intermediates/policy_parse.h
flex-2.5.39: loadlocale.c:131: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_COLLATE) / sizeof (_nl_value_type_LC_COLLATE[0]))' failed.
build/core/binary.mk:662: recipe for target '/home/bertac_t/android/temasek/out/host/linux-x86/obj/STATIC_LIBRARIES/libsepol_intermediates/cil/src/cil_lexer.cpp' failed
[COLOR="Red"]make: *** [/home/bertac_t/android/temasek/out/host/linux-x86/obj/STATIC_LIBRARIES/libsepol_intermediates/cil/src/cil_lexer.cpp] Aborted (core dumped)[/COLOR]
cat /home/bertac_t/android/temasek/out/host/linux-x86/obj/EXECUTABLES/checkpolicy_intermediates/policy_parse.hpp >> /home/bertac_t/android/temasek/out/host/linux-x86/obj/EXECUTABLES/checkpolicy_intermediates/policy_parse.h
echo '#endif' >> /home/bertac_t/android/temasek/out/host/linux-x86/obj/EXECUTABLES/checkpolicy_intermediates/policy_parse.h
make: Leaving directory '/home/bertac_t/android/temasek'
where sentences highlight in red seems to be the problem.
I found THIS on XDA, which seems to be a glibc problem. But, well, I've tried to follow the "fix" gave by @martinoff, but no sign of a build_rom script in my directories...
Thanks to all who will help me !
Instructions
Hello and thank you for using Q/A,
. build/envsetup.sh
make clobber
breakfast oneplus2
brunch oneplus2
Kind regards
Trafalgar Square
Trafalgar Square said:
Hello and thank you for using Q/A,
. build/envsetup.sh
make clobber
breakfast oneplus2
brunch oneplus2
Kind regards
Trafalgar Square
Click to expand...
Click to collapse
First, thanks for your answer mate, but still the same error...
New
Hi again,
please try this:
https://raw.githubusercontent.com/Trafalgar-Square/roomservice/temasek-mm6.0/oneplus2.xml
Add this to the end of your cm.mk:
Code:
# Custom unofficial build tag
TARGET_UNOFFICIAL_BUILD_ID := temasek
repo sync --force-sync
make clean
. build/envsetup.sh
breakfast oneplus2
brunch oneplus2
Kind regards
Trafalgar Square
AICP, CyanPop and Temasek maintainer
Up ! Read first post PLEASE !
@Darth, you can close this thread, I just up so people can be informed about this problem.
Thanks man !
Thread closed per OP request. :good: