Compiling TeX Live on 10.5 (was: libatomic build failure 10.5/x86)

Mojca Miklavec mojca at macports.org
Wed Apr 25 09:05:31 UTC 2018


Hi,

I cannot say why this breaks. This gcc 6 compiler is selected because of
    PortGroup cxx11 1.1
but as far as I remember only dvisvgm required C++11 and that one is
packaged as a separate port anyway. You could try building with gcc 7
(in case it "helps", I tried to build TeX Live 2018 on 10.5/PPC and
that one failed due to another compiler error).

Last year I was able to compile TeX Live 2017 (outside of MacPorts) on
10.6 with gcc 4.2 against 10.5 SDK (after disabling dvisvgm build).

But TeX Live 2018 requires C++11 anyway (ok, maybe it only does so
because of ICU, poppler etc., and the rest of the sources would still
compile without it), so you would soon run into the same compiler
problem.

As a quick fix, I would suggest you to pass the
    --disable-luajittex
flag. Again, I'm not sure why this would be needed, it should
theoretically work (I have a working luajittex for 10.5/i386), but
that might be the fastest workaround. I'm pretty sure you don't need
that binary there.

That's already the case for PPC:

https://github.com/macports/macports-ports/blob/master/tex/texlive-bin/Portfile#L199

If this is in fact broken for some weird reason, we should at least:
- disable luajit in texlive-bin for 10.5/i386 (maybe do more testing)
- test whether gcc 7/8 has the same issue and potentially report it upstream

Mojca

On 25 April 2018 at 10:46, Riccardo Mottola via macports-users 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?
>
> The error is an interna compiler error, not very reassuring!
>
> :info:build make[4]: Entering directory
> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_tex_texlive-bin/texlive-bin/work/texlive-source-20170604-stripped/libs/luajit'
> :info:build depbase=`echo LuaJIT-src/src/lj_cconv.lo | sed
> 's|[^/]*$|.deps/&|;s|\.lo$||'`;\
> :info:build     /bin/sh ./libtool  --tag=CC   --mode=compile
> /opt/local/bin/gcc-mp-6 -DHAVE_CONFIG_H -I.  -I./LuaJIT-src/src
> -DLUAJIT_ENABLE_LUA52COMPAT -DLUAI_HASHLIMIT=6 -U_FORTIFY_SOURCE
> -isystem/opt/local/include -fomit-frame-pointer -march=i686 -msse -msse2
> -mfpmath=sse -fno-stack-protector  -Wall -pipe -Os -m32 -MT
> LuaJIT-src/src/lj_cconv.lo -MD -MP -MF $depbase.Tpo -c -o
> LuaJIT-src/src/lj_cconv.lo LuaJIT-src/src/lj_cconv.c &&\
> :info:build     mv -f $depbase.Tpo $depbase.Plo
> :info:build depbase=`echo LuaJIT-src/src/lj_ctype.lo | sed
> 's|[^/]*$|.deps/&|;s|\.lo$||'`;\
> :info:build     /bin/sh ./libtool  --tag=CC   --mode=compile
> /opt/local/bin/gcc-mp-6 -DHAVE_CONFIG_H -I.  -I./LuaJIT-src/src
> -DLUAJIT_ENABLE_LUA52COMPAT -DLUAI_HASHLIMIT=6 -U_FORTIFY_SOURCE
> -isystem/opt/local/include -fomit-frame-pointer -march=i686 -msse -msse2
> -mfpmath=sse -fno-stack-protector  -Wall -pipe -Os -m32 -MT
> LuaJIT-src/src/lj_ctype.lo -MD -MP -MF $depbase.Tpo -c -o
> LuaJIT-src/src/lj_ctype.lo LuaJIT-src/src/lj_ctype.c &&\
> :info:build     mv -f $depbase.Tpo $depbase.Plo
> :info:build libtool: compile:  /opt/local/bin/gcc-mp-6 -DHAVE_CONFIG_H -I.
> -I./LuaJIT-src/src -DLUAJIT_ENABLE_LUA52COMPAT -DLUAI_HASHLIMIT=6
> -U_FORTIFY_SOURCE -isystem/opt/local/include -fomit-frame-pointer
> -march=i686 -msse -msse2 -mfpmath=sse -fno-stack-protector -Wall -pipe -Os
> -m32 -MT LuaJIT-src/src/lj_ctype.lo -MD -MP -MF
> LuaJIT-src/src/.deps/lj_ctype.Tpo -c LuaJIT-src/src/lj_ctype.c  -fno-common
> -DPIC -o LuaJIT-src/src/.libs/lj_ctype.o
> :info:build libtool: compile:  /opt/local/bin/gcc-mp-6 -DHAVE_CONFIG_H -I.
> -I./LuaJIT-src/src -DLUAJIT_ENABLE_LUA52COMPAT -DLUAI_HASHLIMIT=6
> -U_FORTIFY_SOURCE -isystem/opt/local/include -fomit-frame-pointer
> -march=i686 -msse -msse2 -mfpmath=sse -fno-stack-protector -Wall -pipe -Os
> -m32 -MT LuaJIT-src/src/lj_cconv.lo -MD -MP -MF
> LuaJIT-src/src/.deps/lj_cconv.Tpo -c LuaJIT-src/src/lj_cconv.c  -fno-common
> -DPIC -o LuaJIT-src/src/.libs/lj_cconv.o
> :info:build LuaJIT-src/src/lj_cconv.c: In function 'lj_cconv_ct_ct':
> :info:build LuaJIT-src/src/lj_cconv.c:368:1: internal compiler error: in
> gen_reg_rtx, at emit-rtl.c:1025
> :info:build  }
> :info:build  ^
> :info:build libbacktrace could not find executable to open
> :info:build Please submit a full bug report,
> :info:build with preprocessed source if appropriate.
> :info:build See <https://trac.macports.org/newticket> for instructions.
> :info:build make[4]: *** [LuaJIT-src/src/lj_cconv.lo] Error 1
> :info:build make[4]: *** Waiting for unfinished jobs....
> :
>
> Maybe the dependency can be avoided. Can you build texlive-bin? with which
> compiler? I would also have gcc7:
>
> Koreander:~ multix$ port select gcc
> Available versions for gcc:
>         apple-gcc42
>         gcc40
>         gcc42
>         llvm-gcc42
>         mp-gcc48
>         mp-gcc6
>         mp-gcc7
>         none (active)
>
> 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...)
>
> Thank you!
>
> Riccardo
>
> <main.log.zip>


More information about the macports-users mailing list