[take 2] Re: configuration patch for host_exeext != ""
Jeffrey A Law
law@upchuck.cygnus.com
Wed Mar 24 21:48:00 GMT 1999
In message <199902122321.RAA19303@modi.xraylith.wisc.edu>you write:
> Sigh. I was afraid you wouldn't go for my hack. Here's my current setup.
> Need to be careful in handling cross vs canadian cross builds.
>
> The following changes make is possible to configure and build egcs target
> libraries in all the 3 modes -- native, cross and canadian cross.
>
> Few notes:
> - I'm using AC_EXEEXT, which AFAIK appeared in autoconf 2.13. I don't
> know what's in 2.12.1, nor can I find it, so don't know if the PREREQ
> change is needed or not.
> - When building target libraries, host takes on the value of the target
> system, and there is no reliable way to get the program extension, if
> any, when doing cross-builds. It works for native and canadian cross
> however. That's why we need to check for compiler name using both
> without extension and with one.
> - libstdc++/libio changes are more fragile, since I didn't/couldn't use
> AC_EXEEXT which does a bit more. DJGPP and other ports should add
> their own to the case statement.
> - The change is really 1-3 liner, and the rest is really reformatting. I
> don't like those tabs that make lines really really long.
> - Even with this, libobjc cannot be built when doing canadian cross,
> thanks to the need to build runtime-info.h. I'll send a separate patch
> for that later.
>
> libio/libstdc++:
>
> Fri Feb 12 16:37:45 1999 Mumit Khan <khan@xraylith.wisc.edu>
>
> * configure.in (EXEEXT): Define.
> (compiler_name): Use.
>
> libchill/libf2c/libobjc:
>
> Fri Feb 12 16:37:45 1999 Mumit Khan <khan@xraylith.wisc.edu>
>
> * configure.in (AC_PREREQ): Update to 2.13.
> (AC_EXEEXT): Call to find possible file extension.
> (compiler_name): Use.
> * configure: Regenerate.
THanks. Installed! Sorry for the delay
Jeff
ps. I changed "-o" to "|| test" in a variety of places since apparently
-o is not portable?!?
More information about the Gcc-patches
mailing list