Search results

Gcc 5 is not supported in android and never will be.

The funny thing about all of this is I really can not reproduce the error. I do this in my spare time as a hobby. But now people want me to jump or say how high when they threaten to stop using sabermod. You know what, go ahead **** it I'm out.

I actually don't have that error. And I don't have cloog or isl libs installed from before either. Sent from my LG-H811 using Tapatalk

I suppose, but I'm not sure if that's the best way to fix it.

There's nowhere in the README that says to install cloog... That was removed months ago. https://gitlab.com/SaberMod/sabermod-manifest/commit/1b054df0062b81c586693a6f1c4bf0ddcab36ae9

PATH is not toolchain related. That's something else in your build environment.

No clue man. It's something else in your build environment, has nothing to do with the toolchain...

Are you using one from sabermod.com or one you compiled yourself? If you compile it yourself you'll need to rename the toolchain directory from arm-linux-gnueabi-4.9 to arm-eabi-4.9

Seems like a issue with your device (m9) but not really sure...

You'll need to compile it from source yourself or find one that someone else compiled. That's what this thread is for. Everyone else uses it fine. If your trolling, then seriously get off the thread and don't come back... You trolled Google Plus, we don't need it here too man.

haha ?

no

I highly doubt that. So you'd rather use a sabermod kang? Cause that's what UBERTC is.

Didn't I explain kernel building to you on G+ already? https://plus.google.com/+ShoaibAnwar05/posts/bznyGhtCyup If we don't have the device there's about a 1% chance we can actually do anything to help. It's up to you and the rest of the kernel developers to fix kernel coding issues with...

I'm not sure since I disable clang differently by using vendor/sm... Some people have used those commits before but I've personally never tried them. https://gitlab.com/SaberMod/android-vendor-sabermod/commits/master Sent from my LG-H811 using Tapatalk

Try one of these. I think disabling clang might fix it... https://github.com/SaberMod/SaberMod_art/commits/lollipop

read the op

Nope, don't have a Mac.

Just so everyone knows, I no longer have arm device. I have a G4 now (arm64). All the arm toolchains will now be compiled with the following defaults. -mtune=cortex-a15 and -mfpu=neon-vfpv4 They are located here, and will be updated weekly...

Maybe it goes unanswered because of lack of information. What Linux do you run? Sent from my LG-H811 using Tapatalk

Your error is not a toolchain error, or related to sabermod in any way...

It's a known issue with CM ROMs. I don't normally build CM ROMs so I've never had the issue. It's been discussed already in this thread...

Try this... http://forum.xda-developers.com/showthread.php?t=2770606

The toolchains are on http://sabermod.com What I do is remove all prebuilts gcc then copy them in manually.

On mobile...

Link is dead...

Hi. The Google base build uses a modified Google/aosp gcc branch which maybe or may not contain bugs. In addition it has backports and other patches from sabermod as well. Even stock gnu gcc can contain bugs, in which case the sabermod team really has limited options, unless we find temporary...

Thread closed for now. Will reopen if need be later on, and download links for Lollipop will remain!

PA announced its ending, but there are a few devs trying to keep it going. We just can't count on them to do it or know when it will happen.

With sabermod?

I took a look at the logs. Yes the defconfig is not for arm64. And also kernel logs are incomplete with no errors.

It's fixed in the source if you compile the toolchain yourself. I said this before in my thread. Or you can wait for the next monthly update. If you want support for sabermod, I'd suggest moving this discussion to the sabermod thread. This thread is for switching toolchains, not compiling...

Conflicts aren't the end of the world if you know how to fix them.

Those are linker errors. Might be related to some other warnings or errors further up on your screen. Might have to record a full kernel log. I assume your compiling inline since you didn't say. You can record a log with "make -j bootimage > kernel.log 2>&1" Obviously use -j and the number...

How much of this thread have you read? I've said it before, but I also added it to the OP :rolleyes:

If you build from source no libraries should be needed from now on.

These cortex and neon options are now available for people that compile their own sabermod toolchains. arm and arm64 https://plus.google.com/+PaulBeeler/posts/YUYaafAJsSf

No I'm not. I have a LG G4 now, so I'm waiting for the source for the new nexus to come out since it has similar hardware as the G4. G4 development isn't that good now, but I'm hoping that will change in marshmallow. I still have my nexus 5, but it just sits around for an occasional flash lol.

Nope. Just add this in config/common.mk somewhere. SM_VENDOR := vendor/sm include $(SM_VENDOR)/Main.mk You must set SM_VENDOR because sabermod vendor uses that so you can customize the sync location like vendor/sabermod or whatever you want.

You'll also need to add it in device/sm_devices.mk and products/sm_products.mk like the other devices are. I think that's it. You have the build repo and rom vendor patches already? Sent from my LG-H811 using Tapatalk

You never said what device..

We will see after Android M..

Monthly updated for all toolchains on http://sabermod.com arm-eabi-4.8, arm-eabi-4.9, arm-eabi-5.1, arm-eabi-5.2, arm-eabi-6.0. arm-linux-androideabi-4.8, arm-linux-androideabi-4.9, arm-linux-androideabi-5.1, arm-linux-androideabi-5.2, arm-linux-androideabi-6.0. aarch64-linux-android-4.9...

You can't change the rom toolchain version with .basrc by simply adding it to $PATH. Please read the original post.

I don't have the error, compiles fine for me on both Ubuntu and fedora... Please don't bring uber into this thread.

Your not supposed to install prebuilts.

And that's much more useful then providing a logcat? :rolleyes: Sent from my LG-H811 using Tapatalk

git is all the same. gitlab has all the functionality github has and some more. Well the links are right in the OP :rolleyes:

Your not using official sabermod toolchains. Your using one from a third party... That's why you have the glibc problem. It has nothing to do with sabermod being easy to use or not lol.

For people compiling the toolchains from source. I did a rebase of binutils 2.25 https://plus.google.com/+PaulBeeler/posts/fVeUje3Cc5o Includes more aarch64, Darwin and other patches for ld/gold https://gitlab.com/SaberMod/BinUtils/commits/2.25 The old version is on...