No clear differentiation between programs that run in the host environment
and programs that need to be compiled in the target environment.
Good exercise would be to build LEAF on a non x86 linux box and find all
of this crap (for example, linux/scripts/mkdep (a binary) is compiled
against uclibc by the target compiler, but run on the host).

(Of course, I've mentioned this before... but it really needs to get fixed
 as our host and target environments diverge)
Good luck on that one. I'd really like to see that too, but the last
time I tried, I failed miserably. There are _many_ configure scripts out
there that simply cannot cope with a true cross-compile - many assume
that the build host will also be the target host.
If you specify the appropriate options (--build and --host, if I recall
correctly), they fail. So, even if we fix all the "crap" that's compiled
against uclibc but runs on the build-host, it wouldn't really help much,
unless somebody takes the time and cleans up those troublesome configure
scripts too, and then takes the changes upstream, so the changes to the
configure scripts wouldn't have to be re-applied with the next version.

True, but the only way to solve this is to start, one package at a time. Some better documentation on the build environment would help (no, I'm not volunteering at the moment), perhaps what we need is a "hello world" package that works in a completely cross-compiled environment as a start? Sorry, I can't volunteer for this this year, my head is exploding with other work (in fact, apologies for the delay in replying).


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

_______________________________________________
leaf-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to