[MacPorts] #34603: ace: use the right compiler and -arch flags

[MacPorts]

#34603: ace: use the right compiler and -arch flags
-------------------------------------+--------------------------------------
 Reporter:  ryandesign@…             |       Owner:  lockhart@…            
     Type:  defect                   |      Status:  new                   
 Priority:  Normal                   |   Milestone:                        
Component:  ports                    |     Version:  2.1.1                 
 Keywords:                           |        Port:  ace                   
-------------------------------------+--------------------------------------

Comment(by ryandesign@…):

 Replying to [comment:6 lockhart@…]:
 > Replying to [comment:5 lockhart@…]:
 > > Replying to [comment:4 ryandesign@…]:
 > > > This build system of theirs isn't specifying any particular compiler
 though. It's just using "g++" and that's the problem...
 >
 > So to clarify: this is a problem even though that is
 WhatTheBuildersIntended?

 Yes, it's still a problem. The developers of a program often are not aware
 of the considerations a package management system like MacPorts considers
 important. Using "g++" when you don't know what that is means different
 users might get subtly different builds of the software, or might even
 encounter build failures if they happen to have a completely broken build
 of a compiler installed. Better to lock that down to a specific known-good
 compiler, the one identified by the MacPorts variable ${configure.cxx}.
 These guidelines have come into effect after years of actual users
 actually encountering this type of problem; following these guidelines
 should thus end up decreasing the problems users encounter, and thus
 decreasing the tickets you (and we) have to respond to.

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