[Linaro-dev] Maverick cross toolchain

[Dechesne, Nicolas]

On 07/24/2010 06:44 AM, Steve Langasek wrote:
> Hi Nicolas,
>
> On Thu, Jul 22, 2010 at 03:59:07PM +0200, Dechesne, Nicolas wrote:
>    
>> do you know when these packages will end up in ubuntu archives? can
>> we expect them to be available in 10.10 timeframe?
>>      
>    
>> How about cross compilation of packages, is that working? e.g. can I
>> create an ARM .deb from my x86 machine (assuming my upstream can be
>> cross compiled?).
>>      
> Cross-compilation of packages works, but is dependent on both the upstream
> and the packaging being cross-build-friendly.  I guess if it's your own
> package, then you've addressed this. :)
>    
yes, i am aware. all our packages already cross build (we used to 
develop with openembedded ;-))
> On Fri, Jul 23, 2010 at 02:46:57PM +0200, Dechesne, Nicolas wrote:
>    
>> I was able to cross compile some of my package with dpkg-buildpackage
>> -aarmel. However I am not able to install the -dev packages that I
>> generated (it contains .h files that are required to build my next set
>> of packages). I have used dpkg -a armel -i foo_armel.deb, and it
>> complains about pkg-config-armel-cross missing. what is the standard
>> procedure to install build-dep so that I can build all my packages? the
>> package files (.h, .la) have been installed in /usr/arm-linux-gnueabi,
>> but not the .so (which kind of make sense). but should I worry about the
>> pkg-config issue?
>>      
> When does it complain about pkg-config-armel-cross?  That doesn't sound like
> intended behavior, but I've not looked at pkg-config handling within
> dpkg-cross and the like.
>    
wookey's reply in this thread was very instructive, and perfectly 
addressed my problem.
> Why do you say it makes sense not to install the .so in
> /usr/arm-linux-gnueabi?  Sounds to me like a rather critical bit of the -dev
> package to have included.
>    
well... the .so is included in the standard package, not the -dev... i 
forgot to check this one too!