Ticket #32715 (closed defect: fixed)
mailx doesn't build for the right architectures
| Reported by: | ryandesign@… | Owned by: | toby@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.0.3 |
| Keywords: | Cc: | cal@… | |
| Port: | mailx |
Description
See summary.
Change History
comment:3 Changed 15 months ago by toby@…
arch flags used to be in configure.cflags, I haven't gotten around to working around it. It's not particularly important for things that don't provide libraries, anyway.
comment:4 Changed 15 months ago by toby@…
- Status changed from assigned to closed
- Resolution set to wontfix
Actually this is wontfix, see Mountain Lion for details (if you have access).
comment:5 Changed 15 months ago by ryandesign@…
- Status changed from closed to reopened
- Resolution wontfix deleted
At the moment, MacPorts supports Snow Leopard and Lion, and some users still use Leopard and Tiger. And on all those systems, we want to use the right archs. If you have something to say about the future of OS X and its impact on MacPorts, feel free to bring that up on the mailing list.
comment:6 Changed 15 months ago by toby@…
- Status changed from reopened to closed
- Resolution set to wontfix
Regardless, there's no need for command line tools to be built fat.
comment:7 Changed 15 months ago by ryandesign@…
- Status changed from closed to reopened
- Resolution wontfix deleted
mailx has a universal variant, but it does not build universal. Either the universal variant should build universal, or it should be turned off. But it's not just universal binaries; it's also building for the right single architecture when the user has requested a nonstandard one by changing build_arch in macports.conf. If the user has done this, mailx might fail to build, because although its (undeclared) dependencies would have been built for the requested architecture, mailx itself would not.
Since it's a simple fix I've fixed it in r90369.
Used to work until the base change that screwed up configure.cflags