Don't clobber LDFLAGS user variable
Fix a misunderstanding that's been present since the inception. The LDFLAGS variable is entirely at the builder's disposal. Flags needed for system-internal settings must go in the AM_* equivalents.
This commit is contained in:
parent
31788277f9
commit
6c35b9679b
@ -2,7 +2,7 @@ AM_CPPFLAGS = \
|
||||
-I$(top_srcdir) \
|
||||
$(OPM_BOOST_CPPFLAGS)
|
||||
|
||||
LDFLAGS = $(OPM_BOOST_LDFLAGS)
|
||||
AM_LDFLAGS = $(OPM_BOOST_LDFLAGS)
|
||||
|
||||
|
||||
LDADD = $(top_builddir)/lib/libopmcore.la
|
||||
|
@ -2,7 +2,7 @@ AM_CPPFLAGS = \
|
||||
-I$(top_srcdir) \
|
||||
$(OPM_BOOST_CPPFLAGS)
|
||||
|
||||
LDFLAGS = $(OPM_BOOST_LDFLAGS)
|
||||
AM_LDFLAGS = $(OPM_BOOST_LDFLAGS)
|
||||
|
||||
LDADD = $(top_builddir)/lib/libopmcore.la
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user