Re: Can't use automake-1.10 in Mingw and Cygwin in Windows XP

[Ralf Wildenhues]

Hello Haibin, 

Please do not cross-post to more than one group.  There is no need. 

* haibin zhang wrote on Fri, Feb 09, 2007 at 04:43:17PM CET:
> I found that automake-1.10 can't be used in Mingw and Cygwin in
> Windows XP.

No, that's not right in general. 

> if I use automake-1.9.6, it 's ok. 
>
> I have diffed the line, that I found automake-1.10 have cut some words

Quoting from
<http://sources.redhat.com/cgi-bin/cvsweb.cgi/automake/NEWS?rev=1.318&conten 
t-type=text/x-cvsweb-markup&cvsroot=automake>: 

|   - Per-target flags are now correctly handled in link rules.
|
|     For instance maude_CFLAGS correctly overrides AM_CFLAGS; likewise
|     for maude_LDFLAGS and AM_LDFLAGS.  Previous versions bogusly
|     preferred AM_CFLAGS over maude_CFLAGS while linking, and they
|     used both AM_LDFLAGS and maude_LDFLAGS on the same link command.
|
|     The fix for compiler flags (i.e., using maude_CFLAGS instead of
|     AM_CFLAGS) should not hurt any package since that is how _CFLAGS
|     is expected to work (and actually works during compilation).
|
|     However using maude_LDFLAGS "instead of" AM_LDFLAGS rather than
|     "in addition to" breaks backward compatibility with older versions.
|     If your package used both variables, as in
|
|       AM_LDFLAGS = common flags
|       bin_PROGRAMS = a b c
|       a_LDFLAGS = more flags
|       ...
|
|     and assumed *_LDFLAGS would sum up, you should rewrite it as
|
|       AM_LDFLAGS = common flags
|       bin_PROGRAMS = a b c
|       a_LDFLAGS = $(AM_LDFLAGS) more flags
|       ...
|
|     This new behavior of *_LDFLAGS is more coherent with other
|     per-target variables, and the way *_LDFLAGS variables were
|     considered internally. 

Hope that helps. 

Cheers,
Ralf