#25149 closed defect (invalid)
MacPorts could exit with an error message if trying to build 64 bits on a 32 bit only machine
Reported by: | scott@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | base | Version: | 1.8.2 |
Keywords: | universal, 32, 64, universal_archs | Cc: | ryandesign (Ryan Carsten Schmidt) |
Port: |
Description
It is possible in MacPorts to issue +universal on a CPU that only supports 32 bit builds. This build will fail.
Macports could potentially benefit the user experience by generating an error when the user tries to perform a 64 bit build on a CPU that only supports 32 bit builds.
Please references this thread in the mailing list for more details: http://lists.macosforge.org/pipermail/macports-users/2010-June/020370.html
Change History (3)
comment:1 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
comment:2 Changed 14 years ago by jmroot (Joshua Root)
Resolution: | → invalid |
---|---|
Status: | new → closed |
The build will not usually fail, and we should do what the user asked us to do.
comment:3 Changed 14 years ago by scott@…
I am confused.
and we should do what the user asked us to do
Are you stating that MacPorts should do as the trac ticket poster suggested? If so, which is how I am reading the comment, why was this ticket closed as invalid? I was asked by Ryan to create this ticket, which is why I did so.
When I am an end user of MacPorts, and I believe I am just a very small hair above the average "drive-by download and install MacPorts" kind of users. The error I was receiving, and what the ending explanation was, was not something I understood right off the bat. And again, I do feel I am marginally more familiar with MacPorts that a new user. I think that bailing out with some kind of explanation would be a "Good Thing".
Did I miss out on something here? Thanks everyone.
Having this would have prevented tickets like #25031.