Re: [ts-7000] Re: How to make an EABI cross compiler for ts boards, step by step

[Scott Zimmerman <>]

FWIW: I just spent a couple of hours playing with dpkg-cross and apt-cross to try download cross compiled versions of the libs I want use with my new EABI cross compiler.  I couldn't ever get them to find anything that was available for the arm architecture.  I know there is an X11 that is cross compiled for debian arm.  I can download it using apt-get from the TS-7390.  Why I can't I convince my Ubuntu laptop to go get the same package?!  So frustrating.  So now I have a beautiful cross compile and if all I want to do is build helloworld I'm in fat city.  But I want to build anything real using X11, I'm back to building on the TS-7390 itself.  Is this really such a hard question that no one the list knows the answer?  What is everyone using for GUI on the TS-7000 boards?

Frustrated in California,

...Z

On Fri, Aug 14, 2009 at 5:36 PM, Dunge2 <> wrote:

 

--- In ts-7000%40yahoogroups.com, "andy.shinsel" <> wrote:

> Sorry I missed that, you might also want to change /bin/sh to point to /bin/bash instead of dash.
>
> This really caught my attention:
> > > I tried on two different computer, one on Debian, the other on Ubuntu. After about 1h after I call ./ct-ng build, I get the same error:
>
> After an hour? Make sure that you set the flags properly for multiple process building. On my Quad Core, i set it to 8, and my total compile time is about 15 minutes. On my dual core laptop, I set it to 4, and it takes around 40 minutes or so.
>

Hello, thanks for answering.
Yeah don't worry about the time, I just let your config file "CT_PARALLEL_JOBS=8" while I was on a single core computer. I tried later on my core2duo with build.4 and it went quite fast.

I'm having a bit of trouble of what to do next though. If I understood correctly, I can use this toolchain to build optional libs with all their dependencies, which I would then copy to the ts-provided debian-armel rootfs to use them.

So I want to build multiple libs from source to create some kind of rootfs with everything under the sys-root directory.

I want to build to following libs (not in this order):
glib, gtk+, pango, pixman, cairomm, cairo, libsigc++, glibmm, fontconfig, gtkmm, freetype, glade3, libglademm. I guess cairo and freetype can gain a lot from the FPU support.

I have set the following envvar:
CPPFLAGS="-I/home/dunge/x-tools/arm-ep9312-linux-gnueabi/arm-ep9312-linux-gnueabi/sys-root/usr/include"
LDFLAGS="-L/home/dunge/x-tools/arm-ep9312-linux-gnueabi/arm-ep9312-linux-gnueabi/sys-root/usr/lib"
PKG_CONFIG_PATH="/home/dunge/x-tools/arm-ep9312-linux-gnueabi/arm-ep9312-linux-gnueabi/sys-root/usr/lib/pkgconfig"
LD_LIBRARY_PATH="/home/dunge/x-tools/arm-ep9312-linux-gnueabi/arm-ep9312-linux-gnueabi/sys-root/usr/lib"
PATH="/home/dunge/x-tools/arm-ep9312-linux-gnueabi/arm-ep9312-linux-gnueabi/sys-root/usr/bin:/home/dunge/x-tools/arm-ep9312-linux-gnueabi/bin:$PATH"
export CPPFLAGS LDFLAGS PKG_CONFIG_PATH LD_LIBRARY_PATH PATH

I then call the libs configure script with these parameters:
--host=arm-ep9312-linux-gnueabi --prefix=/home/dunge/x-tools/arm-ep9312-linux-gnueabi/arm-ep9312-linux-gnueabi/sys-root/usr

Problem is, when I run make and make install afterward, it still try to link against libs and include files in /usr/* and obv fail.

I understand some libs needs other customs configure commands, likes --sysconfdir or --with-arch, or god know what. I could make everything point to the crosstool sys-root path, but how do you know what you should pass when it's documented nowhere?.

__._,_.___

Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required)
Change settings via email: =Email Delivery: Digest | m("yahoogroups.com?subject","ts-7000-fullfeatured");=Change Delivery Format: Fully Featured">Switch to Fully Featured
Visit Your Group | Yahoo! Groups Terms of Use | =Unsubscribe

__,_._,___