Re: failure to get gcc9 running

[Hans Goedbloed]

?

Thanks a lot Ryan! Macports and the gfortran compiler now work on all my 
nachines.



Cheers, Hans



From: Ryan Schmidt 
Sent: Saturday, November 9, 2019 5:53 PM
To: Hans Goedbloed
Cc: Chris Jones; trainma...@gmail.com; MacPorts Users
Subject: Re: failure to get gcc9 running

On Nov 9, 2019, at 08:48, Hans Goedbloed wrote:

(Since there are numerous complaints on Xcode 11.2 and Catalina, I downloaded 
Xcode 10.0.)

It's true that using Xcode 11.x on Mojave with MacPorts can be problematic 
right now and we recommend using Xcode 10.x on Mojave. But you should use the 
latest version of Xcode 10.x, which is 10.3. Install the Xcode 10.3 version of 
the command line tools too.


--->  Installing libgcc9 @9.2.0_1
Error: Failed to install libgcc9: no destroot found at: 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc9/libgcc9/work/destroot

See:

https://trac.macports.org/wiki/ProblemHotlist#nodestrootfound

Re: failure to get gcc9 running

[Ryan Schmidt]

On Nov 9, 2019, at 08:48, Hans Goedbloed wrote:
> 
> (Since there are numerous complaints on Xcode 11.2 and Catalina, I downloaded 
> Xcode 10.0.) 

It's true that using Xcode 11.x on Mojave with MacPorts can be problematic 
right now and we recommend using Xcode 10.x on Mojave. But you should use the 
latest version of Xcode 10.x, which is 10.3. Install the Xcode 10.3 version of 
the command line tools too. 


> --->  Installing libgcc9 @9.2.0_1
> Error: Failed to install libgcc9: no destroot found at: 
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc9/libgcc9/work/destroot

See:

https://trac.macports.org/wiki/ProblemHotlist#nodestrootfound

Re: failure to get gcc9 running

[Hans Goedbloed]

1-09T12:09:18+0100'
  libcxx @5.0.1_4 (active) platform='darwin 18' archs='noarch' 
date='2019-11-09T12:08:38+0100'
  libedit @20191025-3.1_0 (active) platform='darwin 18' archs='x86_64' 
date='2019-11-09T12:08:41+0100'
  libffi @3.2.1_0 (active) platform='darwin 18' archs='x86_64' 
date='2019-11-09T12:08:42+0100'
  libiconv @1.16_0 (active) platform='darwin 18' archs='x86_64' 
date='2019-11-09T12:08:48+0100'
  libxml2 @2.9.9_3 (active) platform='darwin 18' archs='x86_64' 
date='2019-11-09T12:08:52+0100'
  llvm-8.0 @8.0.1_0 (active) platform='darwin 18' archs='x86_64' 
date='2019-11-09T12:09:10+0100'
  llvm_select @2_0 (active) platform='darwin 18' archs='noarch' 
date='2019-11-09T12:08:42+0100'
  ncurses @6.1_0 (active) platform='darwin 18' archs='x86_64' 
date='2019-11-09T12:08:38+0100'
  openssl @1.1.1d_0 (active) platform='darwin 18' archs='x86_64' 
date='2019-11-09T12:08:53+0100'
  xar @1.6.1_4 (active) platform='darwin 18' archs='x86_64' 
date='2019-11-09T12:09:05+0100'
  xz @5.2.4_0 (active) platform='darwin 18' archs='x86_64' 
date='2019-11-09T12:08:51+0100'
  zlib @1.2.11_0 (active) platform='darwin 18' archs='x86_64' 
date='2019-11-09T12:08:51+0100'
A number of ports are there, but not the essential ones pertaining to gcc9.
No clou on how to proceed!

---

Attached:
Failed installation gcc9 - (1) Terminal Saved Output 9-11-2019
Failure report man.log - (2) Terminal Saved Output 9-11-2019


From: Chris Jones 
Sent: Tuesday, November 5, 2019 2:47 PM
To: Hans Goedbloed; Ryan Schmidt; trainma...@gmail.com
Cc: MacPorts Users
Subject: Re: failure to get gcc9 running

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'?
>
>
> To Ryan Schmidt:
> -- (1) Attached is "1a. output of upgrade" and "1b. plist". I can not make 
> anything of it.

You mis-typed the command... Its

 > sudo port -d rev-upgrade

not

 > sudo port -d rev -upgrade

i.e. rev-upgrade is one word.

I have no idea what the plist file you sent is for ?

> -- (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"?

 > sudo port sync
 > sudo port upgrade outdated

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

That is not what Ryan asked for. He asked if you had configured your
local installation to use a custom local Portfiles. i.e. have you
*changed* /opt/local/etc/macports/sources.conf ??


( At this point though, given all the problems you have its going to be
very hard I would say for anyway to understand what you have, and have
not done to your system, as part of the upgrade process, so probably the
simplest approach is to wipe out the macports installation and start
afresh. Just my view, others might disagree. )

Chris


Failed installation gcc9 - (1) Terminal Saved Output 9-11-2019
Description: Failed installation gcc9 - (1) Terminal Saved Output 9-11-2019


Failure report main.log - (2) Terminal Saved Output 9-11-2019
Description: Failure report main.log - (2) Terminal Saved Output 9-11-2019

Re: failure to get gcc9 running

[Chris Jones]

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


To Ryan Schmidt:
-- (1) Attached is "1a. output of upgrade" and "1b. plist". I can not make 
anything of it.


You mis-typed the command... Its

> sudo port -d rev-upgrade

not

> sudo port -d rev -upgrade

i.e. rev-upgrade is one word.

I have no idea what the plist file you sent is for ?


-- (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"?


> sudo port sync
> sudo port upgrade outdated


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


That is not what Ryan asked for. He asked if you had configured your 
local installation to use a custom local Portfiles. i.e. have you 
*changed* /opt/local/etc/macports/sources.conf ??



( At this point though, given all the problems you have its going to be 
very hard I would say for anyway to understand what you have, and have 
not done to your system, as part of the upgrade process, so probably the 
simplest approach is to wipe out the macports installation and start 
afresh. Just my view, others might disagree. )


Chris

Re: failure to get gcc9 running

[Chris Jones]

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 
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
---> Cl

Re: failure to get gcc9 running

[Hans Goedbloed]

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 
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 @

Re: failure to get gcc9 running

[Peter Homann]

There's also lots of messages in there that suggest you don't have the
10.14 SDK, which may mean Xcode hasn't yet been updated on your system.

I got my system in quite a tangle recently when Catalina finally got
beyond beta, but the uninstall/reinstall approach worked best for
getting it right again.

Peter.

On 5/11/19 05:49, Ryan Schmidt wrote:
>
> 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

Re: failure to get gcc9 running

[Ryan Schmidt]

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.

Re: failure to get gcc9 running

[Christopher Jones]

> 
> --->  Computing dependencies for gdbm
> --->  Fetching distfiles for 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.
> Error: rev-upgrade failed: Error rebuilding gdbm
> Error: Follow https://guide.macports.org/#project.tickets 
>  to report a bug.
> --​
> 
> It all leads me nowhere. Was it a mistake to upgrade to macOS 1014 for this 
> MacBook? It all worked nicely before with the Fortran compiler g95. However, 
> that does not work anymore with the new system, so I had to download gcc9. 
> Gave me this enormous sequence of errors which I do not know how to fix. I 
> will greatly appreciate assistance on this. 

gcc9 works just fine on 10.14 so whatever you did to get into the state above, 
it is not normal. 

A few comments.

- Did you *really* correctly follow the migration instructions at

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


? 

as I am not sure how you could get into such a mess if you had. Did you really 
remove *all* ports in order to reinstall them ?

- When you get errors like those above, you have to look into the log file that 
is referenced. e.g.

> 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

so, what does that log say ?

Honestly, the simplest solution might be to start again, as if you are doing an 
OS migration. So follow the instructions above, making sure to remove 
everything.

I would also suggest *not* just blinding reinstalling everything you previously 
had, so once you get to a point where you have an empty vanilla MacPOrts 
installation, please just run

> sudo port sync
> sudo port install gcc9

that, should work just fine. Then you can go from there adding what else you 
want.

Chris

smime.p7s
Description: S/MIME cryptographic signature