Changes between Initial Version and Version 1 of Ticket #65912, comment 3


Ignore:
Timestamp:
Oct 2, 2022, 3:40:54 AM (19 months ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #65912, comment 3

    initial v1  
    33Didn't realize +universal was the default build for ports (clisp?) now - my original command was "sudo port install clisp". 
    44
    5 So far the only commands I have given since installing macports are "sudo port self update" , "sudo port install qemu", "sudo port install xorg-server" and the clisp above. Everything has worked fine except clisp. I also reset the portdbpath to /Volumes/LaCieSilver/MacPorts in macports.conf.
     5So far the only commands I have given since installing macports are `sudo port selfupdate` , `sudo port install qemu`, `sudo port install xorg-server` and the clisp above. Everything has worked fine except clisp. I also reset the portdbpath to /Volumes/LaCieSilver/MacPorts in macports.conf.
    66
    7 Changed /opt/local/etc/variants.conf to include "-universal", did a "sudo port clean --all clisp" and "sudo port clean --all ffcall" and ran:
     7Changed /opt/local/etc/variants.conf to include "-universal", did a `sudo port clean --all clisp` and `sudo port clean --all ffcall` and ran:
    88
     9{{{
    910sudo port install clisp -universal
     11}}}
    1012
    1113I still the the "+universal" build fetch and get the same error (below).  Any idea on how I stop if from trying to do +universal for the port?
    … …  
    1315Thanks.
    1416
     17{{{
    1518% sudo port install clisp -universal
    1619--->  Computing dependencies for clisp
    … …  
    3538Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
    3639Error: Processing of port clisp failed
    37 
     40}}}