Related
Problem sloved!
Hi!
I am trying to build cm7 from source for my acer liquid. But about 5 min after starting the build I run into this error:
Install: out/host/linux-x86/bin/simg2img
host Executable: sqlite3 (out/host/linux-x86/obj/EXECUTABLES/sqlite3_intermediates/sqlite3)
/usr/bin/ld: cannot find -lncurses
collect2: ld returned 1 exit status
make: *** [out/host/linux-x86/obj/EXECUTABLES/sqlite3_intermediates/sqlite3] Error 1
I am using Ubuntu 12.04 64 bit on my Laptop with an AMD E-350 processor.
All help welcome,
Alex
iKrautDroid said:
Hi!
I am trying to build cm7 from source for my acer liquid. But about 5 min after starting the build I run into this error:
Install: out/host/linux-x86/bin/simg2img
host Executable: sqlite3 (out/host/linux-x86/obj/EXECUTABLES/sqlite3_intermediates/sqlite3)
/usr/bin/ld: cannot find -lncurses
collect2: ld returned 1 exit status
make: *** [out/host/linux-x86/obj/EXECUTABLES/sqlite3_intermediates/sqlite3] Error 1
I am using Ubuntu 12.04 64 bit on my Laptop with an AMD E-350 processor.
All help welcome,
Alex
Click to expand...
Click to collapse
Make sure you have all the needed packages to build.
yea, install the required packages for 12.04 here
Hmm, i just ran:
sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-dev:i386 \
g++-multilib mingw32 openjdk-6-jdk tofrodos python-markdown \
libxml2-utils xsltproc zlib1g-dev:i386
again and it installed libncurses5, which for some reason wasnt installed when I first set up my build environment. Thanks lithid, problem solved!
I have been wandering around the question and answers forum for some time now...i noticed a thing that most of them who had errors building from source have been left un answered..
i assume the following reasons for this
1)no dev would really care to search through and help out
2)users are scared to pm dev's
3)their posts are getting lost due to no actiivity within seconds of posting
as a outcome of all the above
the user isn't getting help
so i thought of making a thread for just source build errors..
so this this thread will focus on providing answers for all the problems that you are facing while building from source......
now i would like the users to follow a format similar to this for reporting
1)A full error encountered (pastie or any similar site's
2)your device name
3)your device tree that you have used for compiling(github link)
4)which rom are you building(cm aokp etc)
5)The guide which you are using to build(link)
another kind request please spread the link for this thread as many may benefit from it....
and find developers who are interested in helping....
feel free to give suggestions....
Before you move ahead make sure you copy paste this into the terminal
32bit users(ics & below)
HTML:
sudo apt-get install git-core gnupg flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev valgrind squashfs-tools zip curl pngcrush schedtool ia32-libs x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 libwxgtk2.6-dev
64bit ( you need this in addition with 32bit packages)
HTML:
sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs \
x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev \
libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown \
libxml2-utils gcc-4.3-multilib g++-4.3-multilib g++-multilib
common build errors
HTML:
build/core/product_config.mk:196: *** _nic.PRODUCTS.[[device/YG/m805_892x/device_m805_892x.mk]]: "device/YG/m805_892x/m805_892x-vendor-blobs.mk" does not exist. Stop.
cause for problem
device_m805_892x.mk
Here in your device folder it is calling a make file which is required for compiling as in this case (device_m805_892x.mk) has a reference to
(device/YG/m805_892x/m805_892x-vendor-blobs.mk)
check if
(m805_892x-vendor-blobs.mk)
is there in vendors folder... as in this case this is not found ..
solution
1)remove the reference to that makefile..
2)check the path for makefile(these are case sensitive)
3)correct the makefile in vendor folder to match that in the makefile that has called it
2)
HTML:
make: *** No rule to make target `vendor/cm/proprietary/RomManager.apk', needed by `out/target/product/m805_892x/system/app/RomManager.apk'. Stop.
make: *** Waiting for unfinished jobs....
cause for the problem
Here the script is written to copy rommanager.apk to system app during the build process...
But the apk is missing which is stoping the make process
solution
cd into vendors/cm
then type this
HTML:
./get-prebuilts
IF some dev helps you out show your appreciation by using the thanks button
reserved 2
the last one reserved
dude, you rock..
anyways, im still building the same pac...since my initial build wouldn't boot, i decided to switch up some of the internals...
PHP:
build/core/base_rules.mk:171: *** frameworks/native/cmds/sensorservice: MODULE.TARGET.EXECUTABLES.sensorservice already defined by frameworks/base/cmds/sensorservice. Stop.
Ive asked this question so many times, im ready to go nuts...ive looked thru every file and i cant find where these are referenced...where do i redirect this? and any other that may error back the already defined?
Contribute :
So..... A great thread to help all the beginners and the developers ( as everybody are prone to make mistakes ) I'd like to help too
But at first.... With reference to the problems I've encountered so far from different users.. all tat i see is most of them forget to install the necessary packages that are required for the build....
I've made a general command tat would hold most of the packages that are required for the build
For 32 Bit :
Code:
sudo apt-get install git-core gnupg flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev valgrind squashfs-tools zip curl pngcrush schedtool ia32-libs x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 libwxgtk2.6-dev
For 64 Bit :
Code:
sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs \
x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev \
libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown \
libxml2-utils gcc-4.3-multilib g++-4.3-multilib g++-multilib
Ps : I'd add more as and when needed as we encounter new problems
---------- Post added at 10:49 AM ---------- Previous post was at 10:49 AM ----------
Reserved just in case
---------- Post added at 10:53 AM ---------- Previous post was at 10:49 AM ----------
cbucz24 said:
dude, you rock..
anyways, im still building the same pac...since my initial build wouldn't boot, i decided to switch up some of the internals...
PHP:
build/core/base_rules.mk:171: *** frameworks/native/cmds/sensorservice: MODULE.TARGET.EXECUTABLES.sensorservice already defined by frameworks/base/cmds/sensorservice. Stop.
Ive asked this question so many times, im ready to go nuts...ive looked thru every file and i cant find where these are referenced...where do i redirect this? and any other that may error back the already defined?
Click to expand...
Click to collapse
It would help us more to understand the problem if u could provide the device tree that u r using ( Github Link )
cbucz24 said:
dude, you rock..
anyways, im still building the same pac...since my initial build wouldn't boot, i decided to switch up some of the internals...
PHP:
build/core/base_rules.mk:171: *** frameworks/native/cmds/sensorservice: MODULE.TARGET.EXECUTABLES.sensorservice already defined by frameworks/base/cmds/sensorservice. Stop.
Ive asked this question so many times, im ready to go nuts...ive looked thru every file and i cant find where these are referenced...where do i redirect this? and any other that may error back the already defined?
Click to expand...
Click to collapse
it seems that a single service (sensorservice) is defined in two places your tree would help... and spread the word about this thread as it ma help many people out just a request...
your error is like your destination is x
and there are two paths leading to it and you are confused which one to take..
so it has stopped ok try deleting
frameworks/base/cmds/sensorservice
or
frameworks/native/cmds/sensorservice
(one of two not both
)
I would like to share some solution to some basic build problems. I did copy this from my own thread here:
http://forum.xda-developers.com/showthread.php?t=1935162
Fix problems... This the learning part.. Fun but can be really anoying to.
First i got my self:
make otatools did not work.
-Try make -j4 out/host/linux-x86/bin/unpackbootimg
-put "unpackbootimg" in ~/android/system/out/host/linux-x86/bin then i copy it to ~/usr/bin and set chmod.
Im did see a download if it some place. Google.
-copy unpackbootimg to into /usr/bin If it is there, make it executable.
make executable: sudo chmod a+x /usr/bin/unpackbootimg
-Run make clubber from The ICS folder. Than restart pc might help to.
Nother problem that i did run into trying to make ext4 images:
make_ext4fs -s -l 0x40000000 -a data out/target/product/m805_892x/userdata.img out/target/product/m805_892x/data
Need size of filesystem
make: *** [out/target/product/m805_892x/userdata.img] Error 4
make: *** Waiting for unfinished jobs..
The sizes need to be in bytes it seems.
make_ext4fs does not support hex in the -l argument
DD dump you´re partitions and you see the amount of bytes.
I put this in my BoardConfig.mk like this:
BOARD_USERDATAIMAGE_PARTITION_SIZE := 1073741824
Use this to finisch waiting jobs..:
make_ext4fs -s -l 1073741824 -a data out/target/product/m805_892x/userdata.img out/target/product/m805_892x/data
problem:
[email protected]:~/ICS$ make -j4 recoveryimage
build/core/product_config.mk:196: *** _nic.PRODUCTS.[[device/YG/m805_892x/device_m805_892x.mk]]: "device/YG/m805_892x/m805_892x-vendor-blobs.mk" does not exist. Stop.
The error is somewhare found in this file:
device_m805_892x.mk I used the original file and start adding things again.
Problem:
make: *** No rule to make target `vendor/cm/proprietary/RomManager.apk', needed by `out/target/product/m805_892x/system/app/RomManager.apk'. Stop.
make: *** Waiting for unfinished jobs....
Copy: out/target/product/m805_892x/system/bin/compcache
Copy: out/target/product/m805_892x/system/bin/handle_compcache
[email protected]:~/ICS$
For that use the terminal and cd to:
cd /vendor/cm
run:
./get-prebuilts
This will download the RomManager.apk and bit of other stuff.
[email protected] said:
I would like to share some solution to some basic build problems. I did copy this from my own thread here:
http://forum.xda-developers.com/showthread.php?t=1935162
Fix problems... This the learning part.. Fun but can be really anoying to.
First i got my self:
make otatools did not work.
-Try make -j4 out/host/linux-x86/bin/unpackbootimg
-put "unpackbootimg" in ~/android/system/out/host/linux-x86/bin then i copy it to ~/usr/bin and set chmod.
Im did see a download if it some place. Google.
-copy unpackbootimg to into /usr/bin If it is there, make it executable.
make executable: sudo chmod a+x /usr/bin/unpackbootimg
-Run make clubber from The ICS folder. Than restart pc might help to.
Nother problem that i did run into trying to make ext4 images:
make_ext4fs -s -l 0x40000000 -a data out/target/product/m805_892x/userdata.img out/target/product/m805_892x/data
Need size of filesystem
make: *** [out/target/product/m805_892x/userdata.img] Error 4
make: *** Waiting for unfinished jobs..
The sizes need to be in bytes it seems.
make_ext4fs does not support hex in the -l argument
DD dump you´re partitions and you see the amount of bytes.
I put this in my BoardConfig.mk like this:
BOARD_USERDATAIMAGE_PARTITION_SIZE := 1073741824
Use this to finisch waiting jobs..:
make_ext4fs -s -l 1073741824 -a data out/target/product/m805_892x/userdata.img out/target/product/m805_892x/data
problem:
[email protected]:~/ICS$ make -j4 recoveryimage
build/core/product_config.mk:196: *** _nic.PRODUCTS.[[device/YG/m805_892x/device_m805_892x.mk]]: "device/YG/m805_892x/m805_892x-vendor-blobs.mk" does not exist. Stop.
The error is somewhare found in this file:
device_m805_892x.mk I used the original file and start adding things again.
Problem:
make: *** No rule to make target `vendor/cm/proprietary/RomManager.apk', needed by `out/target/product/m805_892x/system/app/RomManager.apk'. Stop.
make: *** Waiting for unfinished jobs....
Copy: out/target/product/m805_892x/system/bin/compcache
Copy: out/target/product/m805_892x/system/bin/handle_compcache
[email protected]:~/ICS$
For that use the terminal and cd to:
cd /vendor/cm
run:
./get-prebuilts
This will download the RomManager.apk and bit of other stuff.
Click to expand...
Click to collapse
i will add this to op... i will expalin the problem the cause for it and the fix for it..i will explain stuff and type it in general for all devices..btw thanks for the reply ... will update the op soon..
So I've subscribed to this thread and I'll help when I can I've built about seven different ROMs and have had to solve allot of issues lol
Sent from my SAMSUNG-SGH-I577 using xda premium
ktempleton said:
So I've subscribed to this thread and I'll help when I can I've built about seven different ROMs and have had to solve allot of issues lol
Sent from my SAMSUNG-SGH-I577 using xda premium
Click to expand...
Click to collapse
thank you for helping..i too have done a lot of source builds and faced hell lot of problems so i made this as a general thread to get help and help other's too...
Great Thread
Really very helpful thread for beginners. Keep on updating this thread. I will post my errors later
RishabhAd said:
Really very helpful thread for beginners. Keep on updating this thread. I will post my errors later
Click to expand...
Click to collapse
thank you for the support spread the thread so that more people get benfited...
Sticky please
Help Please
Getting this error while compiling for Samsung Galaxy Fit. I have used CM 10's device config & did changes as mentioned. Please any there help me
http://pastebin.com/QW2ViEDk
RishabhAd said:
Getting this error while compiling for Samsung Galaxy Fit. I have used CM 10's device config & did changes as mentioned. Please any there help me
http://pastebin.com/QW2ViEDk
Click to expand...
Click to collapse
Code:
packages/apps/Bluetooth/src/com/android/bluetooth/map/BluetoothMasService.java:394: cannot find symbol
symbol : variable REQUEST_TYPE_MESSAGE_ACCESS
location: class android.bluetooth.BluetoothDevice
BluetoothDevice.REQUEST_TYPE_MESSAGE_ACCESS);
^
packages/apps/Bluetooth/src/com/android/bluetooth/map/BluetoothMasService.java:458: cannot find symbol
symbol : variable REQUEST_TYPE_MESSAGE_ACCESS
location: class android.bluetooth.BluetoothDevice
BluetoothDevice.REQUEST_TYPE_MESSAGE_ACCESS);
The part thats causing u the errors... !!!!
check the files BluetoothMasService.java and BluetoothMasService.java with the one in CM10 repo nd see wat is missing
RishabhAd said:
Getting this error while compiling for Samsung Galaxy Fit. I have used CM 10's device config & did changes as mentioned. Please any there help me
http://pastebin.com/QW2ViEDk
Click to expand...
Click to collapse
What repo are you using I'll post a thread in aa min you need to get the repo for utackas repo because pa repo is broke
http://forum.xda-developers.com/showthread.php?p=35507138
Don't know if your using this repo but I was getting errors like that until I switched
Sent from my SAMSUNG-SGH-I577 using xda premium
wilfredcool007 said:
Code:
packages/apps/Bluetooth/src/com/android/bluetooth/map/BluetoothMasService.java:394: cannot find symbol
symbol : variable REQUEST_TYPE_MESSAGE_ACCESS
location: class android.bluetooth.BluetoothDevice
BluetoothDevice.REQUEST_TYPE_MESSAGE_ACCESS);
^
packages/apps/Bluetooth/src/com/android/bluetooth/map/BluetoothMasService.java:458: cannot find symbol
symbol : variable REQUEST_TYPE_MESSAGE_ACCESS
location: class android.bluetooth.BluetoothDevice
BluetoothDevice.REQUEST_TYPE_MESSAGE_ACCESS);
The part thats causing u the errors... !!!!
check the files BluetoothMasService.java and BluetoothMasService.java with the one in CM10 repo nd see wat is missing
Click to expand...
Click to collapse
I tried i think this is d error of source.
ktempleton said:
What repo are you using I'll post a thread in aa min you need to get the repo for utackas repo because pa repo is broke
http://forum.xda-developers.com/showthread.php?p=35507138
Don't know if your using this repo but I was getting errors like that until I switched
Sent from my SAMSUNG-SGH-I577 using xda premium
Click to expand...
Click to collapse
u compiled by using utacka's repo? n what is d size of source?
ktempleton said:
What repo are you using I'll post a thread in aa min you need to get the repo for utackas repo because pa repo is broke
http://forum.xda-developers.com/showthread.php?p=35507138
Don't know if your using this repo but I was getting errors like that until I switched
Sent from my SAMSUNG-SGH-I577 using xda premium
Click to expand...
Click to collapse
Ummm, how long has the pa repo been broken? I did see that someone said something about it. Reason I'm asking, In building PAC and part of the manifest pulls from PA doesn't it? Could that be causing my problems?
Sent from my PC36100 using Tapatalk 2
Have you erased one of those files the error pointed to
My PAC runs fine but when I ran it for the first time I had maybe four duplicates I had to take care of
Sent from my SAMSUNG-SGH-I577 using xda premium
ktempleton said:
Have you erased one of those files the error pointed to
My PAC runs fine but when I ran it for the first time I had maybe four duplicates I had to take care of
Sent from my SAMSUNG-SGH-I577 using xda premium
Click to expand...
Click to collapse
well, i think i have to switch one or two more items in my local_manifest...i saw that git links i was using are not going to be updated any longer due to another dev going forward with the project.
but before i can switch them all out, i have to make sure i have the links right..but github is down so im kinda stuck for a bit
Heloo every one !
i just have format my win7 & install win8 64bit ,
i face problem with my kitchen !!
it was installed correctly before i format my pc !
but now it giving me this error after i press ./menu !!
Code:
[COLOR="Black"]Welcome to dsixda's Android Kitchen
Please wait ..
Error: The application 'gcc' is not installed - the kitchen
will not function properly without it. Ensure you did
not miss a step during installation! Refer to the
Android Kitchen FAQ at xda-developers.com for further
assistance.
** PLEASE READ THE FAQ BEFORE ASKING QUESTIONS!! **[/COLOR]
i tried to uninstall it and install fresh version but still i have this issue ?!
is my win8 64bit related to this issue ?
am working now to dev. a new rom but i face this problem and i need to fix my kitchen !?
i use some solution :
- re-install java sdk
-re-install gcc 3 times !
- fixing compatibility thing !
-all packages already checked & installed
-Also i move it to another part of hard desk !
i Already search google =D
Try this...just in case you're missing anything. That is everything you could need to build from source...therefore should be good enough for kitchen
sudo apt-get install git gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386
Haze028 said:
Try this...just in case you're missing anything. That is everything you could need to build from source...therefore should be good enough for kitchen
sudo apt-get install git gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386
Click to expand...
Click to collapse
Code:
-bash: sudo: command not found
still same problem =)
Probs
Hey, I've got a problem with KITCHEN on Porting a ROM. Here it is. The Kitchen's thread is closed, I dont have any idea who am I going to approach.
Converting to update-script, please wait ...
- Initial formatting ...
- assert ...
- write_raw_image ...
- run_program ...
- delete ...
- symlink ...
scripts/convert_updater_script: line 386: diff: command not found
ERROR: Problem converting symlinks
ChristianFerrer said:
Hey, I've got a problem with KITCHEN on Porting a ROM. Here it is. The Kitchen's thread is closed, I dont have any idea who am I going to approach.
Converting to update-script, please wait ...
- Initial formatting ...
- assert ...
- write_raw_image ...
- run_program ...
- delete ...
- symlink ...
scripts/convert_updater_script: line 386: diff: command not found
ERROR: Problem converting symlinks
Click to expand...
Click to collapse
Here Sir. This is the best and absolutely most functional Kitchen ever built to this point that's currently compatible to more devices than any others ever before this one built. This should take care of your needs and the Developer stays on the projects to improve functions and improve compatibility across the board. I highly doubt you'll be disappointed.
http://forum.xda-developers.com/showthread.php?p=62845957
Gratefully sent from my Rooted N9510 JollyRoger4G
There's an easy way to do whatever's discussed below, except for a) getting the SDK, b) syncing the repos, and c) building the ROM; and that way is using this script. But it's still better to do the steps below manually as it gets you acquainted with the terminal - you'll be using it a lot.
Thanks to @klvnhng for the original tutorial for mako
Credits to him.
You will need:
A computer running Ubuntu with at least 2GB memory and around 40-65 GB of free space
If you don't want to install Ubuntu, run it instead in VMWare Player or VirtualBox.
make sure you provide the virtual machine with the amount of recommended disk space or more
give it no less than 3-4GB of RAM
A (preferably fast) internet connection (trust me, you don't want to do this with a 256 or 512 kbps connection)
Familiarity with Android and Linux. Read up at source.android.com.
Setting up the build environment
1. Install JDK
DO NOT USE OPENJDK. Remove it by entering
Code:
sudo apt-get purge openjdk* icedtea* icedtea-6*
Install Oracle Java 6 by typing this into a terminal:
Code:
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java6-installer
Android SDK requires the x86 compatibility packages, ia32-libs. Install it by entering this:
Code:
sudo apt-get -y install ia32-libs
As an alternative, you can also do this (thanks to @jjchico):
Code:
sudo apt-get install lsb-release lib32gcc1 libc6-i386 lib32z1 lib32stdc++6 lib32bz2-1.0 lib32ncurses5
2. Android SDK
Download it here.
Extract it to a folder of your choice (in this guide, I will refer to it as ~/android/sdk).
Enter these commands into the terminal:
Code:
cd ~/android/sdk/adt-bundle/sdk/tools
./android sdk
Click Install packages. cd to ~/android/sdk/adt-bundle/sdk/platform-tools and type:
Code:
./adb
./fastboot
If you've done everything correctly, you should get a big block of text for both (which list all of the adb/fastboot commands).
3. Install required packages
Copy and paste this command into the terminal:
Code:
sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl zlib1g-dev zlib1g-dev:i386 libc6-dev lib32ncurses5-dev \
ia32-libs x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 \
lib32z-dev libgl1-mesa-dev g++-multilib mingw32 \
tofrodos python-markdown libxml2-utils xsltproc readline-common \
libreadline6-dev libreadline6 lib32readline-gplv2-dev libncurses5-dev \
lib32readline5 lib32readline6 libreadline-dev libreadline6-dev:i386 \
libreadline6:i386 bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev lib32bz2-dev \
libsdl1.2-dev libesd0-dev squashfs-tools pngcrush schedtool libwxgtk2.8-dev
4. Install the repo command
Make directories called bin and android in your home folder, respectively.
Code:
mkdir -p ~/bin
mkdir -p ~/android
Download and setup the repo binary:
Code:
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
Now add it to your path:
Code:
export PATH="$PATH:~/bin"
And make sure it belongs in your path between subsequent reboots:
Code:
echo "export PATH="$PATH:~/android/sdk:~/bin"" >> ~/.bashrc
source ~/.bashrc
5. Configuring USB
You must configure USB to detect your Android device(s) properly.
Do this in a terminal:
Code:
curl https://raw.githubusercontent.com/aureljared/build-env-init/master/51-android.rules > ~/bin/51-android.rules
chmod a+r ~/bin/51-android.rules
sudo cp -vfp ~/bin/51-android.rules /etc/udev/rules.d/51-android.rules
6. Syncing up
The next step is to initialize the repository and download the source code to your computer.
Type the following lines into the terminal:
Code:
mkdir -p ~/android/cm-11.0
cd ~/android/cm-11.0
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
To download all the necessary device-specific files for our device, do this:
Code:
curl https://raw.githubusercontent.com/aureljared/android-manifests/expresslte-cm-11.0/local_manifest.xml >> .repo/local_manifests/local_manifest.xml
Now run
Code:
repo sync
You have now begun downloading all of the CM source code to your build directory. Depending on your internet speed, this can take from a couple of hours to a few days. If the sync interrupts, don't worry. Simply continue the sync (you don't have to restart completely, only the project you were downloading when the interrupt occured, lol) by entering:
Code:
repo sync
Some tips:
You can interrupt the process by pressing Ctrl + C, it will continue where it left off the next time anyway.
Remember, you need to cd into your build directory (~/android/cm-11.0, if you've been following this guide) for the command to work.
If you want only one project to be synced at a time, run repo sync -j1 instead.
This step takes a long time depending on your internet connection speed (FYI you're downloading ~20 GB of code!)
7. Building CM (yay!)
You must download the necessary pre-built apps:
Code:
~/android/cm-11.0/vendor/cm/get-prebuilts
Now let's build! cd to your build directory and run the following commands in the terminal:
Code:
. build/envsetup.sh
brunch expressltexx
Now, just let your computer do the rest. This step is very demanding for your computer, so you better leave it alone while it builds. Usually this takes an hour or more. Go get some sleep or eat something.
Done? If everything went correctly, cd to ~/android/cm-11.0/out/target/product/expresslte and you should see your newly built ROM entitled:
cm-11.0-20xxxxxx-UNOFFICIAL-expressltexx.zip
Congratulations! You've successfully built CM 11.0!
For re-builds (i.e. when the source code has been updated and you would like to make a new nightly), just do this:
Code:
cd ~/android/cm-11.0
make clobber
repo sync
. build/envsetup.sh
brunch expressltexx
Have fun building!
I suggest you to modify step 5 inserting before repo sync
Code:
mkdir .repo/local_manifests
cd .repo/local_manifests
wget https://raw.github.com/KINGbabasula/android_device_samsung_expresslte/cm-10.2/local_manifest.xml
cd ..
cd ..
This will download the specific necessary repos with repo sync
Then remove this in step 6
Code:
mkdir files
cd files
git clone https://github.com/KINGbabasula/proprietary_vendor_samsung.git
as it isn't needed
And change make clean with make clobber because with clobber it will rebuild faster
EDIT: And before step 6 you need to replace these 2 files with the 2 in the attachment
Code:
system/core/mkbootimg/bootimg.h
system/core/mkbootimg/mkbootimg.c
KINGbabasula said:
I suggest you to modify step 5 inserting before repo sync
Code:
mkdir .repo/local_manifests
cd .repo/local_manifests
wget https://raw.github.com/KINGbabasula/android_device_samsung_expresslte/cm-10.2/local_manifest.xml
cd ..
cd ..
This will download the specific necessary repos with repo sync
Then remove this in step 6
Code:
mkdir files
cd files
git clone https://github.com/KINGbabasula/proprietary_vendor_samsung.git
as it isn't needed
And change make clean with make clobber because with clobber it will rebuild faster
EDIT: And before step 6 you need to replace these 2 files with the 2 in the attachment
Code:
system/core/mkbootimg/bootimg.h
system/core/mkbootimg/mkbootimg.c
Click to expand...
Click to collapse
Original post updated.
Can you help me with ia32-libs?
It says that it's referred to by a handful of other packages but it has no installation candidates or something. The bottom line is that I can't install it.
I'm using 13.10 x64 on an ASUS K43SJ.
- Intel i5-2410M Quadcore (2.3GHz normal, 2.9GHz Turbo Boost)
- 2GB RAM available to Ubuntu VM
Sent from my International Galaxy Express using Tapatalk 4
aureljared said:
Original post updated.
Can you help me with ia32-libs?
It says that it's referred to by a handful of other packages but it has no installation candidates or something. The bottom line is that I can't install it.
I'm using 13.10 x64 on an ASUS K43SJ.
- Intel i5-2410M Quadcore (2.3GHz normal, 2.9GHz Turbo Boost)
- 2GB RAM available to Ubuntu VM
Sent from my International Galaxy Express using Tapatalk 4
Click to expand...
Click to collapse
You have to apt-get install every missing library one by one
Inviato dal mio GT-I9070 utilizzando Tapatalk
aureljared said:
2. Android SDK
Download it here.
Extract it to a folder of your choice (in this guide, I will refer to it as ~/android/sdk).
Enter these commands into the terminal:
Code:
cd ~/android/sdk/adt-bundle/sdk/tools
./android sdk
Click Install packages. cd to ~/android/sdk/adt-bundle/sdk/platform-tools and type:
Code:
adb
fastboot
Click to expand...
Click to collapse
Shouldn't it be
Code:
./adb
./fastboot
Or have you added the sdk to your path?
I guess the compilation process will need the sdk. How does it find the sdk? Do you need to provide the path anywhere?
Thanks for the great tuto.
These are the libs that ia32-libs pulls in that are present in Ubuntu 13.10. This should be equivalent to install ia32-libs in Ubuntu 12.04:
$ sudo apt-get install lsb-release lib32gcc1 libc6-i386 lib32z1 lib32stdc++6 lib32bz2-1.0 lib32ncurses5
---------- Post added at 12:08 PM ---------- Previous post was at 11:29 AM ----------
These are the libs that ia32-libs pulls in that are present in Ubuntu 13.10. This should be equivalent to install ia32-libs in Ubuntu 12.04:
$ sudo apt-get install lsb-release lib32gcc1 libc6-i386 lib32z1 lib32stdc++6 lib32bz2-1.0 lib32ncurses5
jjchico said:
These are the libs that ia32-libs pulls in that are present in Ubuntu 13.10. This should be equivalent to install ia32-libs in Ubuntu 12.04:
$ sudo apt-get install lsb-release lib32gcc1 libc6-i386 lib32z1 lib32stdc++6 lib32bz2-1.0 lib32ncurses5
---------- Post added at 12:08 PM ---------- Previous post was at 11:29 AM ----------
These are the libs that ia32-libs pulls in that are present in Ubuntu 13.10. This should be equivalent to install ia32-libs in Ubuntu 12.04:
$ sudo apt-get install lsb-release lib32gcc1 libc6-i386 lib32z1 lib32stdc++6 lib32bz2-1.0 lib32ncurses5
Click to expand...
Click to collapse
jjchico said:
Shouldn't it be
Code:
./adb
./fastboot
Or have you added the sdk to your path?
I guess the compilation process will need the sdk. How does it find the sdk? Do you need to provide the path anywhere?
Thanks for the great tuto.
Click to expand...
Click to collapse
Updated original post.
Sent from my GT-I8730 using Tapatalk
Thanks. Just note the missing double quotes in the export PATH.
Enviado desde mi GT-I9000 mediante Tapatalk
jjchico said:
Thanks. Just note the missing double quotes in the export PATH.
Enviado desde mi GT-I9000 mediante Tapatalk
Click to expand...
Click to collapse
Haha lol sorry. I was very sleepy when I updated last night.
Updated post.
My repo sync is finished with 65 out of 401 projects. ia32-libs now okay thanks to you @jjchico.
Sent from my GT-I8730 using Tapatalk
I get this
[email protected]:~/android/cm-10.2$ repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
No command 'repo' found, did you mean:
Command 'repro' from package 'repro' (universe)
Command 'repl' from package 'nmh' (universe)
Command 'repl' from package 'mailutils-mh' (universe)
Command 'rep' from package 'rep' (universe)
repo: command not found
[email protected]:~/android/cm-10.2$
Any ideas? All seemed good before that
Bazzan
Check that repo is in the bin folder in your user main folder.
Check that repo is executable
chmod a+x ~/bin/repo
Enviado desde mi GT-I9000 mediante Tapatalk
"6. Building CM (yay!)"
"In order to make a working build, you have to get the proprietary files (mainly device build files and drivers) for the device."
so how do I get the propriety files and where do I put them? ADB from your phone?
After this you direct us to prebuilt apps so it appears there is a step missing unless I am pulling proprietary files down from KINGbabasula's Github
Bazzan
bazzan said:
"6. Building CM (yay!)"
"In order to make a working build, you have to get the proprietary files (mainly device build files and drivers) for the device."
so how do I get the propriety files and where do I put them? ADB from your phone?
After this you direct us to prebuilt apps so it appears there is a step missing unless I am pulling proprietary files down from KINGbabasula's Github
Bazzan
Click to expand...
Click to collapse
Yeah, the files are located somewhere in KINGbabasula's github. If you want to use ADB then refer to the text file located in android_device_samsung_expresslte.
Or if you want to download the files themselves, do this in a terminal:
Code:
mkdir proprietary
cd proprietary
git clone https://github.com/KINGbabasula/proprietary_vendor_samsung.git
The files will be located in proprietary/proprietary_vendor_samsung/expresslte.
Sent from my GT-I8730 using Tapatalk
Finally got build going. Thanks for the tutorial @aureljared. You were not kidding when you said takes a while. Not too sure where to from here. Welcome suggestions if anyone wants me to try anything
Bazzan
URGENT
Before proceeding to build any more ROMs, let me ask some questions.
What toolchain for building the kernel are you using? Toolchains that might work are arm-eabi-4.4.3 upwards or linaro 4.4.3 upwards.
What is your configuration for the kernel? It is written to a file called ".config" insinde the kernel source.
Have you applied any kind of patch to the code before compiling? If so, what?
Click to expand...
Click to collapse
Thank you for your time. Your answers to the above questions will be highly appreciated and will be of utmost importance. There is also a good chance that we might build a proper kernel with your reports!
:good: :victory:
Sent from my GT-I8730 using Tapatalk
aureljared said:
URGENT
Before proceeding to build any more ROMs, let me ask some questions.
What toolchain for building the kernel are you using? Toolchains that might work are arm-eabi-4.4.3 upwards or linaro 4.4.3 upwards.
What is your configuration for the kernel? It is written to a file called ".config" insinde the kernel source.
Have you applied any kind of patch to the code before compiling? If so, what?
Thank you for your time. Your answers to the above questions will be highly appreciated and will be of utmost importance. There is also a good chance that we might build a proper kernel with your reports!
:good: :victory:
Sent from my GT-I8730 using Tapatalk
Click to expand...
Click to collapse
No toolchain experience at all. Just substituted kernels from elsewhere. Maybe if you are leaning toward Linaro, I should find myself a tutorial for arm-eabi-4.4.3 upwards and give that a go. then we can cover more ground.
Bazzan
bazzan said:
No toolchain experience at all. Just substituted kernels from elsewhere. Maybe if you are leaning toward Linaro, I should find myself a tutorial for arm-eabi-4.4.3 upwards and give that a go. then we can cover more ground.
Bazzan
Click to expand...
Click to collapse
Sure.
I'm not saying that I'm relying on Linaro now, it's just that Linaro is a toolchain developed by a consortium of technology companies including Samsung that aims to build Linux kernels that perform extremely well on mobile devices.
CM 10.2 uses Linaro 12.09, I think.
I tried building with Linaro a couple of days ago but make threw me some errors, the most confusing being something like this
Code:
make [cypress_touchkeys.o] *** Error 2
I don't even know what Cypress is.
Sent from my GT-I8730 using Tapatalk
aureljared said:
Sure.
I'm not saying that I'm relying on Linaro now, it's just that Linaro is a toolchain developed by a consortium of technology companies including Samsung that aims to build Linux kernels that perform extremely well on mobile devices.
CM 10.2 uses Linaro 12.09, I think.
I tried building with Linaro a couple of days ago but make threw me some errors, the most confusing being something like this
Code:
make [cypress_touchkeys.o] *** Error 2
I don't even know what Cypress is.
Sent from my GT-I8730 using Tapatalk
Click to expand...
Click to collapse
Cannot help with Cypress. Some time ago I downloaded a file called GT-I8730_JB_Opensource.zip - not sure where I found it.
It appears to be what is says it is. Within it is a text file called README_Kernel.txt
It has the following
################################################################################
1. How to Build
- get Toolchain
From android git server , codesourcery and etc ..
- arm-eabi-4.4.3
- edit Makefile
edit "CROSS_COMPILE" to right toolchain path(You downloaded).
EX) export CROSS_COMPILE= $(android platform directory you download)/android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
Ex) export CROSS_COMPILE=/usr/local/toolchain/arm-eabi-4.4.3/bin/arm-eabi- // check the location of toolchain
$ export ARCH=arm
$ make msm8930_express_defconfig
$ make
2. Output files
- Kernel : arch/arm/boot/zImage
- module : drivers/*/*.ko
3. How to Clean
$ make clean
################################################################################
Way out of my depth but will try sometime next week to give it a go with arm-eabi-4.4.3. Major interview Monday so nothing before then.
Bazzan
bazzan said:
Cannot help with Cypress. Some time ago I downloaded a file called GT-I8730_JB_Opensource.zip - not sure where I found it.
It appears to be what is says it is. Within it is a text file called README_Kernel.txt
It has the following
################################################################################
1. How to Build
- get Toolchain
From android git server , codesourcery and etc ..
- arm-eabi-4.4.3
- edit Makefile
edit "CROSS_COMPILE" to right toolchain path(You downloaded).
EX) export CROSS_COMPILE= $(android platform directory you download)/android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
Ex) export CROSS_COMPILE=/usr/local/toolchain/arm-eabi-4.4.3/bin/arm-eabi- // check the location of toolchain
$ export ARCH=arm
$ make msm8930_express_defconfig
$ make
2. Output files
- Kernel : arch/arm/boot/zImage
- module : drivers/*/*.ko
3. How to Clean
$ make clean
################################################################################
Way out of my depth but will try sometime next week to give it a go with arm-eabi-4.4.3. Major interview Monday so nothing before then.
Bazzan
Click to expand...
Click to collapse
That's from Samsung. It contains the kernel source as you already have seen
It's stock 3.4.0 so I don't know if it will work with CM :good:
Sent from my GT-I8730 using Tapatalk
Quote from jt1134:
jt1134 said:
I use the d2 family kernel source.
For stock ROMs and CM10, you can use the source and ramdisk provided by samsung.
For CM10.1 or higher, you'll have to get your hands very dirty. IMO the easiest route would be to port the missing drivers from stock samsung source to the msm8930-common kernel, and modifying it to work with them. This is how I did it for the I437 : http://review.cyanogenmod.org/#/c/47947/ . You may then use the serrano device trees as a template once the kernel is ready.
Click to expand...
Click to collapse
Updated first post with this info.
Sent from my GT-I8730 using Tapatalk
What is this Tutorial?
This tutorial will help you learn about building a custom ROM from source on Google Cloud.
Who this tutorial is for?
This tutorial is for those who want to build a custom ROM from source, but are unable to do that because of following reasons:
1. Low network speed
2. Limited bandwidth
3. Irregular power supply which obstructs the repo sync (yes, this is a reason in some countries )
What is needed for you to start with this thread?
1. A google account
2. A credit card – This is a must to start using Google Cloud Update: I read that people have successfully used debit cards as well.; so try your luck
With you card you can activate free trial and use Google Cloud without any charges for 12 months. Your card will be charged for $1 for verification purpose (and that’s it, the charges on my credit card got reversed in a day- I’m not sure about the reversal of the charges on debit card charges will be reversed on the cards [But I'm not responsible if they don't revert it ]).
3. A PC with good (average will also do, I used 512 kbps connection) internet connection (to access Google Cloud, your bandwidth will not be used much).
4. Common sense (you should have it as you are reading this thread)
5. Willingness to read, search and ask right questions in right forums, communities
So, let’s start our journey!
Part – I
Activating Google Cloud FREE Trial
1. Go to Google Cloud website: https://cloud.google.com/ and click on Free Trial button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Login with your Google account username and password.
3. Click on SIGN UP FOR FREE TRIAL
Enter all the details and click on Accept and start free trial button
4. It will start your free trial and create first project for you
Congratulations! You have completed the most important Part – I of the process and you are now ready to setup the environment for building your ROM!
Update: Now the free trial validity is 1 year so more time to learn how to build the ROM
Part – II
Creating Virtual machine on Google Compute Engine
1. Click on the 2 lines menu displayed on the left top corner to bring on the Products and Services list on left side.
2. In this menu, click on Compute Engine
3. It’ll show following page, click on Create Instance button
4. On Create Instance page, specify the details like Name, Zone (if you want to change them). In Machine Type combo, select a machine configuration that you would like to have.
I use 4 cores and 15 GB memory
5. In Boot disk section, click on Change button.
6. On Boot disk details page, select the OS that you want to have on VM Instance. I always used Ubuntu 14.04 LTS (and it never let me down). Update: Now I use 16.04 LTS
Enter the size of disk. I used 500 GB so that I can sync 2-3 ROMs in the same VM Instance Then click on Select button.
Note: With this configuration I was able to clean build a ROM in around 70 minutes. The repo sync took around 25-30 minutes (which would have taken a week on my slow internet connection)
7. It’ll take you back to Create Instance page. Here you can specify the Firewall by checking both the check boxes. Finally click on Create button to create the VM Instance.
8. It’ll take a minute or two and create the VM instance. It’ll be in running state as indicated by the Green check box in front of the VM Name.
Note: You can start or stop the instance by selecting it and then clicking on stop or start button. It is advised to stop the VM instance once you are done with using it.
9. Click on the 3 dots menu near SSH and select option Open in browser window.
10. It’ll start the SSH connection to the VM Instance that you have created.
11. Run following command to get su
Code:
sudo –s
Now you are ready to install the required packages to build the ROM from source. You can follow this nice guide created by @jackeagle to start:
http://forum.xda-developers.com/showpost.php?p=54118614&postcount=2
That was it!
Wish you all the best for building your first ROM
How to upload the ROM zip on internet?
Many guys, who were able to build the ROM successfully, were asking about how to get the ROM zip on phone
Thanks @hackslash for this nice post: http://forum.xda-developers.com/showpost.php?p=68750149&postcount=146
Upload to AFH: https://forum.xda-developers.com/showpost.php?p=73420609&postcount=315
You can also upload it on Google drive by following these steps:
http://olivermarshall.net/how-to-upload-a-file-to-google-drive-from-the-command-line/ (thanks @Papdya for sharing this link)
Nitin
Awesome guide. I'm sure it'll help out those who are trying hard to build their first ROM and get involved in building stuff. Just a suggestion though
I find @akhilnarang script to be easy to setup server and it's just few commands away. It'd be nice if you include that
Link : github.com/akhilnarang/scripts
-ThugLife™✌
Shreesha.Murthy said:
Awesome guide. I'm sure it'll help out those who are trying hard to build their first ROM and get involved in building stuff. Just a suggestion though
I find @akhilnarang script to be easy to setup server and it's just few commands away. It'd be nice if you include that
Link : github.com/akhilnarang/scripts
-ThugLife™
Click to expand...
Click to collapse
Sure buddy! I'll have a look an include them.
I suffered a lot to build my first ROM (you know that)... So thought to share this easy and fast way to build the ROM. I observed that initially we have to build many times due to errors (coming from lack of knowledge about building). This will reduce the time that is required for "build - error - fix- rebuild" cycle and learn ROM building quickly :fingers-crossed:
Nice
You can add guide to add a disk, format and mount that too
That was my main stuggle when I was trying to use it first
Good for our reading. Thanks
akhilnarang said:
Nice
You can add guide to add a disk, format and mount that too
That was my main stuggle when I was trying to use it first
Click to expand...
Click to collapse
I'll have to understand it from you first
Sent from my Nexus 4 using XDA Free mobile app
To make sure i understand, technically I could build roms on a chromebook with this guide? And the guide listed at the end, do we download all those things on our computer or on the cloud platform? Thanks!
allanlgz said:
To make sure i understand, technically I could build roms on a chromebook with this guide? And the guide listed at the end, do we download all those things on our computer or on the cloud platform? Thanks!
Click to expand...
Click to collapse
Cloud platform m8 :wink:
-ThugLife™✌
allanlgz said:
To make sure i understand, technically I could build roms on a chromebook with this guide? And the guide listed at the end, do we download all those things on our computer or on the cloud platform? Thanks!
Click to expand...
Click to collapse
As @Shreesha.Murthy says, you do everything on Google cloud. That's the whole point of writing this thread
Sent from my Nexus 4 using XDA Free mobile app
Shreesha.Murthy said:
Cloud platform m8 :wink:
-ThugLife™✌
Click to expand...
Click to collapse
Thanks m8. I've never built before but feel comfortable with all the commands and everything. Just one last question, if I want to build for the Sprint LG G3 ls990, I'd have to use the device tree and everything device specific from CM for ls990 (or any other that has all device specific things) to get it to work on my ls990, correct?
Also, thanks so much for the guide it looks really helpful
allanlgz said:
Thanks m8. I've never built before but feel comfortable with all the commands and everything. Just one last question, if I want to build for the Sprint LG G3 ls990, I'd have to use the device tree and everything device specific from CM for ls990 (or any other that has all device specific things) to get it to work on my ls990, correct?
Also, thanks so much for the guide it looks really helpful
Click to expand...
Click to collapse
Yes, you can use the device trees from CM. Do it... :fingers-crossed:
Trying to build
I use the guide link posted at the end however when trying to run the commands I get these errors:
sudo apt-get install git-core gnupg ccache lzop flex bison gperf build-essential zip curl zli
b1g-dev zlib1g-dev:i386 libc6-dev lib32ncurses5 lib32z1 lib32bz2-1.0 lib32ncurses5-dev x11proto-core-dev libx11-
dev:i386 libreadline6-dev:i386 lib32z-dev libgl1-mesa-glx:i386 libgl1-mesa-dev g++-multilib mingw32 tofrodos pyt
hon-markdown libxml2-utils xsltproc readline-common libreadline6-dev libreadline6 lib32readline-gplv2-dev libncu
rses5-dev lib32readline5 lib32readline6 libreadline-dev libreadline6-dev:i386 libreadline6:i386 bzip2 libbz2-dev
libbz2-1.0 libghc-bzlib-dev lib32bz2-dev libsdl1.2-dev libesd0-dev squashfs-tools pngcrush schedtool libwxgtk2.
8-dev python
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'lib32z1-dev' instead of 'lib32z-dev'
E: Unable to locate package zlib1g-dev
E: Unable to locate package libx11-dev
E: Unable to locate package libreadline6-dev
E: Unable to locate package libgl1-mesa-glx
E: Unable to locate package libreadline6-dev
E: Unable to locate package libreadline6
[email protected]:~# sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
ln: failed to create symbolic link ‘/usr/lib/i386-linux-gnu/libGL.so’: No such file or directory
Have followed instructions perfectly so far
allanlgz said:
Trying to build
I use the guide link posted at the end however when trying to run the commands I get these errors:
sudo apt-get install git-core gnupg ccache lzop flex bison gperf build-essential zip curl zli
b1g-dev zlib1g-dev:i386 libc6-dev lib32ncurses5 lib32z1 lib32bz2-1.0 lib32ncurses5-dev x11proto-core-dev libx11-
dev:i386 libreadline6-dev:i386 lib32z-dev libgl1-mesa-glx:i386 libgl1-mesa-dev g++-multilib mingw32 tofrodos pyt
hon-markdown libxml2-utils xsltproc readline-common libreadline6-dev libreadline6 lib32readline-gplv2-dev libncu
rses5-dev lib32readline5 lib32readline6 libreadline-dev libreadline6-dev:i386 libreadline6:i386 bzip2 libbz2-dev
libbz2-1.0 libghc-bzlib-dev lib32bz2-dev libsdl1.2-dev libesd0-dev squashfs-tools pngcrush schedtool libwxgtk2.
8-dev python
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'lib32z1-dev' instead of 'lib32z-dev'
E: Unable to locate package zlib1g-dev
E: Unable to locate package libx11-dev
E: Unable to locate package libreadline6-dev
E: Unable to locate package libgl1-mesa-glx
E: Unable to locate package libreadline6-dev
E: Unable to locate package libreadline6
[email protected]:~# sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
ln: failed to create symbolic link ‘/usr/lib/i386-linux-gnu/libGL.so’: No such file or directory
Have followed instructions perfectly so far
Click to expand...
Click to collapse
Well, those guides are pretty outdated for now. Scroll up or see the 3rd post where I've mentioned about the script. It's automatic and saves you from headache
-ThugLife™✌
Shreesha.Murthy said:
Well, those guides are pretty outdated for now. Scroll up or see the 3rd post where I've mentioned about the script. It's automatic and saves you from headache
-ThugLife™✌
Click to expand...
Click to collapse
alright m8 thanks so much! that sets up the whole build environment right? after running script i can just start builds?
allanlgz said:
alright m8 thanks so much! that sets up the whole build environment right? after running script i can just start builds?
Click to expand...
Click to collapse
Yeah, you just need to sync the ROM source you're trying to build+ device trees and make it compatible for the ROM and you're good to go
-ThugLife™✌
allanlgz said:
Trying to build
I use the guide link posted at the end however when trying to run the commands I get these errors:
sudo apt-get install git-core gnupg ccache lzop flex bison gperf build-essential zip curl zli
b1g-dev zlib1g-dev:i386 libc6-dev lib32ncurses5 lib32z1 lib32bz2-1.0 lib32ncurses5-dev x11proto-core-dev libx11-
dev:i386 libreadline6-dev:i386 lib32z-dev libgl1-mesa-glx:i386 libgl1-mesa-dev g++-multilib mingw32 tofrodos pyt
hon-markdown libxml2-utils xsltproc readline-common libreadline6-dev libreadline6 lib32readline-gplv2-dev libncu
rses5-dev lib32readline5 lib32readline6 libreadline-dev libreadline6-dev:i386 libreadline6:i386 bzip2 libbz2-dev
libbz2-1.0 libghc-bzlib-dev lib32bz2-dev libsdl1.2-dev libesd0-dev squashfs-tools pngcrush schedtool libwxgtk2.
8-dev python
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'lib32z1-dev' instead of 'lib32z-dev'
E: Unable to locate package zlib1g-dev
E: Unable to locate package libx11-dev
E: Unable to locate package libreadline6-dev
E: Unable to locate package libgl1-mesa-glx
E: Unable to locate package libreadline6-dev
E: Unable to locate package libreadline6
[email protected]:~# sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
ln: failed to create symbolic link ‘/usr/lib/i386-linux-gnu/libGL.so’: No such file or directory
Have followed instructions perfectly so far
Click to expand...
Click to collapse
This has been answered in that thread. If you see closely, you'll find out that the packages that are showing error have :i386 in their name. Remove :i386 from their names and you should be good to go.
Or use the scripts that @Shreesha.Murthy has linked
Nitin
thanks for guiding.....:good::good::good:
now i am try to make a rom for my device
@nitin.chobhe - Nice work!
What should be noted that in european countries it seems to only work for people who have a buisiness, at least as per Tos u can't choose and/or use as private person, but most of us have decent internet and power supply and a good enough pc.
Just a note for those who may wonder.