any 64-bit toolchains out there?

not sure if this situation has changed lately, but are there any
validated 64-bit toolchains that can be used for a generic ARM
cross-compile? for instance, if you read here:

  http://elinux.org/BeagleBoard#U-Boot

there's an obvious reference to a codesourcery toolchain (i can hear
koen grinding his teeth already. :slight_smile:

  but, as best as i can tell, *all* of the CS toolchains are 32-bit.
the embinux folks have, as i recall, made available a 64-bit version,
but that's just for android, right?

  so ... anything like that out there? i'm just trying to collect
info for my upcoming talk this weekend.

rday

p.s. i realize my ignorance will be showing here but is there a
summary of all of the toolchains involved in various aspects of
building for the beagle? i realize angstrom builds its own, but i'm
just trying to clarify in my own mind where the rest fit in, and what
value (if any) they have.

Why do you need a 64-bit cross-compiler? Don't all
x86_64 distros have packages to support 32-bit binaries?

Laurent

just to push this one step further, over a year ago, philip balister
opined thusly (http://markmail.org/message/t4p75aoxrobx5o7k):

"I ran "bitbake meta-toolchain" and uploaded the results to:

  http://amethyst.openembedded.net/~crofton/sdk/

My better judgment tells me not to do this, since it may not even work
and will generate more questions than I can answer. I do my
development within OE, which is not ideal, but works for me (mostly)."

  but will that work now? can i just build a current toolchain with
angstrom with the "meta-toolchain" target, and use it for further
cross-compiles for my BB? and therefore ignore any further
codesourcery hassles?

rday

almost certainly. i would just prefer to not load 32-bit
compatibility packages onto my system if i don't absolutely have to.
but i will if there's no real choice.

rday

p.s. i realize my ignorance will be showing here but is there a
summary of all of the toolchains involved in various aspects of
building for the beagle? i realize angstrom builds its own, but i'm
just trying to clarify in my own mind where the rest fit in, and
what value (if any) they have.

just to push this one step further, over a year ago, philip balister
opined thusly (http://markmail.org/message/t4p75aoxrobx5o7k):

"I ran "bitbake meta-toolchain" and uploaded the results to:

I'll that again and see what I get :slight_smile: I am running F11 64 bit.

Philip

as am i and, FYI, i did detail exactly what it took to do all this
under F11 here:

  http://www.crashcourse.ca/wiki/index.php/Angstrom

but here's a followup question. what are the theoretical OE targets
to build if you wanted to just create the toolchain, then move it
elsewhere?

  i can see in my OE checkout under recipes/meta the .bb files
external-toolchain.bb and meta-toolchain.bb. how do those two relate
to each other? it's not clear what they represent or how one would
invoke them.

rday