|
From: | Tom Epperly |
Subject: | automake1.10 ignoring _LDFLAGS |
Date: | Tue, 13 Feb 2007 10:34:38 -0800 |
User-agent: | Thunderbird 1.5 (X11/20051201) |
I am in the process of upgrading Babel,
http://www.llnl.gov/CASC/components/, from automake 1.9.6 to automake --version automake (GNU automake) 1.10 Written by Tom Tromey <address@hidden> and Alexandre Duret-Lutz <address@hidden>. Copyright 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Automake 1.10 seems to be ignoring my _LDFLAGS settings for library and program targets. For example, my Makefile.am contains the following snippet (via an include). nodist_libClient_la_SOURCES = $(PUREBABELGEN) $(SYNCHBABELGEN) \ with Automake 1.10, I get in my Makefile.in: libClient.la: $(libClient_la_OBJECTS) $(libClient_la_DEPENDENCIES)with Automake 1.9.6, I get libClient.la: $(libClient_la_OBJECTS) $(libClient_la_DEPENDENCIES)If I search using emacs for the string libclient_la_LDFLAGS, it's defined but never referenced in the automake1.10 generated Makefile.in. Similarly, I have a program target runF902F90, and it defined runF902F90_LDFLAGS in the Makefile.am. The automake 1.9.6 generated Makefile.in references runF902F90_LDFLAGS in the link action, but there are no references (other than the line where it's defined) to runF902F90_LDFLAGS in the automake 1.10 generated Makefile.in. It's not always ignored. It appears to only be ignored when I need to define the _LINK target. It seems that automake 1.10 puts the _LDFLAGS in when it defines _LINK, and automake 1.9.6 did it differently. I can work around this issue by adding the _LDFLAGS variable reference when I define _LINK. Tom |
[Prev in Thread] | Current Thread | [Next in Thread] |