[MacPorts] #38561: openssl @1.0.1_1 build failure on Tiger (again) no-asm for Dawin 8?

[MacPorts]

#38561: openssl @1.0.1_1 build failure on Tiger (again) no-asm for Dawin 8?
---------------------------+-------------------
  Reporter:  strombland@…  |      Owner:  mww@…
      Type:  defect        |     Status:  new
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.1.3
Resolution:                |   Keywords:  tiger
      Port:  openssl       |
---------------------------+-------------------
Changes (by ryandesign@…):

 * keywords:  Tiger => tiger
 * cc: ryandesign@… (added)
 * owner:  macports-tickets@… => mww@…


Old description:

> Same build failure encountered on OS 10.4 Tiger as reported in ticket
> #33741, https://trac.macports.org/ticket/33741.  Changing the default
> compiler to apple-gcc-4.2 as suggested in the last line of ticket #33741
> also resulted in a build failure.  I am using Xcode version 2.5 and
> running OS 10.4.11 Tiger.

New description:

 Same build failure encountered on OS 10.4 Tiger as reported in ticket
 #33741.  Changing the default compiler to apple-gcc-4.2 as suggested in
 the last line of ticket #33741 also resulted in a build failure.  I am
 using Xcode version 2.5 and running OS 10.4.11 Tiger.

--

Comment:

 See #38015 for why we re-enabled asm, and see comment:ticket:38015:40
 where I tested all systems I had access to and verified that they worked
 with and without asm, except for the few new model Mountain Lion systems
 that were experiencing the bug in that ticket, which required asm to be
 on. I did not have a Tiger i386 test machine set up however so I did not
 test that. And my testing was with 1.0.1d, and you're now using 1.0.1e.
 #33741 was with 1.0.1. The assembly code no doubt changes with each
 release.

 Which specific Intel Mac model do you have? Any particular reason you're
 still running Tiger on it? All Intel Macs can be upgraded to at least Snow
 Leopard, which I feel is a better OS in most every way, and by upgrading
 you should encounter fewer problems building ports (though I can't
 guarantee that would resolve this particular issue).

-- 
Ticket URL: <https://trac.macports.org/ticket/38561#comment:1>
MacPorts <http://www.macports.org/>
Ports system for OS X