Re: AC_PROG_NM when compiling for mingw

[Peter Rosin]

Hi Bruno,

Den 2009-04-24 03:53 skrev Bruno Haible:
*snip*
> Therefore I propose to make LT_PATH_NM know about this case. With the attached
> patch, I get the output:
>
>   checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
>   checking the name lister (/usr/bin/nm -B) interface... BSD nm
>
>
> 2009-04-23  Bruno Haible  <address@hidden>
>
>         * libltdl/m4/libtool.m4 (LT_PATH_NM): Try "nm" program also when
>         compiling for mingw in a cygwin environment.
>
> --- libltdl/m4/libtool.m4.orig  2009-04-24 03:43:53.000000000 +0200
> +++ libltdl/m4/libtool.m4       2009-04-24 03:25:41.000000000 +0200
> @@ -3172,7 +3172,10 @@
>    lt_cv_path_NM="$NM"
>  else
>    lt_nm_to_check="${ac_tool_prefix}nm"
> -  if test -n "$ac_tool_prefix" && test "$build" = "$host"; then
> +  if test -n "$ac_tool_prefix" \
> +     && { test "$build" = "$host" \
> +          || { test "$build_os" = cygwin && test "$host_os" = mingw32; }; \
> +        }; then
>      lt_nm_to_check="$lt_nm_to_check nm"
>    fi
>    for lt_tmp_nm in $lt_nm_to_check; do

That will be wrong when Cygwin 1.7/gcc4 is released with proper
cross tools for building mingw binaries, which should be
Real Soon Now<tm>. It will be sooo nice when the -mno-cygwin crap
is history. Until then, is the extra output really so bad? It's
after all a very strange case when there is no suitably named nm
in sight.

Cheers,
Peter