Re: Call for testing: port migrate

this on a MacBook Pro with M1 processor, macOS Sonoma 14.5, Xcode 15.4 and its CLT’s. So, all in all, a very positive experience. Thanks to the MacPorts team! Ciao Franco > On 12 Jun 2024, at 09:46, Franco Vaccari via macports-users > wrote: > > Dear Josh, > > since your mail caugh

Re: Call for testing: port migrate

Dear Josh, since your mail caught me a few minutes after updating from Ventura to Sonoma, and a few seconds before I started to play with MacPorts migration, I felt obliged to give the migrate command a shot… Currently computing dependency order. Will let you know the outcome… Ciao Franco >

Re: best Xcode version for Mojave?

After updating Xcode while keeping the same OS, should one delete and reinstall all MacPorts packages? Thanks Franco > On 13 Jun 2023, at 21:33, Ken Cunningham > wrote: > > > On 2023-06-12, at 7:25 PM, Richard L. Hamilton wrote: > >> "On macOS 10.14, iTerm2 @3.4.19 requires Xcode 11.0 or

Re: After doing selfupdate and sudo port -v -s upgrade outdated, python310 failed to install

The same holds for python311. Happened to me on a virtual machine I use for testing Ventura on Apple Silicon. Looking at the error message(s) in the log I finally was able to compile and install both python310 and python311 by creating symbolic links where the process were expecting to find.

Re: x86_64 version of libncurses

ote: > > In fact, I am using macOS default shell zsh. > >> On 1 Sep2022, at 8:00 AM,Franco Vaccari wrote: >> >> Just one comment. I see in the error message shown in >> >>> dyld[16273]: Library not loaded: '/opt/local/lib/libncurses.6.dylib' >>> Re

Re: x86_64 version of libncurses

Just one comment. I see in the error message shown in > dyld[16273]: Library not loaded: '/opt/local/lib/libncurses.6.dylib' > Referenced from: '/usr/local/bin/bash' So you are neither using the Apple-provided bash nor the MacPorts provided bash, and stuff in /usr/local may interfere with

Re: wgrib2 installation error

Command not found. > MacBook-Pro:~ 41;which wgrib2 > /opt/local/bin/wgrib2 > > > On 5/18/22 9:43 AM, Franco Vaccari wrote: >> Try >> >> sudo port activate libunwind-headers >> >> Ciao >> >> Franco >> >>> On 18 May 2

Re: wgrib2 installation error

Try sudo port activate libunwind-headers Ciao Franco > On 18 May 2022, at 17:31, Tao Zhang wrote: > > Hi, > > When I install wgrib2 into my Macbook pro (10.14.6), I get the following > error. > Does anyone have the same issue? What causes this issue? > How to fix this it? > >

Re: wgrib2 installation error

When I saw this error I just followed the instructions given in the error message and did sudo port -f deactivate libunwind-headers and retried the installation, and it worked. I think I reactivated libunwind-headers after installing gcc10 Ciao Franco > On 18 May 2022, at 17:31, Tao Zhang

Re: macOS 12.3 and /usr/bin/python. Status?

One of the Mac I manage is on 12.3 (M1 processor). I’ve made a fresh MacPorts installation, and installed the usual packages needed for our environment. Must say that we don’t do any Python ourselves there, but several Python packages are installed as dependencies in the process, and all

Re: Processes getting wedged in "U" (uninterruptible wait) state after Security Update 2020-003

May 2020, at 12:09, Greg Earle wrote: > > On 28 May 2020, at 17:56, Franco Vaccari wrote: > >> Since I’ve SIP enabled and no problems, maybe give it a try and enable it… >> Who knows… >> >> And if you use Console app, you can filter by process name or PID to (

Re: Processes getting wedged in "U" (uninterruptible wait) state after Security Update 2020-003

May 2020, at 17:33, Franco Vaccari wrote: > >> I add to my previous description that on my system, SIP is enabled (just >> checked with csrutil status), but maybe turning it off will work… > > I already had SIP disabled before I ever installed Security Update 2020-003 >

Re: Processes getting wedged in "U" (uninterruptible wait) state after Security Update 2020-003

; Usually all these 3rd party packages being updated to 64 bits. > > Hope it helps! > ~pro > > On Thu, May 28, 2020 at 5:10 PM Franco Vaccari wrote: >> >> Hi Greg… >> >> I’m on 10.14.6 and I installed the security update on my MacBook Pro (Retina &

Re: Processes getting wedged in "U" (uninterruptible wait) state after Security Update 2020-003

Hi Greg… I’m on 10.14.6 and I installed the security update on my MacBook Pro (Retina Mid 2012). Didn’t face any problem with MacPorts. I don’t use the same ports you are mentioning, but I’ve just installed htop to give it a try, and here it works. I’m sorry I can’t help more than this, but

Re: Libkdegames in Mojave (was Re: Jigsaw puzzles)

Hi Ian, your second guess was right… I’ve updated High Sierra to Mojave a couple of weeks ago. On my system: ll /System/Library/Frameworks/OpenAL.framework/Versions total 0 drwxr-xr-x 5 root wheel 160 Sep 21 2019 A lrwxr-xr-x 1 root wheel1 Mar 23 19:38 Current -> A and ll

Re: strange SDKs in El Capitan...

If it may help, on my PowerMac running El Cap I find both showing 10.12: [:~]% ls -la /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs total 16 drwxr-xr-x 3 root wheel 136 Dec 16 2017 . drwxr-xr-x 5 root wheel 170 Dec 15 2016 .. drwxr-xr-x 4 root

Re: /opt/local/var/macports/registry/.registry.lock

Check if you have another port command running or stuck, and eventually kill it if you don’t think it should be there. Then retry your install command Franco > On 18 Mar 2020, at 12:47, belanger wrote: > > I am trying to install gcc and gfortran with sudo port install gcc6 +gfortran > and I

Re: cctools fails to install on my 10.7.5

on LLVM 3.1svn) Target: x86_64-apple-darwin11.4.2 Thread model: posix and cctools finally installs properly So problem solved and sorry for the noise… Thanks Ken for the hint! Franco > On 26 Feb 2020, at 22:33, Franco Vaccari wrote: > > A little digging around and the “b” was a

Re: cctools fails to install on my 10.7.5

A little digging around and the “b” was associated to a supplemental update, and that shouldn’t matter much here. And definitely I can’t compile anything there. I’m afraid Xcode update was not as smooth as it should have been. Will look how to clean that... /usr/bin/clang++ -stdlib=libc++

Re: cctools fails to install on my 10.7.5

Here it is: macOS 10.7.5 11G63b Xcode 4.6.3 4H1503 The only difference is the trailing “b” in macOS. I don’t know its meaning, for sure it’s not “b for beta”, as I’ve never played with beta systems. > On 26 Feb 2020, at 19:48, Ken Cunningham > wrote: > > Please confirm: > > $ echo

Re: cctools fails to install on my 10.7.5

Adding to my previous post sudo port install cctools +xcode properly installed cctools. Is this expected, and should be the default variant on 10.7.5? Thanks Franco > On 26 Feb 2020, at 11:29, Franco Vaccari wrote: > > I wanted to make a fresh installation of MacPorts on a iMa

cctools fails to install on my 10.7.5

I wanted to make a fresh installation of MacPorts on a iMac running 10.7.5. What I did: - removed old MacPorts as per guide instructions - removed old Xcode.app from Applications - installed Xcode 4.6.3 and the command line tools - agreed to sudo xcodebuild -licence - sudo xcode-select -switch

Re: Restarting from scratch on Snow Leopard

> On 1 Mar 2019, at 21:10, Ken Cunningham > wrote: > > > On 2019-03-01, at 11:43 AM, Ken Cunningham wrote: > >> But that is what you get when you want to run 2019 software on a 2006 system >> :> > > > So in the end, you now have a whole new system infrastructure installed in >

Re: Restarting from scratch on Snow Leopard

> On 1 Mar 2019, at 21:10, Ken Cunningham > wrote: > > > On 2019-03-01, at 11:43 AM, Ken Cunningham wrote: > >> But that is what you get when you want to run 2019 software on a 2006 system >> :> And some of the Xserves that keep the lab going are even older than that… :-/ I’m trying to

Re: Restarting from scratch on Snow Leopard

> On 27 Feb 2019, at 21:58, Ken Cunningham > wrote: > >> is llvm39 still the one to be used? > > I still use +llvm39 > > $ port -v installed | grep ld64 > ld64 @3_1+universal-ld64_127-ld64_236-ld64_97 (active) platform='darwin 10' > archs='i386 x86_64' date='2018-09-20T16:56:39-0700' >

Re: Restarting from scratch on Snow Leopard

> On 27 Feb 2019, at 21:58, Ken Cunningham > wrote: > >> is llvm39 still the one to be used? > > I still use +llvm39 > > $ port -v installed | grep ld64 > ld64 @3_1+universal-ld64_127-ld64_236-ld64_97 (active) platform='darwin 10' > archs='i386 x86_64' date='2018-09-20T16:56:39-0700' >

Re: Restarting from scratch on Snow Leopard

> On 27 Feb 2019, at 18:04, Ken Cunningham > wrote: > >> So, just to be sure, you are suggesting to follow the path of >> >> < >> https://trac.macports.org/wiki/LibcxxOnOlderSystems >> > >> >> I can certainly retry that, now that I have a more standard Xcode >> installation. >> >>

Re: Restarting from scratch on Snow Leopard

> On 27 Feb 2019, at 16:27, Ken Cunningham > wrote: > > The best way of giving extra lifespan to SL is to make it work like newer > systems as much as possible. All current software for macOS is built and > tested against libc++ using clang. > > The only reason to use libstdc++ is to get

Restarting from scratch on Snow Leopard

I’ve several old iMacs running Snow Leopard, and on one of them I tried to install some extra packages, but that created quite some troubles with failed updates of some dependencies. So I decided to reinstall MacPorts on that iMac, to see if I could get in par with the others, but with

Re: installation failure because can't fetch the file (10.6.8)

Hi Ken, thanks, will look at that Franco > On 19 Jan 2018, at 19:52, Ken Cunningham > wrote: > > > On 2018-01-19, at 10:41 AM, Christopher Jones wrote: > > >>Dload Upload Total SpentLeft Speed >> 0 00 0

Re: installation failure because can't fetch the file (10.6.8)

r similar. > > Please post the complete log, compressed to save space. > > cheers Chris > > On 19/01/18 15:59, Franco Vaccari wrote: >> I’m trying to update MacPorts on some old computers running 10.6.8. I >> decided to go with a fresh installation on a test machine, removing

installation failure because can't fetch the file (10.6.8)

I’m trying to update MacPorts on some old computers running 10.6.8. I decided to go with a fresh installation on a test machine, removing the existing /opt/local, before hopefully do the same on the main server. I successfully installed many of the packages my group use routinely, but with

Lion - All compilers are either blacklisted or unavailable

Hi, I had a working MacPorts installation on a Xserve running Lion (10.7.5, latest OS supported on that machine). I wanted to add some new package and the step "Scanning binaries for linking errors” failed. I couldn’t find a way to pass that step, and in the end I decided to rm -r /opt/local