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

[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: anonymous
Subject: [Octave-bug-tracker] [bug #34301] Can't compile oct files using gcc -fvisibility=hidden option
Date: Thu, 15 Sep 2011 21:19:47 +0000
User-agent: Mozilla/5.0 (X11; Linux i686; rv:6.0.2) Gecko/20100101 Firefox/6.0.2

URL:
  <http://savannah.gnu.org/bugs/?34301>

                 Summary: Can't compile oct files using gcc
-fvisibility=hidden option
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Thu 15 Sep 2011 21:19:46 UTC
                Category: Configuration and Build System
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Feature Request
                  Status: None
             Assigned to: None
         Originator Name: Andrew Ross
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 3.2.4
        Operating System: GNU/Linux

    _______________________________________________________

Details:


The OCTAVE_EXPORT macro defined in oct-dlldefs.h is empty on gcc. Defining it
for gcc using 

#define OCTAVE_EXPORT __attribute__ ((visibility ("default")))

will allow oct code to be compiled using the gcc -fvisibility=hidden option,
which by default does not export any symbols. See
http://gcc.gnu.org/wiki/Visibility for a brief overview of why this is a good
idea.

This bug report originates from work on the octave bindings for plplot using
swig. The relevant thread showing the discussion and our temporary workaround
is
http://www.mail-archive.com/address@hidden/msg04950.html

Regards

Andrew




    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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