[Top][All Lists]

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

[Octave-bug-tracker] [bug #34301] Can't compile oct files using gcc -fvi

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #34301] Can't compile oct files using gcc -fvisibility=hidden option
Date: Thu, 27 Mar 2014 23:43:31 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.152 Safari/537.36

Update of bug #34301 (project octave):

                Priority:              5 - Normal => 3 - Low                


Follow-up Comment #2:

Still unable to compile Octave itself with -fvisibility=hidden, fixed the
patch to the following:

diff --git a/oct-conf-post.in.h b/oct-conf-post.in.h
--- a/oct-conf-post.in.h
+++ b/oct-conf-post.in.h
@@ -121,6 +121,14 @@
 #if defined (_MSC_VER)
 #define OCTAVE_EXPORT __declspec(dllexport)
 #define OCTAVE_IMPORT __declspec(dllimport)
+#elif defined (__GNUC__)
+#if (__GNUC__ >= 4)
+#define OCTAVE_EXPORT __attribute__ ((visibility ("default")))
+#define OCTAVE_IMPORT __attribute__ ((visibility ("default")))
 /* All other compilers, at least for now. */

With a default build of Octave, there is no change, everything works as it
used to. So I just want to understand better what this change is actually
supposed to help with, is Octave supposed to be able to be built with hidden
symbols, or is it only for the benefit of external packages that are linking
against the Octave libraries (that still expose the full set of library
symbols in their dynamic symbol table)?


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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