Changes between Initial Version and Version 1 of Ticket #47944, comment 2


Ignore:
Timestamp:
Jun 3, 2015, 8:53:25 PM (9 years ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #47944, comment 2

    initial v1  
    1 You would not see this with a normal universal build on a 64-bit Intel machine because it can run all the archs it produces. I see the issue because I'm building on a 32-bit machine. I've also added ppc to the universal_archs which should not be a problem, but I will ultimately want to add ppc64 as well which will be a problem too. You would presumably also see the issue trying to build a normal universal on a PowerPC machine.
     1You would not see this with a normal universal build on a 64-bit Intel machine because it can run all the archs it produces. I see the issue because I'm building on a 32-bit machine. I've also added ppc to the universal_archs which should not be a problem (on Snow Leopard or earlier, because it has Rosetta), but I will ultimately want to add ppc64 as well which will be a problem too. You would presumably also see the issue trying to build a normal universal on a PowerPC machine.
    22
    33Back when muniversal was first introduced Marcus was adding it to ports somewhat at random, for no reason other than muniversal was the new thing and it was thought to be more reliable, but we quickly saw issues with this approach, such as the one I'm bringing up in this ticket. I don't know if muniversal was added to poppler for this (non) reason, or if there was a real reason why the default universal variant didn't work right for poppler, or if so, if that reason still applies with 0.33.0.