I’m working on an integrated SDK for powerpc microprocessor which has some kernel modules. The kernel(3.12.37) and toolchain(powerpc gcc 4.9.2) provided by Yocto project. When i make SDK in native machine(x86_64bit Ubuntu 14) by mentioned toolchain and kernel source, I see these warnings during compilation of kernel module: These warnings appear when i insmod kernel module. I realized that this
Tag: toolchain
What’s the use of LLVM in Android NDK Toolchains?
What’s the use of LLVM in Android NDK Toolchains? A little recap: I was building my native project with Gradlew on Ubuntu, targeting arm and x86_64 architectures. Seems that LLVM were utilized to call C/C++ compiler of arm-linux-androideabi-4.9 as well as x86_64(?) The following is extracted from armeabi-v7a/ndkBuild_build_output.log: /home/mypc/Android/android-ndk-r17c/toolchains/llvm/prebuilt/linux-x86_64/bin/clang++ -MMD -MP -MF /home/mypc/git/android-project-1/build/intermediates/ndkBuild/debug/obj/local/armeabi-v7a/objs-debug/module-5/stream_cpp.o.d -gcc-toolchain /home/mypc/Android/android-ndk-r17c/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64 -fpic -ffunction-sections -funwind-tables -fstack-protector-strong -Wno-invalid-command-line-argument
How to modify the source of Buildroot packages for package development?
I’ve been using buildroot in order to build a toolchain using uclibc. Now, buildroot downloads all the packages, extract them and build them all.. I want to change the toolchain’s uclibc source and then recompile the toolchain with the new source and i just can’t understand how it can be done in the pretty way.. After it finishes building, all
Why does toolchain name have separate OS and EABI fields.?
For eg. arm-unknown-linux-gnueabi Now, once the OS i.e Linux is fixed, the C Library will be fixed (GLibc) and hence the calling convention and ABI being followed will be fixed. What is the requirement of 4th field i.e. ABI separately? Can a toolchain use a different ABI from the one used by underlying OS and LIBC. In that case how