[Buildroot] continued issues with AR

Heiko Zuerker heiko at zuerker.org
Sun Dec 26 14:15:22 UTC 2010


Quoting Lionel Landwerlin <llandwerlin at gmail.com>:

> Le samedi 25 décembre 2010 à 10:20 -0600, Heiko Zuerker a écrit :
>> Hey,
>>
>> it seems like I keep running into issues where it tries to use my
>> local ar, instead of the one from the external toolchain.
>> I'm not familiar with the workings behind the scenes of buildroot, but
>> is it possible that something is missing somewhere?
>> Do we need to always set i.e. AR=$(TARGET_AR) ?
>> Could the same be happening for other files like ld,gcc and so on?
>>
>
> Yup,
>
> As some others packages, lvm2 does not use automake. So makefiles
> remains mostly "hand written"...
>
> With fully autotooled packages, we define CC/AR/LD/etc... variables at
> configure time, so the configure script generates the makefiles with
> proper CC/AR/LD/etc... variables definitions.
> With semi autotooled packages as lvm2, we rely on what as been written
> by the lvm2 developers.
>
> One solution could be to define a kind of Makefile.half.autotool.in top
> makefile to handle these specials cases (which do not seem that special
> after all), in which we would define AR/CC/LD/etc... at build time (most
> of them are defined in TARGET_CONFIGURE_OPTS already).
>
> What do you think ?

Wouldn't it make sense to always define the variables, using a subset  
of TARGET_CONFIGURE_OPTS? Don't we always need them to point to the  
cross compiler?

Or maybe some configuration variable you could specify in the  
Makefile, which then takes care of all the magic.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.





More information about the buildroot mailing list