yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] sparksco:
OK you have too many warnings to search though at the moment. I'll see about sending some pull request when I get home for some of these to test.
[Android Software/Hacking General [Developers Only]] Xileforce:
Awesome man. That's going above and beyond. Almost all of those errors showed up with 5.0. You will have to remove all of the graphite flags from my make file including floop nest optimize tho. Assuming u attempt to compile.
[Android Software/Hacking General [Developers Only]] sparksco:
no problem, these kernel warnings can be confusing. I'm actually going to see if I can make both graphite flags and pthreads work. Since it works on the nexus 9 kernel I'm guessing we're missing something to make it work. And most of the time many warnings are only from a few files. I only had to patch 6 files to fix 104 warnings in my hammerhead kernel.
[Android Software/Hacking General [Developers Only]] Xileforce:
Yea I don't understand these linker errors and such. A lot of them I can figure out, but these ones are out of my league :/ pthreads and graphite would be cool
[Android Software/Hacking General [Developers Only]] sparksco:
Well it looks like graphite and pthreads might not be feasable at the moment since it's related to arch/arm and the nexus 9 is arch/arm64 ..

And as far as the linker errors go, if looks like a problem with drivers/cpufreq changes from Franco that I can't fix... So I guess it's not worth pushing the fixes for the other other warnings until the issues for the cpufreq are fixed. Maybe you could have Franco take a look at it for ya, as I don't really understand what he's trying to accomplish in some of the commits. And also I can't revert the commits because of some of the dependencies for the Linux update commits that are not real merges from Linux. Instead they are copy/paste commits which makes it even more difficult to revert commits in cpufreq. In all honesty I'd start on a fresh new kernel and add changes as you go and see what works.
[Android Software/Hacking General [Developers Only]] Xileforce:
OK thanks I may give that a try. I'll keep messing with it.
[Android Software/Hacking General [Developers Only]] sparksco:
Good luck and let us know how it goes [emoji6]
[Android Software/Hacking General [Developers Only]] sparksco:
https://computing.llnl.gov/tutorials/pthreads/
[Android Software/Hacking General [Developers Only]] sparksco:
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.
[Android Software/Hacking General [Developers Only]] JustArchi:
[MENTION=2394329]sparksco[/MENTION], are you currently compiling your ROMs with 5.1/5.2 androideabi? Are there any known issues?
[Android Software/Hacking General [Developers Only]] sparksco:
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.
[Android Software/Hacking General [Developers Only]] slim80:
[MENTION=2394329]sparksco[/MENTION]

I also have the LG G4 now

:)

I developed a custom kernel for Galaxy S4 with your arm-eabi 4.9 toolchians without any problem.

Now i want to dev a new kernel for this device.

I tried with the aarch64-linux-gnu-4.9, but i have some problem with the compilation. Needs different/new library?

I have Ubuntu 14.04 64bit.

Thanks

Inviato dal mio LG-H815 utilizzando Tapatalk
[Android Software/Hacking General [Developers Only]] droidblitz:
Good luck on your future rom/kernel build [MENTION=4543502]slim80[/MENTION].

S4 community will definitely miss you. :D
[Android Software/Hacking General [Developers Only]] sparksco:
If you build from source no libraries should be needed from now on.
[Android Software/Hacking General [Developers Only]] gokart2:
:NEVERMIND:

Found one large problem, gonna start over.
[Android Software/Hacking General [Developers Only]] xperiafan13:
Im compile kernel with SM-5.1, but im compile wlan as module... and this break wifi?? any help??

with linaro 5.1 is fine
[Android Software/Hacking General [Developers Only]] sparksco:
How much of this thread have you read? I've said it before, but I also added it to the OP :rolleyes:
[Android Software/Hacking General [Developers Only]] zowpow:
I'm having a problem building a kernel for ARM64. Both the CM source: https://github.com/TeamRegular/android_kernel_lge_msm8916 and the CAF source branch LA.BR.1.2.6_rb1.1 give me errors like this:

net/bluetooth/hidp/core.o
/tmp/cc5DpVTS.s: Assembler messages:
/tmp/cc5DpVTS.s:21: Error: unknown mnemonic `mcr' -- `mcr p15,0,x0,c9,c12,3'
/tmp/cc5DpVTS.s:32: Error: unknown mnemonic `mcr' -- `mcr p15,0,x0,c9,c12,1'
/tmp/cc5DpVTS.s:56: Error: unknown mnemonic `mcr' -- `mcr p15,0,x0,c9,c12,2'
/tmp/cc5DpVTS.s:80: Error: unknown mnemonic `mcr' -- `mcr p15,0,x0,c9,c14,1'
/tmp/cc5DpVTS.s:104: Error: unknown mnemonic `mcr' -- `mcr p15,0,x0,c9,c14,2'
/tmp/cc5DpVTS.s:128: Error: unknown mnemonic `mcr' -- `mcr p15,0,x0,c9,c13,2'
/tmp/cc5DpVTS.s:160: Error: unknown mnemonic `mcr' -- `mcr p15,0,x0,c9,c12,0'
/tmp/cc5DpVTS.s:172: Error: unknown mnemonic `mcr' -- `mcr p15,0,x0,c9,c12,5'
/tmp/cc5DpVTS.s:184: Error: unknown mnemonic `mcr' -- `mcr p15,0,x0,c9,c13,1'
/tmp/cc5DpVTS.s:195: Error: unknown mnemonic `mcr' -- `mcr p15,0,x1,c9,c13,2'
/tmp/cc5DpVTS.s:296: Error: unknown mnemonic `mcr' -- `mcr p15,0,x0,c9,c14,1'
/tmp/cc5DpVTS.s:309: Error: unknown mnemonic `mcr' -- `mcr p15,0,x0,c9,c12,3'
/tmp/cc5DpVTS.s:320: Error: unknown mnemonic `mcr' -- `mcr p15,0,x0,c9,c12,1'
/tmp/cc5DpVTS.s:359: Error: unknown mnemonic `mcr' -- `mcr p15,0,x2,c9,c12,2'
/tmp/cc5DpVTS.s:370: Error: unknown mnemonic `mrc' -- `mrc p15,0,x2,c9,c13,2'
/tmp/cc5DpVTS.s:946: Error: unknown mnemonic `mcr' -- `mcr p15,0,x0,c9,c12,2'
/tmp/cc5DpVTS.s:957: Error: unknown mnemonic `mrc' -- `mrc p15,0,x0,c9,c13,2'
/tmp/cc5DpVTS.s:975: Error: unknown mnemonic `mrc' -- `mrc p15,0,x1,c9,c13,2'
/tmp/cc5DpVTS.s:986: Error: unknown mnemonic `mrc' -- `mrc p15,0,x2,c9,c12,3'
/tmp/cc5DpVTS.s:1107: Error: unknown mnemonic `mcr' -- `mcr p15,0,x0,c9,c14,1'
/tmp/cc5DpVTS.s:1120: Error: unknown mnemonic `mcr' -- `mcr p15,0,x0,c9,c12,3'
/tmp/cc5DpVTS.s:1131: Error: unknown mnemonic `mcr' -- `mcr p15,0,x0,c9,c12,1'
/tmp/cc5DpVTS.s:1639: Error: unknown mnemonic `mcr' -- `mcr p15,0,x0,c9,c12,2'
/tmp/cc5DpVTS.s:1655: Error: unknown mnemonic `mrc' -- `mrc p15,0,x1,c9,c13,2'
/tmp/cc5DpVTS.s:1666: Error: unknown mnemonic `mrc' -- `mrc p15,0,x3,c9,c12,3'

I have never seen errors like those before, and google isn't really helping, so I'm stumped :( Anyone know how to solve these?
[Android Software/Hacking General [Developers Only]] sparksco:
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 of cores your building with.
[Android Software/Hacking General [Developers Only]] zowpow:
Thanks for responding. I believe the problem is in my defconfig. The errors happen with both inline building and building the kernel directly. The defconfig I used is stolen from the arch/arm/configs directory, but I am building arm64, so I put the defconfig into arch/arm64/configs. I've uploaded logs of the building inline (kernel.log), building directly (kernel2.log), and building using msm_defconfig (kernel3.log), which seems to bypass the error. This is all using the CAF kernel on the branch mentioned previously. I have also uploaded the defconfig used. Here are the files: http://1drv.ms/1MnQ3Bq
[Android Software/Hacking General [Developers Only]] sparksco:
I took a look at the logs. Yes the defconfig is not for arm64. And also kernel logs are incomplete with no errors.
[Android Software/Hacking General [Developers Only]] ritalee:
Hi sparksco, I'm trying to compile cm-12.1 for my device redmi 1s (armani) with sabermod toolchains.

Im on ubuntu 14.04 where I compiled yesterday 4.9 toolchain (both google and gnu, by the way i really would like to know where i can read about differences..)

the command I used was

bash arm-linux-androideabi-4.9 a7 vfpv4
bash arm-eabi-4.9 a7 vfpv4

Then I saberized Build - Kernel - Vendor/cm - Vendor/sabermod

when i try to compile ther kernel ( mka bootimage ) i get these errors:

LD init/mounts.o
arm-eabi-ld: -f may not be used without -shared
LD arch/arm/mm/built-in.o
arm-eabi-ld: -f may not be used without -shared
LD arch/arm/kernel/built-in.o
arm-eabi-ld: -f may not be used without -shared

If I uncommit your last kernel commit that enables ld graphite flags, then it fails at final vmlinux steps with these errors:

undefined reference to `omp_get_num_threads'
undefined reference to `omp_get_thread_num'

I would appreciate if you could give me some advise.

Thank you.
[Android Software/Hacking General [Developers Only]] sparksco:
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 fixes (in some cases we have).

The gnu base gcc is pretty much the same old sabermod gcc (gnu based), with some (not all) of aosp patches, and sabermod patches.

As far as the error I'm not really sure... Some kernels have these errors like the nexus 4 with prima drivers. Can't really tell with the limited log you've provided...
[Android Software/Hacking General [Developers Only]] ritalee:
Ok, thanks for the input.

Here is the complete log file generated by this command

mka bootimage 2>&1 | tee build.log
[Android Software/Hacking General [Developers Only]] tuankiet65:
I got segfault while compiling external/libvpx/libvpx/vp9/encoder/vp9_dct.c:

external/libvpx/libvpx/vp9/encoder/vp9_dct.c: In function 'vp9_fdct16x16_c':
external/libvpx/libvpx/vp9/encoder/vp9_dct.c:314:6: internal compiler error: Segmentation fault
void vp9_fdct16x16_c(const int16_t *input, int16_t *output, int stride) {
^

gcc -v, command line and preprocessed source: https://gist.github.com/tuankiet65/7167ae107a7d69212c8d

Interestingly this occured with -O2 and larger optimization levels, changing optimization level to -O1 fixed the problem.
[Android Software/Hacking General [Developers Only]] sparksco:
Try this...

http://xdaforums.com/showthread.php?t=2770606
[Android Software/Hacking General [Developers Only]] JustArchi:
Confirming that regression.
[Android Software/Hacking General [Developers Only]] gokart2:
Finally got it to compile. Had a couple errors I've figured out so far. But I'm lost with this one. The linux part has me confused......?

fs/f2fs/dir.c:13:27: fatal error: linux/f2fs_fs.h: No such file or directory
#include <linux/f2fs_fs.h>
^
compilation terminated.
make[2]: *** [fs/f2fs/dir.o] Error 1
make[1]: *** [fs/f2fs] Error 2
make: *** [fs] Error 2
make: *** Waiting for unfinished jobs....
[Android Software/Hacking General [Developers Only]] sparksco:
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...
[Android Software/Hacking General [Developers Only]] sparksco:
Your error is not a toolchain error, or related to sabermod in any way...
[Android Software/Hacking General [Developers Only]] gokart2:
Thanks....believe I figured it out. I'm at work so I can't verify just yet. The "linux" part had me thinking it was OS or compiler based at first.
[Android Software/Hacking General [Developers Only]] beeeto:
Same here.

Did you find a workaround?
[Android Software/Hacking General [Developers Only]] JustArchi:
Nope, I felt back to older release.
[Android Software/Hacking General [Developers Only]] PunkUnity:
Environment isn't set up right for SaberMod or you don't have all the proper libs and tools
[Android Software/Hacking General [Developers Only]] sparksco:
Maybe it goes unanswered because of lack of information. What Linux do you run?
[Android Software/Hacking General [Developers Only]] sparksco:
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:

http://sabermod.com/Toolchains (DEV ONLY)/arm/cortex-a15_neon-vfpv4/

There's still options to compile the toolchains from source with cortex-a7 / a9 and the normal neon. So if you want other options other than the defaults, compile it from source. I don't have time to compile a toolchain twice each for a device I don't own.

Currently I recommend Ubuntu Trusty. It seems the most reliable and it's what Google says to use...
[Android Software/Hacking General [Developers Only]] navenedrob:
Can you give some tips on how to compile your toolchain on OS X?
[Android Software/Hacking General [Developers Only]] sparksco:
Nope, don't have a Mac.
[Android Software/Hacking General [Developers Only]] Shoaib05:
I am using Sabermod 6.0 aarch64 Toolchain to compile a CyanogenMod 3.10.49 arm64 kernel on my PC powered by Ubuntu 14.04.2 LTS x64 OS. However, I haven't been able to do so. I have spent many hours searching on Google but couldn't find anything useful. I am receiving the following error---

In file included from /home/shoaib05/android/source/Velocity_Kernel_for_MSM8939/arch/arm64/include/asm/bug.h:48:0,

from include/linux/bug.h:4,

from include/linux/kref.h:18,

from include/linux/of.h:21,

from drivers/media/platform/msm/camera_v2/msm.c:13:

drivers/media/platform/msm/camera_v2/msm.c: In function 'msm_probe':

drivers/media/platform/msm/camera_v2/msm.c:1057:17: warning: comparison of constant '0' with boolean expression is always false [-Wbool-compare]

error, forbidden warning: msm.c:1057

make[5]: *** [drivers/media/platform/msm/camera_v2/msm.o] Error 1

make[4]: *** [drivers/media/platform/msm/camera_v2] Error 2

make[3]: *** [drivers/media/platform/msm] Error 2

make[2]: *** [drivers/media/platform] Error 2

make[1]: *** [drivers/media] Error 2

make: *** [drivers] Error 2

Can anybody help me overcome this issue? Please! :)
[Android Software/Hacking General [Developers Only]] sparksco:
read the op
[Android Software/Hacking General [Developers Only]] Shoaib05:
Here is the kernel source---

https://github.com/Shoaib0597/Velocity_Kernel_for_MSM8939

Logcat? Is there a logcat for kernel building too?

I hope you can help me get past this error. :) I really want to use the 6.0 version of the Sabermod Toolchain. Please! :)
[Android Software/Hacking General [Developers Only]] sparksco:
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 building gcc. There's really nothing that can be done on the gcc side.

Kernel and ROM code must conform to gcc 99% of the time, not the other way around.
[Android Software/Hacking General [Developers Only]] bigsupersquid:
I'd say try putting -Wno-bool-compare in the Makefile cflags in that directory.
[Android Software/Hacking General [Developers Only]] Shoaib05:
Thanks for the info! bigsuper :good:

Didn't know you were the same Paul Beeler. Understood now what you said. :D

I have switched to UberTC and it compiles without a single error. :)
[Android Software/Hacking General [Developers Only]] sparksco:
I highly doubt that. So you'd rather use a sabermod kang? Cause that's what UBERTC is.
[Android Software/Hacking General [Developers Only]] klabit87:
I'm new to building a kernel and wish to use your toolchain.

I have done it before with the toolchain provided by google 4.7 but that was for an older device.

I am on Ubuntu 14.04 64bit have all the dependencies installed but when i compile i get this error.

/home/klabit/AndroidKernels/toolchains/saber-arm-eabi-6.0/bin/../libexec/gcc/arm-linux-gnueabi/6.0.x-sabermod/cc1: error while loading shared libraries: libisl.so.15: cannot open shared object file: No such file or directory
make[1]: *** [kernel/bounds.s] Error 1
make: *** [prepare0] Error 2

so I need the lib and I'm not entirely sure where to find it as searching hasn't turned up anything.

I am building a kernel for the Nexus 6

Any pointers would be much appreciated.

Thanks.
[Android Software/Hacking General [Developers Only]] Crimsonthunder:
Did you install the pre-built libs provided on the sabermod download server?
[Android Software/Hacking General [Developers Only]] klabit87:
You have got to be kidding me......

Sorry I didn't see that until you pointed it out.

thanks for your response. Everything working fine now :good:
[Android Software/Hacking General [Developers Only]] Crimsonthunder:
No problem! Have fun building! [emoji6]
[Android Software/Hacking General [Developers Only]] Shoaib05:
Yes, it does compile without an error. I have used UberTC 4.9.4 aarch64. I am using CyanogenMod's Kernel source. :)
[Android Software/Hacking General [Developers Only]] sparksco:
haha ?
[Android Software/Hacking General [Developers Only]] MEGAX91:
can i use GCC v6.0 with Ubuntu 15.04 ?

Edit : it's working fine.
[Android Software/Hacking General [Developers Only]] sparksco:
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.
[Android Software/Hacking General [Developers Only]] Shoaib05:
I am neither here for trolling nor for complaining. I have released my kernel so I have no reason to come here. I would have not replied if you haven't told me that you don't think it is possible to compile with UberTC without an error. :). I am learning development so my queries may be a little off. I understand what's this thread for and I am sorry if I did wrong coming here in the first place. Sorry for that Google+ post too.

:good:
[Android Software/Hacking General [Developers Only]] Adromir:
Okay, i am not sure, what I am actually doing wrong, because i think I read every tutorial over switching Toolchains by now and still can't get building with it work. I try to compile AICP LP (CM 12.1 based) with Sabermod for an arm64 Device (m9). If i use the original Toolchains, it builds fine. But as soon as I try switching to Sabermod, building breaks.

That is what i am currently doing:

I remove the original Toolchains via roomservice.xml

<remove-project name="platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8" />
<remove-project name="platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8" />
<remove-project name="platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.8" />
<remove-project name="CyanogenMod/android_prebuilts_gcc_linux-x86_aarch64_aarch64-linux-android-4.9" />

Then I download the these Toolchains from sabermod.com and put them into the according prebuilds directory

http://sabermod.com/Toolchains (DEV...ROM/aarch64-linux-android-4.9_10-24-15.tar.xz

http://sabermod.com/Toolchains (DEV...abi/arm-linux-androideabi-4.9_10-24-15.tar.xz

http://sabermod.com/Toolchains (DEV ONLY)/arm/arm-eabi/arm-eabi-4.8-09272015.tar.xz

But the build breaks with this error:

art/oatdump/oatdump.cc: In member function 'bool art::ImageDumper::Dump()':
art/oatdump/oatdump.cc:1125:3: error: the frame size of 1776 bytes is larger than 1728 bytes [-Werror=frame-larger-than=]

Anything i am missing? Downloading the wrong toolchains as a replacement maybe?
[Android Software/Hacking General [Developers Only]] sparksco:
Seems like a issue with your device (m9) but not really sure...
[Android Software/Hacking General [Developers Only]] desalesouche:
hi, may i ask you how you fixed that error?

specially that one = undefined reference to `__aeabi_ldivmod'
[Android Software/Hacking General [Developers Only]] Adromir:
Thanks for your reply. Would it be safe to turn the warning off? (if i find out where i can do that ;) ) I read through some stuff and mostly the solution was to turn the error off
[Android Software/Hacking General [Developers Only]] USBhost:
Are you building with GCC 5.x
[Android Software/Hacking General [Developers Only]] roshan2989:
Guys need help here..

compiling cm12.1,succesfully compiled 3 build with sabermod 4.9(rom) and gcc 4.8 for the kernel..so i change the kernel toolchain to sabermod 4.9..but im getting error,here is the following error (full error)

HOSTCC scripts/dtc/checks.o
CC scripts/mod/empty.o
ccache: FATAL: Could not find compiler "arm-eabi-gcc" in PATH
/home/preshot/android/system/kernel/motorola/msm8226/scripts/Makefile.build:307: recipe for target 'scripts/mod/empty.o' failed
make[4]: *** [scripts/mod/empty.o] Error 1
/home/preshot/android/system/kernel/motorola/msm8226/scripts/Makefile.build:443: recipe for target 'scripts/mod' failed
make[3]: *** [scripts/mod] Error 2
make[3]: *** Waiting for unfinished jobs....
HOSTCC scripts/dtc/data.o
SHIPPED scripts/dtc/dtc-lexer.lex.c

do i need edit the path in kernel/makefile? help would be apprieacted
[Android Software/Hacking General [Developers Only]] sparksco:
PATH is not toolchain related. That's something else in your build environment.
[Android Software/Hacking General [Developers Only]] Houge_Langley:
This errors I could not find out…
[Android Software/Hacking General [Developers Only]] _neutron_:
not sure if i should be asking here

fresh install of ubuntu 14.04

followed this link step by step

i cant compile any toolchain, fails at:

ERROR: **********************************ﾓ∆ⅰﾚㄩЯ∑**********************************

Sorry your build failed because
host CLOOG libraries failed to install

Email log to:
sabermod.team@gmail.com
for assistance.

Full Log is located at:
/tmp/sm-tc/smbuild/.log/arm-linux-gnueabi-4.8.5.log

Short Log is located at:
/tmp/sm-tc/smbuild/.log/arm-linux-gnueabi-4.8.5-SHORT.log

**************************************ﾓ∆ⅰﾚㄩЯ∑**********************************

short log:

checking build system type... Makefile.am:45: error: required directory ./osl does not exist

long log: attached (uploading to pastebin freezes browser for some reason)

this part isnt related anymore though is it?:

Installing cloog - Can be installed again

Note that this is required to build the toolchains, NO EXCEPTIONS. It is also usefull to have these installed for ROM building with SaberMod. These help a lot for graphite flags, which you should be using (if not no point in using sm). DO NOT install the package libcloog-isl-dev There is newer versions available that I have compiled as prebuilts to be used in /usr/lib/x86_64-linux-gnu download it as a zip file from here: https://github.com/SaberMod/sm-prebuilts/archive/master.zip

cd to where you have the repository downloaded

cd ~/Downloads
unzip sm-prebuilts-master.zip
sudo cp -R sm-prebuilts-master/cloog/lib/* -f /usr/lib/x86_64-linux-gnu
To install future updates, repeat this proccess.
[Android Software/Hacking General [Developers Only]] Synergy510:
Add GCC 6 support to your kernel

https://github.com/SaberMod/android...mmit/4a98feebe2cb735eef2299bc5512b9c83cc789ce
[Android Software/Hacking General [Developers Only]] sparksco:
There's nowhere in the README that says to install cloog... That was removed months ago.

https://gitlab.com/SaberMod/sabermod-manifest/commit/1b054df0062b81c586693a6f1c4bf0ddcab36ae9
[Android Software/Hacking General [Developers Only]] sparksco:
I suppose, but I'm not sure if that's the best way to fix it.
[Android Software/Hacking General [Developers Only]] Houge_Langley:
Thanks for your help[emoji16]
[Android Software/Hacking General [Developers Only]] _neutron_:
That's fine, I was just checking

Any chance of answering the actual query?
[Android Software/Hacking General [Developers Only]] sparksco:
I actually don't have that error. And I don't have cloog or isl libs installed from before either.