Bug 198967
Summary: | new C++ visibility doesn't work as expected | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bill Nottingham <notting> |
Component: | gcc | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | bkoz, caolanm, jason, rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-09-22 16:49:16 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Bill Nottingham
2006-07-15 03:35:08 UTC
Erm, assume there's a #include <string> in there. :) It still errors... I thought libstdc++ (particularly bits/c++config) already uses __attribute__((visibility ("default"))) on the std namespace (and similar namespaces), but apparently it doesn't. This isn't anything new BTW, it has never been there so far and thus code without default visibility around the standard headers has always been broken. Ok, then rather than munge all the #include statements in the package, I can turn off the visibility flag for the build for now. Any chance that at least libstdc++ could be fixed to have proper visiblity in the headers? GCC 4.3 will have that, but for 4.1 such changes are IMHO way too invasive. |