failure to get gcc9 running

Hans Goedbloed J.P.Goedbloed at differ.nl
Tue Nov 5 12:28:33 UTC 2019


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'?


To Ryan Schmidt:
-- (1) Attached is "1a. output of upgrade" and "1b. plist". I can not make anything of it. 
-- (2) I see some perl file dating from 2010 in /opt/local/bin (see attached "2. old perl files").How to update "libpreludedb's +perl variant"?
-- (3) Attached is the list of the "3. old local portfiles". In fact, they date from 2014, but they also have a copy labeled ".default". Should I just delete all of them?
-- (4) Attached are the two gdbm Error logfiles ("4a. gdbm error main logfile" and "4b. gdbm error config logfile" and). Frankly, I am not able to distill a procedure to follow from them.

To Peter Homann:
-- Good warning on what might be in store when I update again to Catalina!
-- To start afresh, should I juste do 'sudo port uninstall gcc9' and then  'sudo port install gcc9'?


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).

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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1a. output of upgrade.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 3841 bytes
Desc: 1a. output of upgrade.docx
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20191105/f5b3622c/attachment.docx>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 1b. plist.txt
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20191105/f5b3622c/attachment.txt>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2. old perl files.rtf
Type: text/rtf
Size: 1581 bytes
Desc: 2. old perl files.rtf
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20191105/f5b3622c/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 3. old local portfiles.rtf
Type: text/rtf
Size: 1165 bytes
Desc: 3. old local portfiles.rtf
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20191105/f5b3622c/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 4a. gdbm error main logfile.rtf
Type: text/rtf
Size: 15237 bytes
Desc: 4a. gdbm error main logfile.rtf
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20191105/f5b3622c/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 4b. gdbm error config logfile.rtf
Type: text/rtf
Size: 32063 bytes
Desc: 4b. gdbm error config logfile.rtf
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20191105/f5b3622c/attachment-0003.bin>


More information about the macports-users mailing list