crosstool - x86_64 as i686->i686 or x86_64->i686
Tue Jan 10 11:02:00 GMT 2006
Dan Kegel wrote:
> On 1/9/06, Keith Kyzivat <firstname.lastname@example.org> wrote:
>> I've got a sucessful canadian cross that is x86_64 built, i686 hosted
>> and i686 targetted, but ran into some ranlib problems that I fixed. ...
>> The obvious thing to choose was to set RANLIB the same way I set AR and
>> CC, with the ranlib generated from step 1.
>> investigating crosstool.sh seemed to support that argument, and off I
>> sent crosstool.
>> Now it's done, and voila! I've got a canadian cross x86_64 built i686
>> -> i686 cross-compiler.
>> Now, here's the question: why is RANLIB not detected properly? Why
>> wasn't this caught before by Dan when he put in the bit of info on
>> canadian cross builds?
> Who knows! Sounds like an obvious thing to add, though.
It's probably because ranlib has become somewhat neglected since the same
functionality was incorporated into ar.
Out of curiosity, why isn't $RANLIB just defined in terms of $AR?
Can't think of a witty .sigline today....
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to email@example.com
More information about the crossgcc