This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
John Clark wrote: > For quite a while I've had a pretty negative view on the use of the > 'configure' > set up utility. > > What seems to be a great idea appears to be fraught with problems when one > steps outside of the bounds of 'compiling on the target machine' > problems arise. Like they say, it's the worst system around, except for all the rest. > My 'method' of dealing with this is to basically had edit the configure > script > until it completes, eliminating the pattern "{ (exit 1); exit 1; };" in all > cases where the 'if test "$cross_compile" = yes ... starts of the if > statement. Much easier just to override the cached result variables (??_cv_*) for the non-functioning tests. ac_cv_foo_bar=1 ./configure -opts Brian -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |