Re: [EXTERNAL] Re: Library libtdbc used in restore_ports script is unsigned

Thanks, Josh, for the workaround. Using “sudo `readlink /opt/local/bin/port-tclsh` ./restore_ports.tcl” worked great. ++Eric The most straightforward workaround is to use a different path for the interpreter. /opt/local/bin/port-tclsh is a symlink to the actual tclsh8.6 in a subdirectory, so

Library libtdbc used in restore_ports script is unsigned

I recently upgraded from macOS 13.x to macOS 14.3.1 Sonoma and started running the MacPorts Migration process. I got interrupted and did the minor macOS update to macOS 14.4 and tried to run the “restore_ports.tcl” script, which worked for a while but then threw an error about the libtdbc

What is "ghc" and why was it installed?

I was running “port selfupdate” and “port upgrade outdated” for the first time in a while, and I noticed that my Intel MacBook Pro was spending almost an hour compiling a port called “ghc” that I don’t remember seeing before and I am sure I did not request. Is this part of something else that

Re: [EXTERNAL] Re: Scanning binaries segfault

Thanks again. Re-installing the MacPorts binary from the .pkg fixed my Segmentation Fault problem. My employer has various tools they use to change things on our Macs, and maybe one of those broke the "port rev-upgrade" function in some way. It is great that the fix was easy. ++Eric

Re: [EXTERNAL] Re: Scanning binaries segfault

Thanks for the suggestion. I have been on Catalina for 4 months. It is possible that my employer upgraded something that I did not know about with their access. I will check SDK. Sent from my iPhone ++Eric > On Apr 25, 2021, at 20:58, Joshua Root wrote: > > Fielding, Eric J wrote: >>

Scanning binaries segfault

I was running a `port upgrade outdated` (actually I had to add `and not py37-scipy` as that was not building), and when it finished upgrading ports, it started the usual “Scanning binaries for linking errors”. This step is crashing with a “Segmentation fault” after about 30%. Does this mean my

Warning: cltversion again

I am getting this warning again from running ‘port upgrade outdated’: Warning: cltversion: The Command Line Tools are installed, but MacPorts cannot determine the version. Warning: cltversion: For a possible fix, please see: https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt I

Re: Catalina xcode-select --install and MacPorts installation

Thanks. Maybe there is something about the mobile device management setup my employer uses that changes how the installations work. On 10/29/20, 03:44, "Ryan Schmidt" wrote: On Oct 28, 2020, at 02:31, Fielding, Eric J (US 329A) wrote: > I just upgraded my MacBook to Catalina

Re: Xcode 11.2 on Mojave and gcc7 or gcc9

Chris, Thanks for the hints. I did the suggested method of forcing the Command-Line Tools installation by Software Update and it told me that it was going to install the Xcode 10.3 CLT. It seems that Xcode 11 now has the CLT included inside Xcode, so that version is not installed by Software

Xcode 11.2 on Mojave and gcc7 or gcc9

My employer automatically installs the latest versions of MacOS software, including now Xcode 11.2. I have been seeing several suggestions that we should go back to Xcode 10.3, which I tried a few weeks ago when I was on Xcode 11.1. That was OK and all my ports were working until they upgraded

MacPorts and Anaconda

I saw the discussion the last few days about the problems with using both HomeBrew and MacPorts on the same system. I was wondering about problems with using MacPorts and Anaconda to install different packages. I have been using MacPorts for a long time with few problems, but sometimes I need