|
From: | Markus Mützel |
Subject: | [Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS on Windows |
Date: | Mon, 28 Sep 2020 14:35:17 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.121 Safari/537.36 Edg/85.0.564.63 |
Follow-up Comment #12, bug #59173 (project octave): Dang! The problem I had with the sparsersb package wasn't caused by the wrong LDFLAGS but by me not knowing the right way to do things. Sorry for that. Still, the flags returned by mkoctfile look strange. But maybe we can lower the priority until we find a real life problem. The change that Rik proposes in comment #11 is much less intrusive and might be what is expected since LDFLAGS should be used as a replacement of the deprecated LFLAGS. And that change will make `mkoctfile -p LDFLAGS` return the same that `mkoctfile -p LFLAGS` returned previously. Is it ok that additional flags (like "-Wl,--export-all-symbols" from comment #0) might be lost? _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?59173> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |