|
From: | Carnë Draug |
Subject: | [Octave-bug-tracker] [bug #48678] mkoctfile returns linker flags on LFLAGS instead of LDFLAGS |
Date: | Sat, 13 Aug 2016 23:09:05 +0000 (UTC) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0 |
Follow-up Comment #6, bug #48678 (project octave): That explains the large set of flags. I never quite understood why we had so many and why they looked kind of redundant. I thought the purpose of mkoctfile was to build oct files and that therefore "-p" would be the flags that mkoctfile uses. Because mkoctfile should not ignore user environment variables, in my view that includes the flags required by Octave plus whatever the user has set in the environment if any. If a user would want to get only the flags that Octave requires (instead of the flags that mkoctfile will use), then it should use octave-config (which I now realize doesn't really have any flags and is not an Octave specific version of pkg-config). _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?48678> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |