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

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

[Octave-bug-tracker] [bug #55033] mkoctfile link failure on macos


From: Rik
Subject: [Octave-bug-tracker] [bug #55033] mkoctfile link failure on macos
Date: Tue, 1 Jan 2019 11:03:45 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko

Update of bug #55033 (project octave):

                  Status:               Need Info => Patch Reviewed         

    _______________________________________________________

Follow-up Comment #20:

@Ben: I don't have any problems wit the diff you submitted so why don't you
turn it in to a full changeset.

As for where to place linker options like "-Ldirectory", I think I would defer
to Mike on that.  The command in mkoctfile.in.cc is


      std::string cmd
        = (vars["DL_LD"] + ' ' + vars["ALL_CXXFLAGS"] + ' '
           + vars["DL_LDFLAGS"] + ' ' + pass_on_options
           + " -o " + octfile + ' ' + objfiles + ' ' + libfiles + ' '
           + ldflags + ' ' + vars["LFLAGS"] + ' ' + octave_libs + ' '
           + vars["OCT_LINK_OPTS"] + ' ' + vars["OCT_LINK_DEPS"]);


If this is known at configure time it could go in to the variable
OCT_LINK_OPTS.

Alternatively, it could go into a regular shell environment variable LFLAGS.

The naming convention of LFLAGS (which are really for lex flags) rather than
using the stand LDFLAGS is already the subject of bug report #48678.


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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