OpenSSH 9.7p1 fails to build due to outdated /opt/local/include/launch.h missing launch_activate_socket

[badger200]

I simply renamed /opt/local/include/launch.h and the port then built successfully. I’m not sure why there’s an old launch.h from 2005 there?

macOS Catalina 10.15.7 x86_64 SDK 10.15

[ryandesign (Ryan Carsten Schmidt)]

You tell us. What does port provides /opt/local/include/launch.h say? I searched the database on ​https://ports.macports.org and it has no record of that file.

[badger200]

I just upgraded from 10.9 to 10.15, I did the entire port migration procedure.

I looked at the inodes in /opt/local/include/ and the other entry with very close inode is LegacySupport folder. I’m not sure if it’s some remnant from 10.9 LegacySupport.

Port provides says no port owns that launch.h. So I guess this can be closed. There has to be some reason why OpenSSH 9.7p1 binaries weren’t available though which led to me building from source in the first place. Unless I just happened to update ports right after a new release and before the servers had 10.15 binaries built?

[ryandesign (Ryan Carsten Schmidt)]

legacy-support is a port like any other. Its files would be identified as belonging to it.

I searched the macports-legacy-support repository and found no matches for launch.h. legacy-support was originally called snowleopardfixes and it wasn't added to MacPorts until 2017 so any files installed by it shouldn't have had a modification date in 2005.

Yes, you should remove launch.h and probably any other headers or libraries you find in /opt/local/include and /opt/local/lib that cannot be matched with a port. But components installed by MacPorts base, including the /opt/local/bin/port command, are also identified as not belonging to any port, so cleanup in /opt/local/bin and /opt/local/var needs to be done more carefully.

There have been many updates to several llvm ports recently, each of which take hours or days to build. As a result, the build servers have a large backlog at the moment.