Hi :) On Sun 20 Mar 2011 14:50, l...@gnu.org (Ludovic Courtès) writes:
> There’s already ‘%host-type’. Ah, cool. > However, I don’t think defining ‘%target-type’ would make sense > since: > > 1. Of the GNU triplet, only the $target_arch matters for bytecode; > > 2. You can really choose at run-time what target you want to build > for, by just setting the endianness fluid. Can I convince you otherwise? Right now it's endianness, but I would like to hack an ARM native compiler sometime soonish, and that's going to be easier as a cross-compiler; and at that point you do need the %target-type. I guess that's my point: right now it's endianness, in the future it will be more things, might as well go ahead and add %target-type now. > Now, if we want to produce something comparable to cross-GCC & > cross-Binutils[*], we could install, say, arm-linux-gnueabi-guile-tools Yes, that sounds good, though I would be happier if we did this simply with --program-prefix and --target. I really don't want to add an endianness kwarg to `compile', for example, though an endianness fluid in (language assembly) is OK for me. Cheers, Andy -- http://wingolog.org/
