failure to get gcc9 running

Chris Jones jonesc at hep.phy.cam.ac.uk
Tue Nov 5 13:06:30 UTC 2019


Hi,

On 05/11/2019 12:28 pm, Hans Goedbloed wrote:
> 
> Hi Peter, Ryan and Chris
> 
> Thanks for your help.
> 
> Reply to Chris Jones:
> -- I am not sure that I removed all ports, how can I find out?
> -- How do I create an empty vanilla MacPorts installation?
> By 'port -u uninstall'?

Follow

<https://guide.macports.org/chunked/installing.macports.uninstalling.html>

Once you have done that, just follow the usual instructions to install 
MacPorts from scratch.

> I am inclined to just start afresh, but I am very interested in all of your suggestions, since I have another iMac to go (from 2014), that has been upgraded to macOS 10.14 with the old port files on it (I never upgraded ports since all was working fine, until the recent upgrde to 10.14).

Whenever you upgrade your OS it is *mandatory* that you follow the 
migration guide

<https://trac.macports.org/wiki/Migration>

Not following that, precisely (which yes means uninstalling all ports 
and reinstalling them once upgraded), is a very good way to end up with 
the troubles you are having here.

Another bit of advice - *never* updating your ports after you install 
them is also not at all recommended, as it is also a good way to end up 
with troubles as when you do the updates are a lot bigger and more 
problematic the longer the time period since the last update. I 
recommend periodically running

 > sudo port sync
 > sudo port upgrade outdated

and

 > sudo port selfupdate

to keep your ports in good health.

Chris

> 
> Thanks in advance,
> Hans
> 
> 
> 
> 
> ________________________________________
> From: Ryan Schmidt <ryandesign at macports.org>
> Sent: Monday, November 4, 2019 7:49 PM
> To: Hans Goedbloed
> Cc: MacPorts Users
> Subject: Re: failure to get gcc9 running
> 
> 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