[Bug 239608] print/tex-luatex: Linker failure: ld: error: undefined symbol: std::__throw_length_error(char const*)
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sat Aug 3 08:28:01 UTC 2019
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239608
Bug ID: 239608
Summary: print/tex-luatex: Linker failure: ld: error: undefined
symbol: std::__throw_length_error(char const*)
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: Individual Port(s)
Assignee: hrs at FreeBSD.org
Reporter: ohartmann at walstatt.org
Flags: maintainer-feedback?(hrs at FreeBSD.org)
Assignee: hrs at FreeBSD.org
On some boxes running most recent CURRENT as well as recent 12-STABLE and
recent ports (weekly updates) we face a very nasty issue updating and compiling
print/texlive-base/full and especially two pieces of the software packages,
namely print/tex-luatex and print/tex-xetex. print/tex-luatex is named as
example here.
Both ports fail to compile and exit linker, print/tex-luatex fails with:
[...]
/bin/sh ./libtool --tag=CXX --mode=link c++ -Wimplicit -Wreturn-type
-Wno-unknown-pragmas -Wno-write-strings -O2 -pipe -fstack-protector-strong
-fno-strict-aliasing -export-dynamic -fstack-protector-strong -o luatex
luatexdir/luatex-luatex.o mplibdir/luatex-lmplib.o libluatex.a libff.a
libluamisc.a libluasocket.a -L/usr/local/lib -ltexlua52 libmplib.a
-L/usr/local/lib -lmpfr -L/usr/local/lib -lgmp -L/usr/local/lib -lcairo
-lpthread -L/usr/local/lib -lpixman-1 -L/usr/local/lib
-fstack-protector-strong -lzzip -lz -L/usr/local/lib -lpng16 -lz -lz
/usr/ports/print/tex-luatex/work/texlive-20150521-source/libs/poppler/libpoppler.a
lib/lib.a -L/usr/local/lib -lkpathsea libmputil.a libunilib.a libmd5.a -lm
libtool: link: c++ -Wimplicit -Wreturn-type -Wno-unknown-pragmas
-Wno-write-strings -O2 -pipe -fstack-protector-strong -fno-strict-aliasing
-fstack-protector-strong -o luatex luatexdir/luatex-luatex.o
mplibdir/luatex-lmplib.o -fstack-protector-strong -Wl,--export-dynamic
libluatex.a libff.a libluamisc.a libluasocket.a -L/usr/local/lib -ltexlua52
libmplib.a -lmpfr -lgmp -lcairo -lpthread -lpixman-1 -lzzip -lpng16 -lz
/usr/ports/print/tex-luatex/work/texlive-20150521-source/libs/poppler/libpoppler.a
lib/lib.a -lkpathsea libmputil.a libunilib.a libmd5.a -lm
ld: error: undefined symbol: std::__throw_length_error(char const*)
>>> referenced by stl_vector.h:1756 (/usr/local/lib/gcc9/include/c++/bits/stl_vector.h:1756)
>>> Catalog.o:(void std::vector<Dict*, std::allocator<Dict*> >::_M_realloc_insert<Dict* const&>(__gnu_cxx::__normal_iterator<Dict**, std::vector<Dict*, std::allocator<Dict*> > >, Dict* const&)) in archive /usr/ports/print/tex-luatex/work/texlive-20150521-source/libs/poppler/libpoppler.a
ld: error: undefined symbol: std::__throw_length_error(char const*)
>>> referenced by stl_vector.h:1756 (/usr/local/lib/gcc9/include/c++/bits/stl_vector.h:1756)
>>> Catalog.o:(void std::vector<PageAttrs*, std::allocator<PageAttrs*> >::_M_realloc_insert<PageAttrs*>(__gnu_cxx::__normal_iterator<PageAttrs**, std::vector<PageAttrs*, std::allocator<PageAttrs*> > >, PageAttrs*&&)) in archive /usr/ports/print/tex-luatex/work/texlive-20150521-source/libs/poppler/libpoppler.a
[...]
It looks like something is referencing gcc/gcc9 (it was some days ago gcc8) and
fails. I did recompile via "portmaster -dRf print/texlive-full" every piece of
the port several times for now in the hope getting rid of the problem, which is
really sticky on both CURRENT and 12-STABLE boxes. Also did I delete the
packages print/tex-luatex and print/tex-xetex and tried rebuilding the whole
port print/texlive-full, but with no success. I had to install both packages
manually again from a poudriere repository to make texlive work again.
Speaking of poudriere, there seems no problem (but poudriere is no option for
specific machines since they have very individual configs in some ports, but
not TeX).
The problem occured a while ago and bothers me every time tex-xetex or
tex-luatex are updated.
Can someone shed some light on this sort of problem? I do not wee where clang
gets replaced and referenced towards gcc, so there might be a simple fix for
this.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list