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

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

[Octave-bug-tracker] [bug #54260] mkoctfile doesn't export some Octave f


From: John Donoghue
Subject: [Octave-bug-tracker] [bug #54260] mkoctfile doesn't export some Octave features that packages need at build time
Date: Fri, 6 Jul 2018 14:10:47 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Edge/16.16299

Follow-up Comment #1, bug #54260 (project octave):

LOCALVERFCNFILEDIR, LOCALVEROCTFILEDIR, LOCALVERARCHLIBDIR are artifacts of
the old configure/make file that felt the need to show where things were
gooing to be installed, but arent needed.


gsl is doing a temporaty set of CPPFLAGS=-I so that the configure's
AC_CHECK_HEADER will work


just out of interest, what is/was the intent of octave-config? or is that tool
going to disappear over time ? 

or do some things that are direct build settings need be in mkoctfile, others
that are more of just how octave was configured?

Perhaps there needs to also be more spearation between octave-config and
mkoctfile ?


My vote at the very least is not to use octave for compile options

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?54260>

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




reply via email to

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