Re: When crosscompiling, does configure really need --build?

2002-10-04 Thread Stewart Brodie
> --host. If a cross compiler is detected then cross compile mode will be used." > > Why? I don't know, but I get that all tbe time too, so I have a script that runs the configure script for me and it always puts in: --build=`config.guess` which seems to make it happy e

Re: cross compiling -- building programs to run on build system

2002-10-08 Thread Stewart Brodie
ters so that these ones take precedence. Another approach I have seen is software relying on a separate environment variable to indicate the native C compiler to use. Various names are used for this CC_FOR_BUILD or BUILD_CC. -- Stewart Brodie, Senior Software Engineer Pace Micro Technology PLC Cambridge, CB5 8PB, United Kingdom http://www.pace.co.uk

Re: cross compiling -- building programs to run on build system

2002-10-08 Thread Stewart Brodie
In message <[EMAIL PROTECTED]> Andreas Schwab <[EMAIL PROTECTED]> wrote: > Stewart Brodie <[EMAIL PROTECTED]> writes: > > |> This is the approach that I have taken: > |> > |> AC_MSG_NOTICE([configuring the tools for *native* builds]) &

Re: functions in different libraries on different OSes.

2002-10-10 Thread Stewart Brodie
header files, so I might as well check that one. There are systems that do not have sys/types.h. That way, all header file checks are done the same way. That also means that I always check for stdio.h too, which is contrary to the recommendations, but makes all the header checks the same. --

Re: Alternate header locations

2002-10-15 Thread Stewart Brodie
er is required is to simply remove the inclusion of that header and see what falls over. That will at least show you one place where declarations from that header are required. It's more complicated than that to find all the uses of such declarations, of course. -- Stewart Brodie, Senior Soft

Re: removing the old build/host/target compatibility code (Was: current glibc vs debian sid)

2002-10-24 Thread Stewart Brodie
nv_host_alias_set=${host_alias+set} ac_cv_env_host_alias_value=$host_alias ac_env_target_alias_set=${target_alias+set} ac_env_target_alias_value=$target_alias ac_cv_env_target_alias_set=${target_alias+set} ac_cv_env_target_alias_value=$target_alias # Ensure ac_tool_prefix is set early enough test -n "

Re: PACKAGE_FOO macros

2002-10-25 Thread Stewart Brodie
lt;$2>" else pace_include_$1="/* #include <$2> */" fi AC_SUBST([pace_include_$1]) ] ) I couldn't be bothered to make the variable name be dependent on the header name - I probably ought to have taken the time to do that, but there wasn't time at the time. -- Stewart Brodie, Senior Software Engineer Pace Micro Technology PLC 645 Newmarket Road Cambridge, CB5 8PB, United Kingdom WWW: http://www.pacemicro.com/