[MacPorts] #18187: ncursesw and ncurses universal builds are incorrect

[MacPorts]

#18187: ncursesw and ncurses universal builds are incorrect
------------------------------------+---------------------------------------
  Reporter:  mcalhoun@…             |       Owner:  imajes@…                  
      Type:  defect                 |      Status:  reopened                  
  Priority:  Normal                 |   Milestone:  Port Bugs                 
 Component:  ports                  |     Version:  1.7.0                     
Resolution:                         |    Keywords:  ncursesw ncurses universal
      Port:  ncursesw ncurses       |  
------------------------------------+---------------------------------------

Comment(by mcalhoun@…):

 Replying to [comment:3 ryandesign@…]:
 > At least on a PowerPC Mac. (You end up with just a ppc build.)
 >
 > On an Intel Mac, it also prevents the creation of an
 i386/ppc/x86_64/ppc64 universal build. (You end up with just an
 i386/x86_64 build.)
 This is intentional.[[BR]]
 The configure script must run binaries to work correctly (hence "set
 merger_must_run_binaries yes").[[BR]]
 The muniversal PortGroup often has difficulty merging three architectures
 as it does with ncurses and ncursesw (hence "set merger_no_3_archs yes").

 In the Intel case, if the user has universal_archs set to "ppc i386 ppc64
 x86_64," then the ppc64 can definitely not be built and the PortGroup must
 choose[[BR]]
 two architectures from the remaining valid three.[[BR]]
 It chooses i386 and x86_64.

 What was the value of universal_archs on the PowerPC build?[[BR]]
 The PortGroup would have removed the i386 and x86_64 architectures.

 The two ports used to build using -arch, but, as can be seen in the header
 files, the build were incorrect.[[BR]]
 I figured it was better to build correctly on fewer architectures than
 incorrectly on all architectures.

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