[MacPorts] #67509: Building lame on Tiger fails as the SDK name is incorrect

[MacPorts]

#67509: Building lame on Tiger fails as the SDK name is incorrect
----------------------+--------------------------
  Reporter:  RealKGB  |      Owner:  barracuda156
      Type:  defect   |     Status:  assigned
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:  2.8.1
Resolution:           |   Keywords:  tiger
      Port:  lame     |
----------------------+--------------------------

Comment (by barracuda156):

 Replying to [comment:9 kencu]:
 > Replying to [comment:6 barracuda156]:
 > > Replying to [comment:3 kencu]:
 > > > also not all ppc systems support altivec, so that should be fixed
 too
 > >
 > > Should we disable optimizations for Tiger or how to handle it
 correctly?
 >
 > disabling altivec on Tiger is the easy way out, but then is not quite
 right for Tiger systems that do have altivec…
 >
 > testing for altivec during the build and enabling it if present is kinda
 better, but then breaks the prebuilt binaries from the buildbots if the
 buildbot supports altivec but the user does not.
 >
 > testing for altivec during the build and enabling it if present, and
 also disabling prebuilt binaries for the port, works, but people will
 complain about no prebuilt binaries someday perhaps.  As we will probably
 never have a Tiger builbot anyway, this is what we usually do.
 >
 > building it both with and without altivec and determining “on the fly”
 if the machine can use altivec is really the way to go, but almost nobody
 knows how to properly do that :)

 For 10.5, we can assume that no one gonna install it on a G3?

-- 
Ticket URL: <https://trac.macports.org/ticket/67509#comment:10>
MacPorts <https://www.macports.org/>
Ports system for macOS