[MacPorts] #18187: ncursesw and ncurses universal builds are incorrect
MacPorts
noreply at macports.org
Wed Feb 11 15:02:38 PST 2009
#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:6 ryandesign@…]:
> Replying to [comment:4 mcalhoun@…]:
> > What was the value of universal_archs on the PowerPC build?[[BR]]
> The default, i386 ppc.
> > The PortGroup would have removed the i386 and x86_64 architectures.
> Yes, it did.
So it seems that at least the PortGroup is behaving as intended (cold
comfort for some).
> > 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.
> But it is better still to build correctly for all four architectures. :)
Touche.[[BR]]
Any ideas on how to accomplish such a thing?
Personally, I would not object to allowing Intel/PowerPC universal to fade
away.[[BR]]
The concept has always had a difficult time fitting in with the MacPorts
model of "download, compile, and run."
I do not think the maintainer of these ports has weighed in on this issue.
--
Ticket URL: <http://trac.macports.org/ticket/18187#comment:7>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list