failure to get gcc9 running

Ryan Schmidt ryandesign at macports.org
Mon Nov 4 18:49:23 UTC 2019



On Nov 4, 2019, at 10:12, Hans Goedbloed wrote:
​
> [/Users/hansgoedbloed]$sudo port install gcc9
> Password:
> ---> Computing dependencies for gcc9
> ---> Cleaning gcc9

First things first: this shows that gcc9 was already successfully installed before you ran this command.


> ---> Updating database of binaries
> ---> Scanning binaries for linking errors
> ---> Found 9 broken files, matching files to ports
> ---> Found 4 broken ports, determining rebuild order
> You can always run 'port rev-upgrade' again to fix errors.
> The following ports will be rebuilt:
>  cmake @3.15.5
>  readline @8.0.000
>  gdbm @1.18.1
>  llvm-8.0 @8.0.1
> Continue? [Y/n]: y


After any port install or upgrade, MacPorts checks all installed ports for linking errors. It found some on your system. We would need to see the output of "sudo port -d rev-upgrade" to know specifically what problems were found with those ports.


> Warning: No port perl5.8 found in the index.

perl5.8 was removed a long time ago. The current version is perl5.30. Nothing in MacPorts should be referencing perl5.8 anymore. (I found one port that was; I filed a ticket: https://trac.macports.org/ticket/59600)

Do you perhaps have any local Portfiles (check your /opt/local/etc/macports/sources.conf file) that might be very old and out of date?


> Warning: The macOS 10.14 SDK does not appear to be installed. Ports may not build correctly.
> Warning: You can install it as part of the Xcode Command Line Tools package by running `xcode-select --install'.

I see below that you did run this command. Good.


> ---> Computing dependencies for cmake
> ---> Fetching distfiles for cmake
> ---> Attempting to fetch cmake-3.15.5.tar.gz from https://distfiles.macports.org/cmake
> ---> Verifying checksums for cmake                                             
> ---> Extracting cmake
> ---> Applying patches to cmake
> ---> Configuring cmake
> ---> Building cmake
> ---> Staging cmake into destroot
> ---> Deactivating cmake @3.15.5_0
> ---> Cleaning cmake
> ---> Uninstalling cmake @3.15.5_0
> ---> Cleaning cmake
> Warning: The macOS 10.14 SDK does not appear to be installed. Ports may not build correctly.
> Warning: You can install it as part of the Xcode Command Line Tools package by running `xcode-select --install'.
> ---> Computing dependencies for cmake
> ---> Installing cmake @3.15.5_0
> ---> Activating cmake @3.15.5_0
> ---> Cleaning cmake
> Warning: The macOS 10.14 SDK does not appear to be installed. Ports may not build correctly.
> Warning: You can install it as part of the Xcode Command Line Tools package by running `xcode-select --install'.
> ---> Computing dependencies for readline
> ---> Fetching distfiles for readline
> ---> Attempting to fetch readline-8.0.tar.gz from https://distfiles.macports.org/readline
> ---> Verifying checksums for readline
> ---> Extracting readline
> ---> Applying patches to readline
> ---> Configuring readline
> ---> Building readline
> ---> Staging readline into destroot
> ---> Unable to uninstall readline @8.0.000_0, the following ports depend on it:
> --->       gdbm @1.18.1_1
> Warning: Uninstall forced.  Proceeding despite dependencies.
> ---> Deactivating readline @8.0.000_0
> ---> Cleaning readline
> ---> Uninstalling readline @8.0.000_0
> ---> Cleaning readline
> Warning: The macOS 10.14 SDK does not appear to be installed. Ports may not build correctly.
> Warning: You can install it as part of the Xcode Command Line Tools package by running `xcode-select --install'.
> ---> Computing dependencies for readline
> ---> Installing readline @8.0.000_0
> ---> Activating readline @8.0.000_0
> ---> Cleaning readline

Whatever the problem with cmake and readline was, MacPorts successfully rebuilt them so they are no longer broken.


> ---> Computing dependencies for gdbm
> ---> Fetching distfiles for gdbm
> ---> Attempting to fetch gdbm-1.18.1.tar.gz from https://distfiles.macports.org/gdbm
> ---> Verifying checksums for gdbm
> ---> Extracting gdbm
> ---> Applying patches to gdbm
> ---> Configuring gdbm
> Error: Failed to configure gdbm, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_gdbm/gdbm/work/gdbm-1.18.1/config.log
> Error: Failed to configure gdbm: configure failure: command execution failed
> Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_gdbm/gdbm/main.log for details.

We would need to see the contents of those two logfiles to know why this failed and what to do about it.


> Was it a mistake to upgrade to macOS 1014 for this MacBook?

As far as MacPorts goes, it should work fine.



More information about the macports-users mailing list