#32196: MacPorts_Framework: parse error before ‘NSUInteger’ ---------------------------------+------------------------------------------ Reporter: rudloff@… | Owner: juanger@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: tiger | Port: MacPorts_Framework ---------------------------------+------------------------------------------ Changes (by ryandesign@…): * owner: macports-tickets@… => juanger@… * cc: juanger@… (removed) * cc: ryandesign@… (added) Comment: 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. -- Ticket URL: <https://trac.macports.org/ticket/32196#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS

#32196: MacPorts_Framework: parse error before ‘NSUInteger’ ----------------------------------+----------------------------------------- Reporter: rudloff@… | Owner: juanger@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Resolution: wontfix | Keywords: tiger Port: MacPorts_Framework | ----------------------------------+----------------------------------------- Changes (by ryandesign@…): * status: new => closed * resolution: => wontfix Comment: 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. -- Ticket URL: <https://trac.macports.org/ticket/32196#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS