[MacPorts] #21865: wine-devel doesn't like x86_64

MacPorts noreply at macports.org
Fri Oct 9 23:48:43 PDT 2009


#21865: wine-devel doesn't like x86_64
------------------------------------+---------------------------------------
  Reporter:  Damien@…               |       Owner:  ryandesign@…           
      Type:  defect                 |      Status:  closed                 
  Priority:  Normal                 |   Milestone:                         
 Component:  ports                  |     Version:  1.8.1                  
Resolution:  fixed                  |    Keywords:  x86_64, libexpat       
      Port:  wine-devel             |  
------------------------------------+---------------------------------------
Changes (by ryandesign@…):

  * status:  assigned => closed
  * resolution:  => fixed


Comment:

 Replying to [comment:12 jussi.eskelinen@…]:
 > In case someone has a similar problem: I had to first run sudo port
 install portname and then run sudo port upgrade --enforce-variants
 portname +universal for each package.

 It should be sufficient to initially install the ports with the +universal
 variant; upgrading with --enforce-variants is only necessary if you
 already have the ports installed without +universal. Of course, by the
 time you see wine-devel's message, the dependencies will already have been
 installed with the wrong architectures. Unfortunately it is not possible
 for the wine-devel portfile itself to do anything until its dependencies
 have been installed. A better solution to this could probably be
 implemented in MacPorts base.

 Replying to [comment:13 arno+macports@…]:
 > Would it be a bad idea to make "+universal" a default variant?

 That might be useful starting with Snow Leopard. I
 [http://lists.macosforge.org/pipermail/macports-
 dev/2009-September/009724.html suggested this] on the mailing list and
 have done so on my machine, but this has revealed just how many ports have
 trouble building x86_64/i386 universal, which is quite a lot. So that's
 not a good idea at this time.

 > Or would this be better handled by a mechanism to automatically handle
 such cases by either informing the user that they must rebuild specific
 ports as universal,

 I added advice to rebuild dependencies universal to the archcheck
 portgroup in r59112.

 > or automatically rebuilding the required ports as such?

 That and the above are handled by request #20728.

-- 
Ticket URL: <http://trac.macports.org/ticket/21865#comment:14>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list