Re: how to determine (after the fact) the version of the componentsused to create the cross compiler when using crosstool?

[Daniel Kegel <dank at kegel dot com>]

Ken Wolcott wrote:
>   But how to determine what version of binutils was used? 

ld -v

> How to determine the version of the linux kernel headers?

See either UTS_RELEASE or LINUX_VERSION_CODE in <linux/version.h>

>   Is there a way to embed this information somehow in the resulting tool 
> chain?

It's there, you just have to pull it out with a little shell script...

>   Would be nice to get an answer quickly as I am under a tight deadline and I 
> really have no clue how to generate this information.
>
>   I best guess so far is to modify crosstool so that the versions of all of 
> the components is written in a text file somewhere embedded in the resultant 
> cross tool chain, but how could I have any certainty that it would remain 
> with the tool chain?

I'd suggest writing a shell script that does gcc -v, ld -v, peeks at lib/libc*,
and peeks at <linux/version.h>, and prints the results.

I might include something like that in a future crosstool.

Alternately, I could change $TOOLCOMBO to encode binutils and kernel version.
That'd make for long paths, but isn't such a bad idea, really.
- Dan

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com