#1255: fix PARROT_EXPORT visibility=default for gcc other than 4.x
-----------------------+----------------------------------------------------
Reporter: jkeenan | Owner:
Type: patch | Status: new
Priority: normal | Milestone:
Component: configure | Version: 1.7.0
Severity: medium | Keywords:
Lang: | Patch: new
Platform: |
-----------------------+----------------------------------------------------
Description changed by coke:
Old description:
> This ticket transfers into Trac an issue originally discussed in the Trac
> system at [http://rt.perl.org/rt3/Ticket/Display.html?id=62010 RT
> #62010].
>
> In that ticket, Donald Hunter said:
>
> ''"This patch fixes a problem with gcc 3.4.6 on Linux where
> -fvisibility=hidden is detected as supported but
> __attribute__((visibility("default"))) is not used for PARROT_EXPORT. The
> setting for export visibility was hard-coded for gcc > 4.0 so I changed
> it to be a new test based on the detection of support for
> -fvisibility=hidden''
>
> ''"I created a new file for the config step because it has to happen
> after config/auto/warnings.pm and there's no other relevant file to put
> it in."''
>
> However, a number of Parrot developers (including myself) were skeptical
> of the need for a new configuration step as proposed in that RT.
> Discussion was inconclusive.
>
> infinoid, can you take this ticket?
>
> Thank you very much.
>
> kid51
New description:
This ticket transfers into Trac an issue originally discussed in the RT
system at [http://rt.perl.org/rt3/Ticket/Display.html?id=62010 RT #62010].
In that ticket, Donald Hunter said:
''"This patch fixes a problem with gcc 3.4.6 on Linux where
-fvisibility=hidden is detected as supported but
__attribute__((visibility("default"))) is not used for PARROT_EXPORT. The
setting for export visibility was hard-coded for gcc > 4.0 so I changed it
to be a new test based on the detection of support for
-fvisibility=hidden''
''"I created a new file for the config step because it has to happen after
config/auto/warnings.pm and there's no other relevant file to put it
in."''
However, a number of Parrot developers (including myself) were skeptical
of the need for a new configuration step as proposed in that RT.
Discussion was inconclusive.
infinoid, can you take this ticket?
Thank you very much.
kid51
--
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1255#comment:1>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
