Thanks for all your input on this guys, I haven’t had chance to try this out yet but I’ve bookmarked the emails ready to read.  I liked the idea of bitbake but I couldn’t quickly pick it up so I’m going to have to sit down and learn it sometime in the next few weeks.

 

Thanks very much! :D

Drew

 

From: gumstix-users-bounces@lists.sourceforge.net [mailto:gumstix-users-bounces@lists.sourceforge.net] On Behalf Of Peter Buelow
Sent: 28 April 2008 18:00
To: General mailing list for gumstix users.
Subject: Re: [Gumstix-users] FW: Cross Compile Badness, AARRRRGGGGG!

 

Harry J Mason wrote:

On Fri, 25 Apr 2008, Drew wrote:
  
Harry Mason wrote:
    
On Fri, 25 Apr 2008, Drew wrote:
 
      
I configure the app like so.
export CC=~/gumstix/gumstix3/tmp/cross/arm-angstrom-linux-gnueabi/bin/gcc
        
[...]
      
./configure --host=arm-angstrom-linux-gnueabi --disable-gtkui
CROSS COMPILE Badness: /usr/include in INCLUDEPATH: /usr/include/glib-2.0
        
 
  
In many cases, configure will still need access to the host compiler, to
build utilities used in the compile process, so setting CC would prevent
this.
      
export
CC=/home/gumstix/gumstix/gumstix3/tmp/cross/arm-angstrom-linux-gnueabi/\
bin/gcc
    
 
You need to remove this. configure should automatically use the right compiler
based on the --host option.
 
  
If you're really using glib, you might also need to add the include path to
the include directory built with the cross compiler.
      
 
  
./configure --build=i386-linux --host=arm-angstrom-linux-gnueabi
--includedir=/home/gumstix/gumstix/gumstix3/tmp/staging/arm-angstrom-linux-g
nueabi/include/glib-2.0 --disable-gtkui
    
 
--includedir controls where to install include files, if the application
installs any. You need to tell gcc where to look for include files; the
simplest way is to tell autoconf via pkgconfig.
 
Add this environment variable first:
PKG_CONFIG_PATH=~/gumstix/gumstix3/tmp/staging/\
               arm-angstrom-linux-gnueabi/lib/pkgconfig
 
This might not be exactly right; I'm trying to work out the syntax from
bitbake's config.
 
Is there any reason you can't add a recipe and use bitbake to do this?
It might be simpler.
 
  

I think you hit it here Harry. For some reason, some configure scripts pick up the default pkg-config files instead of the cross location. These setup the /usr/include paths which a cross compiler will immediately barf on. I have the same issues compiling OGG and MPD packages in a different environment. The safest way to fix this is to use bitbake to be honest. Otherwise, you may end up running around in circles a lot.


-- 
Pete
 
Funny=Truth
Truth=Beauty
So take it as a complement when people say you look Funny.