Opened 13 years ago
Closed 12 years ago
#32196 closed defect (wontfix)
MacPorts_Framework: parse error before ‘NSUInteger’
| Reported by: | rudloff@… | Owned by: | juanger@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.0.3 |
| Keywords: | tiger | Cc: | armahg@…, ryandesign (Ryan Carsten Schmidt) |
| Port: | MacPorts_Framework |
Description
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_MacPorts_Framework/MacPorts_Framework/work/MacPorts_Framework/MPMacPorts.m:118: error: parse error before ‘NSUInteger’
Does this mean that it can't be built on Tiger ?
If so, it should produce a nicer error.
Attachments (1)
Change History (4)
comment:1 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… added; juanger@… removed |
|---|---|
| Owner: | changed from macports-tickets@… to juanger@… |
| Summary: | MacPorts_Framework: Build error on Tiger → MacPorts_Framework: parse error before ‘NSUInteger’ |
Changed 13 years ago by rudloff@…
comment:3 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Since nobody appears to be working on making MacPorts_Framework Tiger-compatible, I've marked the port as requiring Leopard or greater in r94034. This is not a big problem anyway since Pallet, the only port using MacPorts_Framework, is already marked that way.
Note: See
TracTickets for help on using
tickets.
This is not a complete log. (You did not clean before building.) However, it's enough to see that yes, this won't work on Tiger; NSInteger / NSUInteger was introduced in Leopard. This can probably be worked around by defining these to the appropriate int type, but there may be other Tiger-incompatible code; for example #27722 was filed last year about a different error on Tiger.