octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #55447] mkoctfile: wrong LFLAGS warning, reset


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #55447] mkoctfile: wrong LFLAGS warning, resets LDFLAGS
Date: Wed, 23 Jan 2019 17:43:04 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

Follow-up Comment #10, bug #55447 (project octave):

GNU make implicit rule looks like this


$(CXX) $(CXXFLAGS) $(CPPFLAGS) $(LDFLAGS) $(TARGET_ARCH) $^ $(LOADLIBES)
$(LDLIBS) -o $@


where '$^' are the source files, and notice the '-o $@' is at the end, the
order of that doesn't really matter. 'LDLIBS' appears to be GNU make's
equivalent of automake's 'LIBS' variable. It's documented in the GNU make
manual, in particular the difference between 'LDFLAGS' and 'LDLIBS' is clearly
described.

GNU automake default link rule looks like this


$(CXXLD) $(AM_CXXFLAGS) $(CXXFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -o $@
$(foo_OBJECTS) $(foo_LDADD) $(LIBS)


where 'foo_OBJECTS' is the automake variable derived from 'foo_SOURCES', and
'foo_LDADD' is a documented automake variable for that purpose.

If we do add a new variable, we can create a new one called either 'LIBS' or
'LDLIBS', with a default value of empty, as a placeholder for the user to add
whatever library operands they want to the link command. We can add that now
for Octave 5 if we agree that this would be useful.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?55447>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]