S
S
Selat2014-03-03 23:05:55
Gentoo
Selat, 2014-03-03 23:05:55

Gentoo error while building luatex: how to fix?

Error building luatex 0.76.0 with poppler-9999.

i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I./w2c  -I/usr/include  -I/usr/include/libpng16  -DPOPPLER_VERSION=\"0.25.1\" -I/usr/include/poppler  -I./libmd5 -DpdfTeX -I./luatexdir -DLUA_COMPAT_MODULE -I./luatexdir/lua52 -DSYNCTEX_ENGINE_H='<synctex-luatex.h>' -I./synctexdir  -Wimplicit -Wreturn-type -Wdeclaration-after-statement -Wno-unknown-pragmas -O2 -march=native -msse4.2 -pipe -c -o luatexdir/lua/libluatex_a-lnodelib.o `test -f 'luatexdir/lua/lnodelib.c' || echo './'`luatexdir/lua/lnodelib.c
luatexdir/lua/lepdflib.cc: In function 'int m_Catalog_getStructTreeRoot(lua_State*)':
luatexdir/lua/lepdflib.cc:576:1: error: cannot convert 'StructTreeRoot*' to 'Object*' in assignment
luatexdir/lua/lepdflib.cc: In function 'int m_PDFDoc_getStructTreeRoot(lua_State*)':
luatexdir/lua/lepdflib.cc:2155:64: error: cannot convert 'StructTreeRoot*' to 'Object*' in assignment
Makefile:6818: recipe for target 'luatexdir/lua/libluatex_a-lepdflib.o' failed
make: *** [luatexdir/lua/libluatex_a-lepdflib.o] Error 1
make: *** Waiting for unfinished jobs....
 * ERROR: dev-tex/luatex-0.76.0::gentoo failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=dev-tex/luatex-0.76.0::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=dev-tex/luatex-0.76.0::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/dev-tex/luatex-0.76.0/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-tex/luatex-0.76.0/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-tex/luatex-0.76.0/work/luatex-beta-0.76.0/source/texk/web2c'
 * S: '/var/tmp/portage/dev-tex/luatex-0.76.0/work/luatex-beta-0.76.0/source'

>>> Failed to emerge dev-tex/luatex-0.76.0, Log file:

Both are required by texlive-2013. How can I fix it?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
B
Boris Nagaev, 2015-03-27
@starius

The developer writes that the problem is fixed. Fixed?

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question