[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS o
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS on Windows |
Date: |
Mon, 28 Sep 2020 11:58:21 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.83 Safari/537.36 |
Follow-up Comment #8, bug #59173 (project octave):
mkoctfile always checks the environment variable first and uses that in
preference to anything set during the build configuration. See
src/mkoctfile.in.cc. For this particular example,
vars["LDFLAGS"] = get_variable ("LDFLAGS", %OCTAVE_CONF_LDFLAGS%);
On Linux, this just generally works and the override mechanism is only used
when the user themselves have specified something.
I suspect on cross-builds anything from the build machine is likely to be
incorrect. Does Octave's initialization file for windows (.bat or .vbs) set
up the environment variables so that mkoctfile works correctly?
If so, it may be that mkoctfile the executable should not be called directly
from the command line but needs a wrapper to set the environment variables
correctly.
I'm just guessing that the Makefile for sparsersb calls 'mkoctfile -p LDFLAGS'
directly from the command line. An replacement, just to see if this works,
would be
octave --eval 'mkoctfile -p LDFLAGS'
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?59173>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS on Windows, Markus Mützel, 2020/09/23
- [Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS on Windows, John Donoghue, 2020/09/24
- [Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS on Windows, John W. Eaton, 2020/09/24
- [Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS on Windows, Rik, 2020/09/24
- [Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS on Windows, Markus Mützel, 2020/09/27
- [Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS on Windows, Rik, 2020/09/27
- [Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS on Windows, Markus Mützel, 2020/09/28
- [Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS on Windows, John Donoghue, 2020/09/28
- [Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS on Windows,
Rik <=
- [Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS on Windows, Rik, 2020/09/28
- [Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS on Windows, Markus Mützel, 2020/09/28
- [Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS on Windows, Rik, 2020/09/28
- [Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS on Windows, Markus Mützel, 2020/09/28
- [Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS on Windows, Rik, 2020/09/28
- [Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS on Windows, Markus Mützel, 2020/09/29
- [Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS on Windows, Rik, 2020/09/29
- [Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS on Windows, John W. Eaton, 2020/09/29
- [Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS on Windows, John W. Eaton, 2020/09/29
- [Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS on Windows, Markus Mützel, 2020/09/29