On Apr 25, 2018, at 03:46, Riccardo Mottola wrote: > Then I resume upgrading.. and something pulls in texlive-bin > > ---> Computing dependencies for texlive-bin > ---> Building texlive-bin > Error: Failed to build texlive-bin: command execution failed > Error: See > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_tex_texlive-bin/texlive-bin/main.log > for details. > Error: Problem while installing texlive-bin > > > > I do not have it currently installed: > > texinfo @6.5_1 (active) > texlive-common @2017.1_0 (active) > > > so it is not an upgraded but a new dependency?
Evidently. > The error is an interna compiler error, not very reassuring! > But gcc6 is checked as a dependency, I attach the log. > > I notice this: > :notice:configure ---> Configuring texlive-bin > :debug:configure Preferred compilers: gcc-4.2 apple-gcc-4.2 gcc-4.0 > macports-clang-3.4 macports-clang-3.3 > :debug:configure Using compiler 'MacPorts GCC 6' > > toes this mean I have none of the "preferred" compilers ? I actually have > e.g. apple-gcc42 and also clang 3.4 from macports: > > Koreander:~ multix$ port select clang > Available versions for clang: > mp-clang-3.4 > none (active) > > So why is it using gcc6? (not that gcc6 should.... ICE, but well...) texlive-bin, like many other ports these days, requires a C++11-capable compiler. On PowerPC, we only use MacPorts gcc6 to build such ports.
