[Top][All Lists]

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

[Octave-bug-tracker] [bug #53627] build: oct files should not need to li

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #53627] build: oct files should not need to link with -loctinterp -loctave
Date: Thu, 12 Apr 2018 14:52:17 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0


                 Summary: build: oct files should not need to link with
-loctinterp -loctave
                 Project: GNU Octave
            Submitted by: mtmiller
            Submitted on: Thu 12 Apr 2018 11:52:15 AM PDT
                Category: Configuration and Build System
                Severity: 2 - Minor
                Priority: 5 - Normal
              Item Group: Feature Request
                  Status: Postponed
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux



This applies equally to the .oct files that are built as part of Octave, as
well as the mkoctfile rules for building external .oct files.

On GNU/Linux, a shared object that is a plugin or loadable module doesn't need
to link with the base libraries of the program that is loading it. Since
Octave is doing the loading, all .oct files will have access to the functions
in Octave's executable image.

I propose that we drop DLD_LIBOCTINTERP_LIBADD and remove both liboctinterp.la
and liboctave.la from the LIBADD of each of the .oct files built in
libinterp/dldfcn. I also propose that "-loctinterp -loctave" be removed from
the mkoctfile build command.

But this will definitely need some testing on macOS and Windows to see whether
this is safe or needs to be made conditional.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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