NOTE: All new releases from 11th June and onwards are going to be in the second post: http://forum.xda-developers.com/showpost.php?p=53192240&postcount=2[/SIZE]
I used Christopher83's Cortex-A8 Linaro 4.7.4 Toolchain to build Quarx 3.0 Kernel. Even though I don't own this phone but I have buillt custom kernels in the past for my Defy Mini. Please test it and report to me.
How to build:
1. Download Quarx's 3.0 Kernel source here: https://github.com/Quarx2k/jordan-kernel/archive/p-android-omap3-3.0.zip
2. Unzip the file.
3. Now here comes the building part:
Code:
cd jordan-kernel-p-android-omap3-3.0
export CROSS_COMPILE=/home/YOURUSERNAME/PATHOFTOOLCHAINFOLDER/NAMEOFTOOLCHAINFOLDER/bin/arm-gnueabi-
export ARCH=arm
make mapphone_defconfig
make -j9
4. Now you will see zImage in the folder /jordan-kernel-p-android-omap3-3.0/arch/arm/boot
5. You will also see modules but they will be defined as [M] in the output of Terminal when kernel finishes building and you will need to find it various folders to find where the modules are.
Instructions on installing the kernel:
1. Unzip zImage.zip and copy zImage to /system/bootstrap/2nd-boot
2. Unzip Modules.zip and copy it to /system/lib/modules
3. Fix permissions to 644 for modules and zImage.
I have attached a screenshot of the output when compiling.
Christopher83's Linaro Toolchain thread: http://forum.xda-developers.com/showthread.php?t=2098133
Quarx 3.0 Kernel Source: https://github.com/Quarx2k/jordan-kernel/tree/p-android-omap3-3.0
NOTE: Linaro 3.0 Kernels will be built every time I see a new commit in Quarx's Github.
Linaro 4.7.4 and 4.8.3 Versions of Quarx 3.0 Kernel Releases and Changelogs
NOTE: Installation instructions are in the OP. Please read the OP for Manual installation method!
Please read before flashing or installing the kernel!
Flashable update.zip have the name "update" at the front. The zip files with the name "zImage" and "Modules" at the front are for manual installation.
3rd June 2014 Release:
- Built using sources of Quarx 3.0 Kernel committed up to 3rd June on Github.
- Download Linaro 3.0 Kernel and Modules in the attachment of 1st post.
11th June 2014 Release:
- Built using sources of Quarx 3.0 Kernel committed up to 11th June on Github.
- Built using both Linaro 4.7.4 and Linaro 4.8.3 Cortex-A8 toolchain by @Christopher83
- Released a TWRP flashable zip or use manual method to install.
- Changelog for the kernel for this release can be found here: http://forum.xda-developers.com/showpost.php?p=53277156&postcount=370
Flashable TWRP zips can be find here: http://www.androidfilehost.com/?w=files&flid=15539
Please test this kernel @Fight4Music and report to me thanks. May you also try both Linaro 4.7.4 and Linaro 4.8.3 versions of the kernel and upload the screenshot? Thanks
@rootdefyxt320
working (Defy+)
Fight4Music said:
@rootdefyxt320
working
Click to expand...
Click to collapse
For me the Wi-Fi doesn't get activated anymore :/ it says always activating, but never does.
I copied the zimage and set permissions and copied the modules and overwrite all existing ones and corrected permissions there as well. Any ideas?
L
Gesendet von meinem GT-I9505 mit Tapatalk
Set permissions for all modules and zimage to rw-r-r and reboot. That's it
Fight4Music said:
@rootdefyxt320
working (Defy+)
Click to expand...
Click to collapse
Thanks for your feedback. Does it feel much smoother? Well then I will be building Linaro 3.0 nightly kernels then.
Fight4Music said:
Set permissions for all modules and zimage to rw-r-r and reboot. That's it
Click to expand...
Click to collapse
They are rw-r-r.
I'm on the 2014-06-03 nightly
L
Gesendet von meinem GT-I9505 mit Tapatalk
rootdefyxt320 said:
Thanks for your feedback. Does it feel much smoother? Well then I will be building Linaro 3.0 nightly kernels then.
Click to expand...
Click to collapse
In my opinion it feels smoother - could anyone also give feedback? I hope its not only placebo
If you want to build more kernel nightlys - open a new thread, please
Fight4Music said:
In my opinion it feels smoother - could anyone also give feedback? I hope its not only placebo
If you want to build more kernel nightlys - open a new thread, please
Click to expand...
Click to collapse
If you want to test if it is not a placebo, then run Antutu Benchmark to compare
Sorry for my n00b question, what's differente between quarx kernel and this? xD
DragonautMk said:
Sorry for my n00b question, what's differente between quarx kernel and this? xD
Click to expand...
Click to collapse
Quarx builds use 4.6.x GCC while my one uses a 4.7.4 Linaro. Linaro tends to be smoother than GCC.
My builds use https://github.com/JustArchi/linaro/tree/4.8-androideabi
4.8 linaro.
Great Work you guys are doing -- I am Slimbean 4.4.2 which uses 2.6.x kernel ,
can anything be done ( like Flashable ZIP ) , so that i can flash 3.0.x kernel on it and test it .....
Thanks
jassi32 said:
Great Work you guys are doing -- I am Slimbean 4.4.2 which uses 2.6.x kernel ,
can anything be done ( like Flashable ZIP ) , so that i can flash 3.0.x kernel on it and test it .....
Thanks
Click to expand...
Click to collapse
There is a seperate rom whitch support 3.0. Kernel
Usual 2.6.. kernel rom would not boot with 3.0.. kernel
Sent from my MB525 red , froyo 2.2.2 german blurless service.sbf, as stock rom
There is a Linaro 4.8 toolchain optimised for Cortex-A8 by @Christopher83. The zImage seems to be smaller with his toolchain.
Sent from my U20i using XDA Free mobile app
But Quarx said above he uses Linaro 4.8, I don't get this
This Kernel have bugs?
DragonautMk said:
This Kernel have bugs?
Click to expand...
Click to collapse
The same as that being developed by Quarx.
DiegoxG said:
But Quarx said above he uses Linaro 4.8, I don't get this
Click to expand...
Click to collapse
Quarx uses JustArchi's Linaro 4.8 android-eabi toolchain which can compile both ROM's and Kernels while I use Christopher83's Linaro 4.7.4 Cortex-A8 Toolchain which can only compile kernels. I will compile using Christopher83's Linaro 4.8 Cortex-A8 Toolchain soon when I finish up my exams.
New kernel nightly tonight since Quarx has committed new changes on Github in 3.0 kernel
Will be using both Linaro 4.7.4 Cortex-A8 Toolchain and Linaro 4.8.3 Cortex-A8 Toolchain to compile.
Related
For everyone who has knowledge in building kernels
we try to build kernel version 3.6.11 for our device using this source
we need to setup repo on github
can anyone download this source then push it to github so we can all work on it
thanks
Already tried it. The problem are the proprietary LinuStoreIII drivers.
MarcoToo said:
Already tried it. The problem are the proprietary LinuStoreIII drivers.
Click to expand...
Click to collapse
But Maroc-OS did it , Workaround ?
Might have modded the module API or sth. On a 'normal' compilation Linux ver and toolchain have to match
via XDApp
Is this kernel for something like jb or ics???
rather try to compile 2.6.35.14
Mohamed.Anwar said:
For everyone who has knowledge in building kernels
we try to build kernel version 3.6.11 for our device using this source
we need to setup repo on github
can anyone download this source then push it to github so we can all work on it
thanks
Click to expand...
Click to collapse
i downloaded it i am creating now a repo to upload it i think it will be uploaded in like 10-20 mins
GB is specified working with v2.6 kernel. I wonder if you'll succed. compared to v3.2 our kernel structure is a lot different. someone have tried to use v2.7 source code in the past but it didn't boot on GB rom.
You all don't understand
I can't do it my self as I'm a noob
I created this thread to make you build this kernel
I mean I'm 100% sure it's possible
i start uploading the files to my github
https://github.com/cosminx13/sgy_3.6.11_kernel_source
it will take some yime to add all the files because github client crash if there are over 15000 files in a sync
hi guys !
its is really hard ..
a lot of devs exp on world try and no sucess...
btw source of rasperry no is good for start on my opnion !
for port 3.x kernel will need know alls drivers useds on gy and need for backports a lot .... lol
would be more useful to try porting 2.6 kernel more current!
btw I updated in 1.3.3 kernel 2.6.35.14 the source for about 30%
but after that I completely corrupted the source! hehe
sorry my bad english !
finished uploading source to github please pm me your names to add you to the callaborators
Only little fix to patch from 2.6.35.7 to 2.6.35.14 but for 3.x.x its change lot kernel structur so goodluck guys..
Ps. Thanks whiteXP for.. u know..
Hi guys! i share with you this compiler. It's linaro optimized for coxter-a15 architecture
I WILL NOT SUPPORT THIS PROJECT ANYMORE, YOU CAN FIND UPDATED TOOLCHAIN HERE
DOWNLOAD
Linaro GCC 4.8.3 2014.01 cortex-a15
Linaro GCC 4.8.3 2013.12 cortex-a15
Linaro GCC 4.8.3 2013.11 cortex-a15 v2
Configuration:
Code:
Configuration:
- Target -> Linux Kernel 3.4.77
- Built using latest Crosstool-NG Toolchain Builder
- Linaro GCC 4.8.3 2014.01
- Binutils 2.24
- EGLibc 2.18
- DMalloc 5.5.2
- Duma 2.5.15
- Linaro GDB 7.6-2013.05
- LTrace 0.5.3
- STrace 4.6
- GMP 5.1.1
- MPFR 3.1.2
- ISL 0.11.1
- CLOOG 0.18.0
- MPC 01.0.1
- LibElf 0.8.13
- Multilib support
- Hard float
Changelog:
Code:
22-JAN-2014
update to linaro 2014.01
update kernel headers to 3.4.77
7-JAN-2014
update to linaro 2013.12
update Binutils to version 2.24
update Linaro GDB to version 7.6-2013.05
2-JAN-2014
update Binutils to lastest version
fix some mistake
25-DEC-2013
update to linaro gcc 4.8.3 2013.11
update libraries
9-APR-2013
update to linaro toolchain 2013-03
using Hardfloat
sync with ng-crosstool repo
26-FEB-2013
initial version
Credits:
http://crosstool-ng.org/
XDA:DevDB Information
Linaro toolchain optimized for cortex-a15, a Tool/Utility for the HTC One S
Contributors
rmbq
Version Information
Status: Abandoned
Current Stable Version: 2014.01
Stable Release Date: 2014-01-22
Created 2013-12-26
Last Updated 2014-03-24
here is an how to build: http://forum.xda-developers.com/showthread.php?t=2098133
my config file for Linaro GCC 4.8.3 2013-11 is this: https://www.mediafire.com/?fq9ae7k9exwo2ub
Nice! Thanks for the share!
Sent from my HTC One S using Tapatalk 2
What is this?
Sent from my HTC One S
veeny101 said:
What is this?
Sent from my HTC One S
Click to expand...
Click to collapse
Toys for devs
Sent from my HTC One X using xda app-developers app
Zarboz said:
Toys for devs
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Oh ok.
Sent from my HTC One S
symlinks are broken in source
R: [TOOL] Linaro toolchain optimized for cortex-a15
Zarboz said:
symlinks are broken in source
Click to expand...
Click to collapse
Really? May it cause issues in file system?
Sent from my One S using xda app-developers app
yes, I get the same errors when trying to extract the tar.. Broken symlinks and doesnt extract right.
Seems interesting though and would love to use
R: [TOOL] Linaro toolchain optimized for cortex-a15
AKToronto said:
yes, I get the same errors when trying to extract the tar.. Broken symlinks and doesnt extract right.
Seems interesting though and would love to use
Click to expand...
Click to collapse
I'll re-upload asap
Sent from my One S using xda app-developers app
rmbq said:
I'll re-upload asap
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
new version!
rmbq said:
new version!
Click to expand...
Click to collapse
this one is not even possible to open
fixed
rmbq said:
fixed
Click to expand...
Click to collapse
These are the errors I get when extracting the .tar
tar: arm-cortex_a15-linux-gnueabi/arm-cortex_a15-linux-gnueabi/sysroot/usr/lib32: Cannot create symlink to `lib': File exists
tar: arm-cortex_a15-linux-gnueabi/arm-cortex_a15-linux-gnueabi/sysroot/usr/lib64: Cannot create symlink to `lib': File exists
tar: arm-cortex_a15-linux-gnueabi/arm-cortex_a15-linux-gnueabi/sysroot/lib32: Cannot create symlink to `lib': File exists
tar: arm-cortex_a15-linux-gnueabi/arm-cortex_a15-linux-gnueabi/sysroot/lib64: Cannot create symlink to `lib': File exists
tar: arm-cortex_a15-linux-gnueabi/arm-cortex_a15-linux-gnueabi/lib: Cannot create symlink to `sysroot/lib': File exists
tar: arm-cortex_a15-linux-gnueabi/arm-cortex_a15-linux-gnueabi/lib32: Cannot create symlink to `lib': File exists
tar: arm-cortex_a15-linux-gnueabi/arm-cortex_a15-linux-gnueabi/lib64: Cannot create symlink to `lib': File exists
tar: Exiting with failure status due to previous errors
just an fyi
It's OK it isn't a real error
Sent from my One S using xda app-developers app
Thx for this
Sent from my HTC One S using xda premium
new version up!
Edit: maybe the new file is corrupt, I'll check it asap
rmbq said:
new version up!
Edit: maybe the new file is corrupt, I'll check it asap
Click to expand...
Click to collapse
Works now.. Just want to say your work is great and your dedication to the users.. You have helped me soo much thank you.. This compiler is awesome as well
Sent from my One S using xda premium
are you planning to update this with linaro 4.8 optimized for cortex a15?
Thank you !!
Sent from my hTC One S powered ViperS by Team Venom™
hi Guys,
as some of u maybe know from the OPO/OP2/OPX area i'm doing a "build-service" for non official boeffla kernel builds and as we recently also got a boeffla kernel
for the One Plus 3 device (kudos and thx to @Lord Boeffla!) i want to share with u my self made Linaro/Uber builds for that device in addition.
i'm gonna reduce redundancy and keep it shorter this time as about how this started and my primary intention can also be taken from the corresponding Samsung Thread
so without further ado let's go:
First of all the obligatorily Disclaimer:
As also written in the title please note these builds are UNOFFICIAL, are NOT SUPPORTED in any way by Lord Boeffla or myself and might be EVEN UNSTABLE! So take them as they are! As always flash them at your own risk and make a backup before flashing! (yeah take this advice seriously!)
About bugs: Before you report ANY issues with the linaro/uber builds provided here (doesn't matter which one!) FIRST TRY the non-linaro/uber official builds from HERE (offline, project EOL)to see if they will be gone then. if they wont, you can go on and report your problems in the official boeffla kernel threads! I hope you understand that we have to treat and keep these builds here completely separate from official ones as they have in no terms something to do with each other! Not respecting this will force me to stop building further linaro/uber builds of boeffla kernel.
About benchmarks and comparisons between toolchains:
It's common known that linaro (maybe also uber?) builds might give us higher benchmark rates and that seems great for some people (in fact it's pointless per se in my opinion)
so please if you really must, post them ONLY here and NOT in official boeffla kernel thread, thanks!
Now some more precise informations about what's going on here:
what i did:
the images are always build with original sources from official boeffla kernel OP3 repositories with some not worth to mention minor changes
to be able to build it on my build environment with non stock toolchains.
all images are compiled from special branches from a forked Boeffla Kernel repository
with recent versions of Uber/Linaro Toolchains (Credits to Team Uber and Thx and Credits to @DespairFactor for the pre-configured/-build toolchains)
Sources:
all images are build with changes from different branches in following repositories:
https://github.com/zanezam/boeffla-kernel-cm-oneplus3
https://github.com/zanezam/boeffla-kernel-oos-oneplus3
Beside of some additional fixes from my side all changes are taken from repositories of @ak
so all credits to him, and thx again for the starting point!
what i will do:
build the source code with linaro/uber toolchain and (like Lord Boeffla usually does) provide a recovery image of recent boeffla kernel versions.
do a test for about 1 day with this builds and if they work without any big issues, add them on the corresponding download locations.
i will try to keep the linaro/uber toolchains as up-to-date as possible till the need of bigger code change will be reached.
not providing versions that are not released by Lord Boeffla yet.
not providing an image if it is not working - well of course not *g* but it will be marked as "canceled" then for info.
not change the source code to add/remove features or fix boeffla kernel related bugs.
not support the whole stuff here.
what i will maybe do (sooner or later):
provide ZZMoove Governor test builds if there are any new versions to test - more infos and discussions about ZZMoove Governor can be found HERE
provide builds for special operations (no plans, they will just pop-up)
maybe tune the build flags if some more linaro/uber experienced dev comes up with "better" ones (feel free to post and let me know, toolchain specialists! *g*)
Downloads:
One Plus 3 Oxygen OS v3.x.x (+Nethunter special build)
(*l541* *l621* linaro / *u541* *u631* uber)
One Plus 3 Oxygen OS v4.x.x (+Nethunter special build)
(*l541* *l621* linaro / *u541* *u631* uber)
One Plus 3 Oxygen OS v5.x.x (+Nethunter special build)
(*l541* *l621* linaro / *u541* *u631* uber)
One Plus 3 CM13.0 (+Nethunter special build)
(*l541* *l621* linaro / *u541* *u631* uber)
One Plus 3 CM14.1 / LineageOS 14.1 (+Nethunter special build)
(*l541* *l621* linaro / *u541* *u631* uber)
OnePlus3T:
One Plus 3T Oxygen OS v3.x.x (+Nethunter special build)
(*l541* *l621* linaro / *u541* *u631* uber)
One Plus 3T Oxygen OS v4.x.x (+Nethunter special build)
(*l541* *l621* linaro / *u541* *u631* uber)
One Plus 3T Oxygen OS v5.x.x (+Nethunter special build)
(*l541* *l621* linaro / *u541* *u631* uber)
One Plus 3T CM14.1 / LineageOS 14.1 (+Nethunter special build)
(*l541* *l621* linaro / *u541* *u631* uber)
Mirror on Androidfilehost for all devices (only latest kernel versions)
Nethunter Install Packs:
For One Plus 3(T) Marshmallow/Nugat Roms
Why do we need 4 threads of this?
itsLewin said:
Why do we need 4 threads of this?
Click to expand...
Click to collapse
to keep things separated?
EDIT: lol sry i thought u were referring to the other device threads!
no of course that was a technical issue when creating the thread. i didn't notice that it happened
anyway other threads r deleted now and this one is the only one thx for the heads up. u guys r crazy fast! *g*
ok but now lets start with this:
Following builds are up Guys!
Boeffla-kernel-1.0-beta1-OOS3xx-OnePlus3
Boeffla-kernel-1.0-beta1-CM13.0-OnePlus3
...uploaded
enjoy!
ZZ
Just want to ask which version to download and flash as there are 2 versions linaro and uber builds?
as u like. u can flash over both versions and the official ones so u can switch as u like. I can't really say which one better works for u I'm also still testing and not yet settled.
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
...and I've prayed God for @Lord Boeffla kernel with @ZaneZam flavour!! And finally is hereeeee!! Thank you guysss!!
Zzmoove 4tw!!!
Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
Thanks for your support for OP3. Would definitely give it a try.
I was thinking since lord is here where is ZZ..!! Here he is..!!
Welcome to the party lord and ZZ..!! I am glad that the top most and epic devs of oneplus one are here..!! The device is going to get even better now..!!
So there are 4 files of same build in cm13 folder. Which one i should flash? The difference is only in build time mark. I downloaded the latest though.
Edit: just realized that there are also differences in uber and linaro versions
nazerro said:
So there are 4 files of same build in cm13 folder. Which one i should flash? The difference is only in build time mark. I downloaded the latest though.
Edit: just realized that there are also differences in uber and linaro versions
Click to expand...
Click to collapse
He Personally loves the uber 541 builds.. I have always used linaro 541 builds try and see how they behave.. Linaro is very calm..
geekynoob said:
He Personally loves the uber 541 builds.. I have always used linaro 541 builds try and see how they behave.. Linaro is very calm..
Click to expand...
Click to collapse
Thanks man.. So between ubertc and linaro, which one is more battery friendly?
nazerro said:
Thanks man.. So between ubertc and linaro, which one is more battery friendly?
Click to expand...
Click to collapse
Battery is subjective.. Uber is a happy go lucky peppy fellow while linaro us a calm person.. I've used linaro builds always on my oneplus one.. U can try them.. :&
Uber is amazing. Never tried Linaro before though. Decisions decisions..
Sent from my iPod touch using Tapatalk
nazerro said:
So there are 4 files of same build in cm13 folder. Which one i should flash? The difference is only in build time mark. I downloaded the latest though.
Edit: just realized that there are also differences in uber and linaro versions
Click to expand...
Click to collapse
yes there are 4 builds which are the same kernel version. the difference is only the used toolchain as stated in op for example u541 = uber gcc 5.4.1, l611 = linaro gcc 6.1.1 and so on.
build time might differ yes but doesn't matter base is always the same source. things are too fresh for a advice which one u should flash, try and see. i do the same
geekynoob said:
He Personally loves the uber 541 builds.. I have always used linaro 541 builds try and see how they behave.. Linaro is very calm..
Click to expand...
Click to collapse
true for my other devices on the OP3 i more tend to the 6.1.1 builds atm.
nazerro said:
Thanks man.. So between ubertc and linaro, which one is more battery friendly?
Click to expand...
Click to collapse
geekynoob said:
Battery is subjective.. Uber is a happy go lucky peppy fellow while linaro us a calm person.. I've used linaro builds always on my oneplus one.. U can try them.. :&
Click to expand...
Click to collapse
yes i would agree and honestly i dont think we can archive big differences with a kernel in terms of battery biggest potential is still in in the system "userland".
using these uber/linaro versions is in my opinion just a "fine tune" in terms of speed and fluitness.
cerealguy said:
...and I've prayed God for @Lord Boeffla kernel with @ZaneZam flavour!! And finally is hereeeee!! Thank you guysss!!
Zzmoove 4tw!!!
Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
Click to expand...
Click to collapse
oh a zzmoove fellow! hehe u're welcome, have fun!
MisterCoolBeans said:
Uber is amazing. Never tried Linaro before though. Decisions decisions..
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
i know what u mean and especially on the very fast OP3 it's hard to feel the difference in addition. but well i do the roundabout all the time
at some point i hope i find mine too but as said im not settled too, but hey the credo is never settle!
@ZaneZam Thank you for share your work with us man i want to ask if you will build with Uber 7.0? like you did for the OnePlus One.
Jole7 said:
@ZaneZam Thank you for share your work with us man i want to ask if you will build with Uber 7.0? like you did for the OnePlus One.
Click to expand...
Click to collapse
i would love to but it's not possible yet i got ICE (internal compiler errors) with all 7.0 toolchains i tried. spented 2h+ with trying to fix that but as u can see no build available that means i wasn't successful
(yet! i will continue to try with newer TC versions of course)
Ok Thanks man kernel is great good luck with these builds.
Does any one have the nrsm wakelock on linaro build kernel V l644.
I'll start testing *u611* uber on OOS. Let's see how it goes!
Hello Zanezam,
nice to see you also here. Seems taht I MUST now change from Galaxy S3 to Oneplus 3 .
By the way: I just found a reference of your kernel at OTA Update Center App but unfortunately there is no file located.
Was this just a try? Can you reactivate this possibility?
I aksed Andi if it would be possible to integrate the update function for your kernel also in the official boeffla app but as it is unofficial and aligned with you he will not do it.
I am just searching for a little bit more comfortable way of keeping the kernel up to date.
Hm maybe this is the rigth time to start developing my own app ?!? I will have to think about this tonight
Greetings
Renegade1504
Introduction
Hello everyone, these are some arm and arm64 toolchains I have compiled using a script created by @USBhost and modified by @frap129 and me. I know the concept of toolchains is not a new one, as there have been many specialized/optimized variants. However, some people may want a pure/unaltered toolchain for certain projects. That's what this will be, a generic/simple toolchain configuration. These will be done on a semi-nightly basis. They have been tested on up to date Arch Linux and Ubuntu 17.04 systems. If you know how to use scripts or cross compile, feel free to skip straight to the downloads!
Configuration
The GNU (standard or unlabeled) toolchains are built from GNU's latest gcc-7-branch. The Linaro toolchains are compiled from the linaro-local/gcc-7-integration-branch branch.
These are the additional components:
Code:
binutils 2.29.1
gmp 6.1.2
mpfr 3.1.5
mpc 1.0.3
isl 0.18
bionic r15c
Latest Linux Kernel headers (7318413077a5141a50a753b1fab687b7907eef16)
These toolchains are statically linked so they should work on any 64-bit Linux system; let me know if there are any issues with this.
Build script
These were compiled with crosstool-NG, which is extremely versatile but a little complex for the average user. Instead, I offer a build script in this repo to compile very similar toolchains (they will not be statically linked but that's no issue if you are only compiling on your machine and they won't have bionic). It has been modified heavily from the original repo to support two different architecture configurations (more can easily be added upon request).
To learn more about the script, give the README a glance, as it will be more up to date than the thread.
Using the toolchains
Please see the README.
Issues?
If you run into any issues with either using or compiling these toolchains, please do one of the following:
Open an issue on Github. Use the toolchains repo for issues with using, use the script repo for issues with compiling.
Make a post on here.
In both cases, I will require a detailed explanation of your system configuration, what you are compiling, and a FULL terminal output; without these, your problem will be ignored.
Credits
@USBhost: For the initial script and permission to make this thread
@frap129: For his modifications to the script
@MSF Jarvis: For testing the arm option
@kantjer: For testing the Ubuntu versions on Linux Mint
Reserved
Great stuff
nice, thank you ?
Sent from my LGLS676 using Tapatalk
Dude it took me days to get arm to build because of weird errors and you just added a flag that builds it?
frap129 said:
Dude it took me days to get arm to build because of weird errors and you just added a flag that builds it?
Click to expand...
Click to collapse
Yeah, all I did was target arm-linux-gnueabi and build the arm Linux headers and everything compiled just fine.
So linaro or standard, what's recommended?
And what flags do you suggest to use for ROM and kernel?
Any support for x86/x86_64 platform?
neobuddy89 said:
So linaro or standard, what's recommended?
And what flags do you suggest to use for ROM and kernel?
Click to expand...
Click to collapse
I personally use Linaro given all the work they do for the arm architecture. These are the flag I use for my kernel. I'd love to claim credit for them but @kwoktopus helped me with most of them
zainifame said:
Any support for x86/x86_64 platform?
Click to expand...
Click to collapse
I do not currently plan on it but if there is enough demand I can consider it.
The Flash said:
I personally use Linaro given all the work they do for the arm architecture. These are the flag I use for my kernel. I'd love to claim credit for them but @kwoktopus helped me with most of them
I do not currently plan on it but if there is enough demand I can consider it.
Click to expand...
Click to collapse
Hope u support the x86/x86_64 platform
The Flash said:
I do not currently plan on it but if there is enough demand I can consider it.
Click to expand...
Click to collapse
X86_64 is theoretically already supported.
All you need to do is Target x86_64 and choose what version then done.
Like what was done for arm
USBhost said:
X86_64 is theoretically already supported.
All you need to do is Target x86_64 and choose what version then done.
Click to expand...
Click to collapse
True, I can add an option to the script. I assumed he was referring to the prebuilts
what's recommended? btw great stuff
Dreamstar said:
what's recommended? btw great stuff
Click to expand...
Click to collapse
I don't really recommend anything other than trying both variants and seeing which one you like.
Great stuff on XDA after a long time good work
Hi, can I use it to compile my rom based on LineageOS 14.1? I started to develop my own rom recently and now I wanted to try changing the toolchain.
zibiksior said:
Hi, can I use it to compile my rom based on LineageOS 14.1? I started to develop my own rom recently and now I wanted to try changing the toolchain.
Click to expand...
Click to collapse
Mostly will not be able to compile a ROM with this but give it a try. It for sure can compile the inline kernel.
Just a brief update, the build script still works perfectly fine but I will start compiling the provided toolchains with crosstool-NG as I can make the toolchains statically linked, meaning that they should work with all versions of Linux. It will also be easier for me to manage and tarballs will be smaller. I will try to have this done tomorrow, given Linaro just released their updated snapshot source
The Flash said:
Mostly will not be able to compile a ROM with this but give it a try. It for sure can compile the inline kernel.
Just a brief update, the build script still works perfectly fine but I will start compiling the provided toolchains with crosstool-NG as I can make the toolchains statically linked, meaning that they should work with all versions of Linux. It will also be easier for me to manage and tarballs will be smaller. I will try to have this done tomorrow, given Linaro just released their updated snapshot source
Click to expand...
Click to collapse
Ok, I undertstand can you instead point me some link with prebuild toolchains which I can use to compile my rom? I connot find any... Or meybe some manual how to compile appropriate version of toolchain?
20170520 toolchains are now uploaded!
As I mentioned before, they are compiled with crosstool-NG so that it's easier for me to update. Furthermore, the toolchains are much smaller now so they're easier to download and they're statically linked so they *should* work when any updated form of Linux. Let me know of any issues and enjoy!
Nice stuff indeed, thanks
Btw i've once been told that gnueabi and androideabi are slightly different, would it be okay to compile android kernels with gnueabi?
HardcoreKernel for the Nexus 5X
Features
- Based on latest Google Release (April 2018)
- 3.10.108
- Compiled with Linaro 4.9
- Reduced kernel size
- Disable useless debug
- Wireguard support
Download
http://pc.cd/ru77
Kernel Source
https://github.com/HardcoreKernel/bullhead (8.1.0-hardcore13)
Telegram Channel
https://t.me/hardcorekernelchannel
PS:
Can be used as a clean base for creating custom kernels (8.1.0-linux)
Reserved
scafroglia93 said:
HardcoreKernel for the Nexus 5X
Features
- Based on latest Google Release
- 3.10.108
- Compiled with UberTC 4.9
Download
https://goo.gl/ZuiJos
Kernel Source
https://github.com/HardcoreKernel/bullhead
Telegram Channel
https://t.me/hardcorekernelchannel
PS:
Can be used as a clean base for creating custom kernels (8.0.0-linux)
Click to expand...
Click to collapse
3.10.108 ? awesome ! Thanks
What feature also included in this kernel (except the latest security patches from Google, 3.10.108 and UberTC?)?
AFK269 said:
What feature also included in this kernel (except the latest security patches from Google, 3.10.108 and UberTC?)?
Click to expand...
Click to collapse
No at the moment, my main goal is provide a simply kernel for all with the latest upstream made by Linux according to the latest reports made by Kernel Mantainer (Greg and Willy) about upstream lts kernel.
The other goal is to provide third-party developers with a base for creating their own custom kernel starting from a clean base so if you want add another features you can grab my kernel and edit without any problem with the support of latest Kernel LTS version 3.10.108
Edit
It's a simply google + linux
Thanks for this kernel.
Sent from my Nexus 5X using Tapatalk
scafroglia93 said:
No at the moment, my main goal is provide a simply kernel for all with the latest upstream made by Linux according to the latest reports made by Kernel Mantainer (Greg and Willy) about upstream lts kernel.
The other goal is to provide third-party developers with a base for creating their own custom kernel starting from a clean base so if you want add another features you can grab my kernel and edit without any problem with the support of latest Kernel LTS version 3.10.108
Edit
It's a simply google + linux
Click to expand...
Click to collapse
Adding wakelock control should be appreciated!
November's kernel source is available
AFK269 said:
November's kernel source is available
Click to expand...
Click to collapse
I know...
*Update*
HardcoreKernel-bullhead--20171107-1012
- Merge November Security Patch
what conflicts you had when merging upstream linux to base 3.10.73? did you merge or cherry-pick?
Yaznas said:
what conflicts you had when merging upstream linux to base 3.10.73? did you merge or cherry-pick?
Click to expand...
Click to collapse
All cherry-picked, check my source
scafroglia93 said:
*Update*
HardcoreKernel-bullhead--20171107-1012
- Merge November Security Patch
Click to expand...
Click to collapse
Why you don't do a kernel with some features to save battery and other optimisations and tools instead as just publishing the base as you looks like to be really experimented?
francos21 said:
Why you don't do a kernel with some features to save battery and other optimisations and tools instead as just publishing the base as you looks like to be really experimented?
Click to expand...
Click to collapse
Why complain? if you don't want to use it, move along.
francos21 said:
Why you don't do a kernel with some features to save battery and other optimisations and tools instead as just publishing the base as you looks like to be really experimented?
Click to expand...
Click to collapse
It's the same "base" used by Google plus the upstream to latest Linux kernel version.
If you want some features fork my kernel and work on it, it's simply
k4zkispr0xy said:
Why complain? if you don't want to use it, move along.
Click to expand...
Click to collapse
I'm not complaining man, I'm just asking why he don't compile his with useful features because he think that's simple but not really as to begin I don't have an access to linux during the week as my laptop don't support it.
@scafroglia93, Awesomeness! Nice work. ??
francos21 said:
I'm not complaining man, I'm just asking why he don't compile his with useful features because he think that's simple but not really as to begin I don't have an access to linux during the week as my laptop don't support it.
Click to expand...
Click to collapse
UPSTREAM it's the most useful features which you can find in a kernel
I cloned your source to my PC but for some reason the kernel version is 3.10.73 and not the 3.10.108.
AFK269 said:
I cloned your source to my PC but for some reason the kernel version is 3.10.73 and not the 3.10.108.
Click to expand...
Click to collapse
Well, the default branch is 8.0.0-base (1:1 Google) just git checkout 8.0.0-linux and you're okay