Murray.Jensen at csiro.au wrote:
> On Tue, 01 Nov 2005 14:32:31 +0100, Joerg Schilling writes:
> >> I don't think autoconf deserves the bad rap about cross-compiling anymore
> >> (besides, its just a tool really, the problem was always with the software
> >> authors which didn't write the autoconf scripts properly - they tended not
> >> to cross-compile so much until recently).
> >
> >If you believe this, please explain why.
>
> I have cross-built a Linux for our embedded PowerPC boards for many years
> now. I remember the early days when almost everything complained about cross
> building.
autoconf allows to set up ONE default for cross compilation.
If people used _this_ single default to "compile in" Linux defaults, then people
who like to cross compile for Linux are happy but all other people will be
sad.....
> >Don't lok at simple programs, look at cdrecord, star or similar.
>
> I have to build boot code, linux kernel, kernel modules (drivers etc), and
> all the standard Linux/GNU software (from init to shells to utilities etc).
>
> I must admit that I have no need for things like graphics adapters, cd/dvd
> drives (or any disk drives at all), keyboards/misc, etc. so I suppose you
> could say that most of the stuff I deal with is "simple".
>
> But in the end, it depends on the author of the "package" and how well they
> write their autoconf scripts. You can work out most things about the target
> environment in a cross-building friendly fashion.
No - sorry autoconf does not really support cross compilation.
J?rg
--
EMail:joerg at schily.isdn.cs.tu-berlin.de (home) J?rg Schilling D-13353 Berlin
js at cs.tu-berlin.de (uni)
schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
