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

[Ken Wolcott <ken dot wolcott at med dot ge dot com>]

Hi Dan;

  Thanks for your reply.  It does look kind of obvious now that you have 
specified "ld -v" -- doh!

  But I don't have access to the arm platform, I just build the arm cross tool 
chain (and some time soon, the arm environment).  I bundle it up and others 
take it and install it on the target board.  I need to have a means of 
determining the versions independent of the platform that I'm on...of course 
what you have suggested would work after the arm cross tool chain (and arm 
environment) were installed and running on the target...

  It would be real nice to make the $TOOLCOMBO variable have all the 
components specified (that's what I do locally).  I also remove the 
writeability test file.

  Didn't you mention in another mailing list that you already had version 0.28 
of crosstool available?  I still see only version 0.27 on your website...

  Hope your RSI gets better -- seems like the only solution is to reduce the 
typing? :-(

Thanks,
Ken

On Friday 20 February 2004 16:22, Daniel Kegel wrote:
> 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