|
From: | Mike Miller |
Subject: | [Octave-bug-tracker] [bug #34301] Can't compile oct files using gcc -fvisibility=hidden option |
Date: | Thu, 27 Mar 2014 04:41:23 +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): Severity: 3 - Normal => 1 - Wish Status: None => Need Info Release: 3.2.4 => dev _______________________________________________________ Follow-up Comment #1: This suggested change has no noticable effect on compiling Octave with gcc with a default configure run. Was the suggestion in the report that Octave itself should be able to be built with the -fvisibility=hidden gcc option, or was that meant to suggest that third-party projects could compile with that option and still link properly with the Octave libraries? The gcc wiki page seems to imply that the shared library itself should be built with this option. If that's correct, then that does not currently work for me. Trying to build Octave with -fvisibility=hidden results in many link errors when the octave-cli and octave-gui executables are built. Let me know if I'm doing something wrong. Attached patch is the change I am building with. (file #31054) _______________________________________________________ Additional Item Attachment: File name: visibility.diff Size:0 KB _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?34301> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |