gcc48 not supported on MacOS 10.13 High Sierra

[manulcaux]

I upgraded my Mac OS to 10.13 High Sierra I upgraded MacPort downloading and running the MacPorts-2.4.1-10.13-HighSierra.pkg When then running sudo port upgrade outdated, I get this error :

[macp2052:~] caux% sudo port selfupdate
Password:
--->  Updating MacPorts base sources using rsync
MacPorts base version 2.4.1 installed,
MacPorts base version 2.4.1 downloaded.
--->  Updating the ports tree
--->  MacPorts base is already the latest version

The ports tree has been updated. To upgrade your installed ports, you should run
  port upgrade outdated
[macp2052:~] caux% sudo port upgrade outdated
--->  Fetching distfiles for gcc48
Error: gcc48 is not supported on macOS High Sierra and newer
Error: Failed to fetch gcc48: unsupported platform
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc48/gcc48/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
[macp2052:~] caux% sudo port clean
Can't map the URL 'file://.' to a port description file ("Could not find Portfile in /Users/caux").
Please verify that the directory and portfile syntax are correct.
To use the current port, you must be in a port's directory.
[macp2052:~] caux% 

In the file /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc48/gcc48/main.log

I see

gcc48 is not supported on macOS High Sierra and newer

Is this definitive ? Meaning the software I have needing gcc48 to compile will not be working anymore ?

[manulcaux]

should have written :

[macp2052:~] caux% sudo port upgrade outdated 
---> Fetching distfiles for gcc48
Error: gcc48 is not supported on macOS High Sierra and newer 
Error: Failed to fetch gcc48: unsupported platform 
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc48/gcc48/main.log for details. 
Error: Follow ​https://guide.macports.org/#project.tickets to report a bug. 

[macp2052:~] caux% sudo port clean 
Can't map the URL '​file://.' to a port description file ("Could not find Portfile in /Users/caux"). 
Please verify that the directory and portfile syntax are correct. To use the current port, you must be in a port's directory. 
[macp2052:~] caux%

[mf2k (Frank Schima)]

In the future, please use WikiFormatting and fill in the Port field.

[raimue (Rainer Müller)]

After upgrading to High Sierra, please run a full Migration.

Do you actually need gcc48 for anything? Which ports are outdated, that would help us to identify which port wants to use gcc48 and could use an alternative.

[manulcaux]

As suggested, I tried to find which ports were using gcc48, and following the instructions given in the Migration procedure instructions, I tried to upgrade the first one (alphabetically), which is ast.

It tried to re-install it, and for that it downloaded gcc5 but failed to build it, please find the details in the attached file.

May be I do not need anymore gcc4.8, but for sure I mandatory need gcc5 for a few ports, ast and gildas at least.

Therefore I am even more stuck !

Many thanks for helping me.

[ryandesign (Ryan Carsten Schmidt)]

The gcc5 log you attached omitted all relevant information. However I assume it's the same gcc5 build error already being tracked as #54949.

gcc6, gcc7 and gcc8 build fine on High Sierra. Can you use one of those instead? I don't think there's a compelling reason yet to invest time in making gcc4x work on High Sierra.

[ryandesign (Ryan Carsten Schmidt)]

Replying to manulcaux:

[...] I tried to upgrade the first one (alphabetically), which is ast.

It tried to re-install it, and for that it downloaded gcc5 [...]

ast has variants for choosing which gcc you want. The default today is gcc7:

$ port variants ast
ast has the variants:
   dragonegg33: Build using the MacPorts dragonegg 3.3 compiler
     * conflicts with dragonegg34 g95 gcc44 gcc45 gcc46 gcc47 gcc48 gcc49 gcc5 gcc6 gcc7
   dragonegg34: Build using the MacPorts dragonegg 3.4 compiler
     * conflicts with dragonegg33 g95 gcc44 gcc45 gcc46 gcc47 gcc48 gcc49 gcc5 gcc6 gcc7
   g95: Build using the g95 Fortran compiler
     * conflicts with dragonegg33 dragonegg34 gcc44 gcc45 gcc46 gcc47 gcc48 gcc49 gcc5 gcc6 gcc7
   gcc44: Build using the MacPorts gcc 4.4 compiler
     * conflicts with dragonegg33 dragonegg34 g95 gcc45 gcc46 gcc47 gcc48 gcc49 gcc5 gcc6 gcc7
   gcc45: Build using the MacPorts gcc 4.5 compiler
     * conflicts with dragonegg33 dragonegg34 g95 gcc44 gcc46 gcc47 gcc48 gcc49 gcc5 gcc6 gcc7
   gcc46: Build using the MacPorts gcc 4.6 compiler
     * conflicts with dragonegg33 dragonegg34 g95 gcc44 gcc45 gcc47 gcc48 gcc49 gcc5 gcc6 gcc7
   gcc47: Build using the MacPorts gcc 4.7 compiler
     * conflicts with dragonegg33 dragonegg34 g95 gcc44 gcc45 gcc46 gcc48 gcc49 gcc5 gcc6 gcc7
   gcc48: Build using the MacPorts gcc 4.8 compiler
     * conflicts with dragonegg33 dragonegg34 g95 gcc44 gcc45 gcc46 gcc47 gcc49 gcc5 gcc6 gcc7
   gcc49: Build using the MacPorts gcc 4.9 compiler
     * conflicts with dragonegg33 dragonegg34 g95 gcc44 gcc45 gcc46 gcc47 gcc48 gcc5 gcc6 gcc7
   gcc5: Build using the MacPorts gcc 5 compiler
     * conflicts with dragonegg33 dragonegg34 g95 gcc44 gcc45 gcc46 gcc47 gcc48 gcc49 gcc6 gcc7
   gcc6: Build using the MacPorts gcc 6 compiler
     * conflicts with dragonegg33 dragonegg34 g95 gcc44 gcc45 gcc46 gcc47 gcc48 gcc49 gcc5 gcc7
[+]gcc7: Build using the MacPorts gcc 7 compiler
     * conflicts with dragonegg33 dragonegg34 g95 gcc44 gcc45 gcc46 gcc47 gcc48 gcc49 gcc5 gcc6

Perhaps when you originally installed it, gcc5 was the default. But if instead of upgrading it you reinstall it without specifying any variants, or if you specify the gcc7 variant, it should use that instead of gcc5.

[manulcaux]

Hi,

The problem is I need gcc5 for another port (gildas). I also need g95 but both crash at install. I then uninstall all my ports (sudo port uninstall all) to start from a fresh and clean Mac Port install, but both gcc5 and g95 are still crashing at install.

I attach both main.log files.

Many thanks for helping me.

[ryandesign (Ryan Carsten Schmidt)]

The gcc5 build failure is known and is tracked in #54949.

Two different g95 build failures are already known and tracked in #54427 and #54825 though neither of them look like what's in your log so you may have found a third problem. We can leave this ticket open to track your g95 issue, or we can close it (since your original request related to making gcc48 work on High Sierra, which I think we're not going to do) and you can file a new ticket for your g95 issue.

[ryandesign (Ryan Carsten Schmidt)]

Replying to manulcaux:

The problem is I need gcc5 for another port (gildas).

gildas also has variants to let you choose which compiler you want to use. Simply tell it you want to use gcc7.

[manulcaux]

Hi,

Even if gildas can be compiled with gcc7 (did not try), it requests cfitsio to be compiled with g95. I also use g95 on a regular basis to compile hand-made fortran codes.

To summarise, even if I can close this ticket opened for gcc48 and if I should not bother about gcc5 (TBC), I at least need g95 to compile on High Sierra.

I will then open a new ticked specific to this as you say it is a new bug not traced by the 2 other tickets.

Many thanks

[ryandesign (Ryan Carsten Schmidt)]

cfitsio also has variants for choosing the compiler.