Changes between Initial Version and Version 1 of Ticket #38561


Ignore:
Timestamp:
Mar 27, 2013, 11:59:14 PM (11 years ago)
Author:
ryandesign (Ryan Carsten Schmidt)
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).

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #38561

    • Property Keywords tiger added; Tiger removed
    • Property Cc ryandesign@… added
    • Property Owner changed from macports-tickets@… to mww@…
  • Ticket #38561 – Description

    initial v1  
    1 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. 
     1Same 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.