|
From: | Rik |
Subject: | [Octave-bug-tracker] [bug #55447] mkoctfile: wrong LFLAGS warning, resets LDFLAGS |
Date: | Wed, 23 Jan 2019 17:24:22 -0500 (EST) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko |
Follow-up Comment #8, bug #55447 (project octave): @Mike: Could you check the order of the flags? My understanding is that LDFLAGS needs to be after the output argument -o. Here is an example taken from https://stackoverflow.com/questions/13249610/how-to-use-ldflags-in-makefile. $(CC) $(CFLAGS) $(OBJECTS) -o client $(LDFLAGS) The ordinary link command is now: std::string cmd = (vars["DL_LD"] + ' ' + vars["ALL_CXXFLAGS"] + ' ' + vars["DL_LDFLAGS"] + ' ' + vars["LDFLAGS"] + ' ' + pass_on_options + " -o " + octfile + ' ' + objfiles + ' ' + libfiles + ' ' + ldflags + ' ' + vars["LFLAGS"] + ' ' + octave_libs + ' ' + vars["OCT_LINK_OPTS"] + ' ' + vars["OCT_LINK_DEPS"]); I believe LDFLAGS should be placed after LFLAGS so that, if present, it overrides LFLAGS and ldflags. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?55447> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |