Changes between Initial Version and Version 1 of Ticket #65912, comment 3
- Timestamp:
- Oct 2, 2022, 3:40:54 AM (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #65912, comment 3
initial v1 3 3 Didn't realize +universal was the default build for ports (clisp?) now - my original command was "sudo port install clisp". 4 4 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.5 So 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. 6 6 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: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: 8 8 9 {{{ 9 10 sudo port install clisp -universal 11 }}} 10 12 11 13 I 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? … … 13 15 Thanks. 14 16 17 {{{ 15 18 % sudo port install clisp -universal 16 19 ---> Computing dependencies for clisp … … 35 38 Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. 36 39 Error: Processing of port clisp failed 37 40 }}}