cross compiling eglibc with Linaro toolchain
- date: January 17, 2012
I am trying to cross-compile Eglibc library with Linaro tool chain(which is a pre built tool chain for arm, running on ubuntu).My aim is to cross-compile the library and add it with the tool-chain.
I referred to the link http://www.eglibc.org/archives/patches/msg00078.html README. (README.cross-compiling of the libc) and did the following.
I thought that binutils is not required as the tool chain itself contains the loader, assembler etc.(which are the most important in the binutils).So i skipped that step.
I did the below steps as in the above link.
1) copied the Linux Kernel Headers
2) EGLIBC Headers and Preliminary Objects
2.1) configuring the Eglibc headers by the below steps.
$ ~/cross_compile_eglibc/ppc/obj/eglibc-headers$ BUILD_CC=gcc CC=/home/appan/cross_compile_eglibc/ppc/tools/bin/arm-linux-gnueabi-gcc CXX=/home/appan/cross_compile_eglibc/ppc/tools/bin/arm-linux-gnueabi-cpp AR=/home/appan/cross_compile_eglibc
Valgrind for ARM with Linaro Toolchain requiring libc6dbg with Buildroot
location: linuxexchange.com - date: January 10, 2013
I cross compiled Valgrind (http://valgrind.org/downloads/valgrind-3.8.1.tar.bz2) for ARM using the following commands with the Linaro Toolchain on my Ubuntu 10.04 host ( I am using Buildroot ):
CC=arm-linux-gnueabi-gcc CFLAGS=-I/home/user/toolchain/linaro/arm-linux-gnueabi/libc/usr/include LDFLAGS=-L/home/user/toolchain/linaro/arm-linux-gnueabi/libc/usr/lib ./configure --prefix=/opt/valgrind --host=armv7-none-linux-gnueabi --target=arm-none-linux-gnueabi --build=i386-ubuntu-linux
sudo make install
When I copy the binaries to my ARM target board, I get the following error:
==413== Memcheck, a memory error detector
==413== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==413== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
==413== Command: /home/user/testApp
valgrind: Fatal error at startup: a function redirection
valgrind: which is mandatory for this platform-tool combination
[SOLVED] Cross compiling software for arm with a proprietary toolchain
location: linuxquestions.com - date: February 28, 2011
We have a device here at work running an Arm processor, I have a cross-compiler for the device, it was distributed to our company with the linux distribution we are using on the device (montavista linux). I would love to be able to cross compile some software for this device, however, I really suck at this kind of thing. Whenever I try to cross compile software, I usually get an error like "unrecognized host platform" (I'm paraphrasing obviously), but the toolchain is not that much different from a generic Arm toolchain, just with some extra libraries installed and stuff. I tried using other arm toolchains, but those are a crapshoot, they compile fine, but they don't always run correctly on the device (for instance, busybox).
The reason I get the unrecognized platform error is because the toolchain has a weird prefix on it (arm_v5t_le-) which the configure script can't handle, but if it would just try to cross compile it like it does with other arm targets, it would work fin
cross compiling on ubuntu fails with "gcc: error trying to exec 'cc1':"
location: ubuntuforums.com - date: March 23, 2012
I am trying to cross compile for an embedded linux platform.
I am running on ubuntu and I am using a gcc based toolchain that was supplied by the folks who manufacture the platform.
They have given me a total of five toolchains and four work just fine. I have been able to build code and ship libraries back and I have been told that these are working OK.
For the last toolchain, I get the following error when I try to run make:
gcc: error trying to exec 'cc1': execvp: No such file or directory
There is a cc1 in the toolchain of similar size to the cc1 in the other toolchains and all of the permissions and access modes look OK.
The folks who supplied the toolchain say that it works for them so I expect that it may be some install or config issue.
compiling software with crosstoolng's toolchain
location: ubuntuforums.com - date: December 13, 2010
I'm trying to compile some software for an embedded linux system using crosstool-ng and I seem to be stuck. I have created a toolchain using crosstool-ng on another box, but now that box has 2 compilers - the gcc compiler it had installed and the newly created one that's part of a toolchain. The entire toolchain was installed to a folder at ~/x-tools. I know I can compile programs one file at a time with the newly created gcc compiler (toolchain_gcc -o test_prog test.c), but what if I want to compile an entire program from source?
If I have a program, lets say a calculator that I downloaded as calc.tar.gz:
I untar it
cd into folder
then what? How do I tell ./configure and 'make' that I want to use the toolchain to compile the program and not the OS's regular compiler?
[SOLVED] cross compiling for arm with buildroot
location: linuxquestions.com - date: January 27, 2011
this is my first attempt at cross compiling. I'm trying to build some boot and kernel images for my WD Mybook world edition, which uses an arm processor on my x86_64 host box. Ultimately i'd like to install slackarm. Lilo doesn't work on arm so you have to compile your own kernel and have the bootloader statically linked to kernel inorder to boot the OS. So i'm using my slackware install to cross compile the boot loaders (u-boot) and kernel image (uImage).
I've successfully compiled the buildroot environment which has generated the arm-linux-* binaries, eg, gcc 3.4.2 for arm.
Cross Compiling Linux Arm Kernel with new driver module
location: linuxexchange.com - date: January 21, 2014
I am trying to include a driver for use on my arch linux arm machine. I tried using these steps to include the driver module, but my cross-compiled kernel with the added driver doesn't load.
1) Include the driver I want to add by making it have < M > beside it's
name in make ARCH=arm menuconfig
2) run: make ARCH=arm CROSS_COMPILE=/home/z3/bin/arm- (the path for my cross-compiling toolchain)
3) run: make ARCH=arm CROSS_COMPILE=/home/z3/bin/arm- modules
4) run: make ARCH=arm CROSS_COMPILE=/home/z3/bin/arm- install
5) run: make ARCH=arm CROSS_COMPILE=/home/z3/bin/arm- modules_install
6) copy my uImage from: arch/arm/boot
to my boot location: /tftpboot/
Then when my embedded linux arm tries to load the kernel uImage, it hangs with:
EDIT: Changed the entry point address to 80008000, so now it hangs with:
Load address: 0x81800000
how to work with external libraries when cross compiling?
location: linuxexchange.com - date: January 1, 1970
I am writing some code for raspberry pi ARM target on x86 ubuntu machine. I am using the gcc-linaro-armhf toolchain. I am able to cross compile and run some independent programs on pi. Now, I want to link my code with external library such as ncurses. How can I achieve this.
Should I just link my program with the existing ncurses lib on host machine and then run on ARM? (I don't think this will work)
Do I need to get source or prebuilt version of lib for arm, put it in my lib path and then compile?
What is the best practice in this kind of situation?
I also want to know how it works for the c stdlib. In my program I used the stdio functions and it worked after cross compiling without doing anything special. I just provided path for my arm gcc in makefile. So, I want to know, how it got correct std headers and libs?
Cross compiling Qt application for Windows on Linux with dynamic linking
location: linuxexchange.com - date: January 30, 2013
To comply with Qt's LGPL license, an application using the Qt library must either make the source code available or link dynamically against Qt (if I got that correctly in this few words).
So I'd like to create a closed source application doing exactly that. Additionally, I'd like to develop on Linux (currently Xubuntu 12.04) using g++/MinGW with C++11 support to create windows binaries. I followed this helpful guide to accomplish the latter. But as the guide also states, statically linked executables are created.
Since I used MXE to automatically download and build the Qt library (version 5.0), I didn't have much of a chance to influence the process. So my question is, how do I create dynamically linked versions of the Qt library and respective applications?
Cross compiling for mac os x on ubuntu
location: ubuntuforums.com - date: June 23, 2008
I have a c program I'd like to compile for mac os x. Sadly I don't have a mac, but a mac user have told me that my program compiles without a problem on his mac.
I've been cross compiling for windows using mingw, but there seems to be no such package for mac os x as well, and nothing I've found on the web was very helpful thus far.
Can anyone here guide me to an easy to follow tutorial/howto?
Page: 1 2 3 4 5 6 7 8 9 10