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

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

[Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS o


From: Markus Mützel
Subject: [Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS on Windows
Date: Mon, 28 Sep 2020 02:34:41 -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 #6, bug #59173 (project octave):

I regularly compile .oct files on Windows before doing similar changes in core
files. That is by far faster than cross-compiling Octave completely and allows
for a more efficient development cycle (at least with the trial-and-error
approach I often find me using).
So in my experience, `mkoctfile` generally works on Windows.
But if necessary, I am passing flags manually.
I ran across the issue here when I tried to run `pkg install -forge sparsersb`
for another bug. `sparsersb` uses `mkoctfile -p LDFLAGS` in its makefile.

Now that bug #59189 is fixed, I'll try again cross-compiling with the patch
from here.

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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