Re: AC_PROG_NM when compiling for mingw

[Ralf Wildenhues]

* Peter Rosin wrote on Fri, Apr 24, 2009 at 09:02:53AM CEST:
> Den 2009-04-24 03:53 skrev Bruno Haible:
>> 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>.

Will it produce wrong code then (with Cygwin 1.7/gcc4), or just if the
$host-nm is bogusly not found anyway?  What about Cygwin 1.7 with older
gcc?  (Yes, I understand you can only guess.)

With current stable Cygwin, is this only a cosmetic improvement of
configure output or a cause for a broken build?

Thanks for explaining to me again,
Ralf