Opened 13 years ago

Closed 12 years ago

#28932 closed defect (fixed)

gcc 4.6 should have a fix "-fwritable-strings not compatible with literal CF/NSString"

Reported by: anatol (Anatol Pomozov) Owned by: mww@…
Priority: Normal Milestone:
Component: ports Version: 1.9.2
Keywords: Cc:
Port: gcc46

Description

Now, when gcc 4.6 is out and it is clear that it will not have a fix for "-fwritable-strings not compatible with literal CF/NSString" issue.

See the description of the problem and a testcase for it here http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47997.

GCC team has provided several possible patches for it, but did not include it to 4.6 release as it was too late to do it. I believe macports should add this patch.

Change History (5)

comment:1 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)

Owner: changed from macports-tickets@… to mww@…

gcc46 should also be updated to the latest version of gcc 4.6.

comment:2 Changed 13 years ago by anatol (Anatol Pomozov)

More information: I have 10.6.4 macosx. The warning is reproducible on the current gcc46 port. So the patch is applicable only for gcc46.

gcc from xcode is too outdated and does not contains few features that I need (e.g. thread local variables) so I looked for gcc42 alternatives. I tried gcc45 from macports and I found that it is unusable for macosx development - it is not possible to compile a program that uses Core framework. From other side GCC 4.6 is *very* usable. I use it for development now - and everything looks fine.

It is possible to use gcc46 without the patch provided by gcc team - but it might confuse people who tries to use it. I would prefer to have the patch included to macports (assuming that it does not introduce any other bugs).

comment:3 Changed 13 years ago by mf2k (Frank Schima)

Port: gcc46 added; gcc removed

comment:4 Changed 13 years ago by Veence (Vincent)

This apparently has been fixed in 4.6.1

comment:5 Changed 12 years ago by jmroot (Joshua Root)

Resolution: fixed
Status: newclosed

Closing as per comment:4.

Note: See TracTickets for help on using tickets.