[MacPorts] #16666: Update apple-gcc42 to rev 5564 and include c++ support

[MacPorts]

#16666: Update apple-gcc42 to rev 5564 and include c++ support
--------------------------------------------------+-------------------------
 Reporter:  illogical1@…                          |       Owner:  mww@…           
     Type:  defect                                |      Status:  new             
 Priority:  Normal                                |   Milestone:  Port Bugs       
Component:  ports                                 |     Version:  1.6.0           
 Keywords:  apple-gcc42 c++ inline-asm apple gcc  |        Port:  apple-gcc42     
--------------------------------------------------+-------------------------

Comment(by illogic-al@…):

 Replying to [comment:24 ryandesign@…]:
 > Replying to [comment:19 illogic-al@…]:
 > > I have no idea what the changes upstream were made. All I know is bugs
 were fixed and 5564 works better (as in, at all).
 >
 > What I was trying to figure out was why your proposed portfile changes
 the entire port -- changes how it builds, makes it build universal all the
 time, causes it to violate the mtree, no longer appends the customary
 suffix to the binaries -- when your original request was simply to enable
 C++ support and to update to a newer version.
 Because as it states in the portfile, it won't work (for whatever reason).
 Whatever apple's doing

 >
 > I think the universal support you've added is what's causing the port to
 fail to build for me. I'm on Leopard on Intel but my universal_archs
 contains all four architectures (i386 ppc x86_64 ppc64), and with your
 [attachment:Portfile.3 Portfile.3] and [attachment:Portfile.4 Portfile.4]
 I get the message:
 This is not universal support, it is building a compiler which is capable
 of compiling universal code. It creates an x86 code compiler and a ppc
 code compiler (for me as those are the only universal archs I have set).
 As I said above I can just change it back to be "i386 and ppc" which would
 be better than the current option of nothing on 10.4

 >
 > {{{
 > /mp/var/macports/build/_Users_rschmidt_macports_dports_lang_apple-
 gcc42/work/gcc_42-5564/obj-i686-ppc64/./gcc/as: line 2: exec: ppc64: not
 found
 > }}}
 >
 > The full log is [attachment:apple-gcc42.txt.bz2 attached].
 I added x86_64 and ppc64 to my universal section in macports.conf so I'll
 check this out.

 >
 > We should keep in mind that this is not our port. Although the
 maintainer has not responded to this issue within the prescribed 72 hour
 period, we should not take this to mean that we can completely rearrange
 his port.
 >
 > I would like to scale back and make just a few precise changes to the
 portfile, for which I'm attaching patches:
 >
 >  1. [attachment:apple-gcc42-ryandesign-livecheck.diff Change the
 livecheck] to more reliably tell us when the version is out of date.
 Fine by me.

 >  2. [attachment:apple-gcc42-ryandesign-5566.diff Update the version to
 5566] which seems to be the latest now.
 Haven't tested this, why 5566 and not 5564 which we know works?

 >  3. [attachment:apple-gcc42-ryandesign-cxx.diff Enable the C++ and
 Objective C++ languages].
 Did you try this (actively use this compiler) and get it to work (with
 kde).

 >
 > Do these meet your needs? I would be comfortable committing patches 1
 and 2. Patch 3 I'm not comfortable committing without input from the
 maintainer, because the portfile contains a note that enabling C++ causes
 the build to fail, which I was not able to reproduce. So I would first
 like to know under which circumstances or on what machines Marcus observed
 the build to fail with C++ before we go enabling it.
 >
 See previous comment. Ultimately we'd have to ask jm if it meets his
 needs. My needs are already met with xcode 3.1 :-)

-- 
Ticket URL: <http://trac.macports.org/ticket/16666#comment:26>
MacPorts <http://www.macports.org/>
Ports system for Mac OS