LINUX.ORG.RU
Форум — General  

emerge -uDN world


0

0

Доброго времени суток, при очередном обновлении как всегда траблы.

checking for gsapi_new_instance in -lgs... no configure: error: You need libgs in order to compile libspectre

!!! Please attach the following file when seeking support: !!! /var/tmp/portage/app-text/libspectre-0.2.2/work/libspectre-0.2.2/config.log * * ERROR: app-text/libspectre-0.2.2 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 1128: Called econf '--disable-dependency-tracking' '--disable-asserts' '--disable-checks' '--disable-testing' * ebuild.sh, line 534: Called die * The specific snippet of code: * die "econf failed" * The die message: * econf failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/app-text/libspectre-0.2.2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-text/libspectre-0.2.2/temp/environment'

в чем может быть дело?

Во первых в форматировании поста... Во вторых оно тебе само сказало «You need libgs in order to compile libspectre»

init_6 ★★★★★
()
Ответ на: комментарий от init_6

>>> Unpacking source...
>>> Unpacking libspectre-0.2.2.tar.gz to /var/tmp/portage/app-text/libspectre-0.2.2/work
* Running elibtoolize in: libspectre-0.2.2
* Applying install-sh-1.5.4.patch ...
* Applying portage-1.5.10.patch ...
* Applying max_cmd_len-1.5.20.patch ...
* Applying sed-1.5.6.patch ...
* Applying as-needed-1.5.patch ...
>>> Source unpacked in /var/tmp/portage/app-text/libspectre-0.2.2/work
>>> Compiling source in /var/tmp/portage/app-text/libspectre-0.2.2/work/libspectre-0.2.2 ...
* econf: updating libspectre-0.2.2/config.guess with /usr/share/gnuconfig/config.guess
* econf: updating libspectre-0.2.2/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-tracking --disable-asserts --disable-checks --disable-testing
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for style of include used by make... GNU
checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether i686-pc-linux-gnu-gcc accepts -g... yes
checking for i686-pc-linux-gnu-gcc option to accept ISO C89... none needed
checking dependency style of i686-pc-linux-gnu-gcc... none
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ld used by i686-pc-linux-gnu-gcc... /usr/i686-pc-linux-gnu/bin/ld
checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes
checking for /usr/i686-pc-linux-gnu/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... i686-pc-linux-gnu-gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for i686-pc-linux-gnu-g++... i686-pc-linux-gnu-g++
checking whether we are using the GNU C++ compiler... yes
checking whether i686-pc-linux-gnu-g++ accepts -g... yes
checking dependency style of i686-pc-linux-gnu-g++... none
checking how to run the C++ preprocessor... i686-pc-linux-gnu-g++ -E
checking for i686-pc-linux-gnu-g77... no
checking for i686-pc-linux-gnu-xlf... no
checking for i686-pc-linux-gnu-f77... no
checking for i686-pc-linux-gnu-frt... no
checking for i686-pc-linux-gnu-pgf77... no
checking for i686-pc-linux-gnu-cf77... no
checking for i686-pc-linux-gnu-fort77... no
checking for i686-pc-linux-gnu-fl32... no
checking for i686-pc-linux-gnu-af77... no
checking for i686-pc-linux-gnu-xlf90... no
checking for i686-pc-linux-gnu-f90... no
checking for i686-pc-linux-gnu-pgf90... no
checking for i686-pc-linux-gnu-pghpf... no
checking for i686-pc-linux-gnu-epcf90... no

nemilen
() автор топика
Ответ на: комментарий от nemilen

checking for i686-pc-linux-gnu-gfortran... i686-pc-linux-gnu-gfortran
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether i686-pc-linux-gnu-gfortran accepts -g... yes
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from i686-pc-linux-gnu-gcc object... ok
checking for objdir... .libs
checking for i686-pc-linux-gnu-ar... i686-pc-linux-gnu-ar
checking for i686-pc-linux-gnu-ranlib... i686-pc-linux-gnu-ranlib
checking for i686-pc-linux-gnu-strip... i686-pc-linux-gnu-strip
checking if i686-pc-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no
checking for i686-pc-linux-gnu-gcc option to produce PIC... -fPIC
checking if i686-pc-linux-gnu-gcc PIC flag -fPIC works... yes
checking if i686-pc-linux-gnu-gcc static flag -static works... yes
checking if i686-pc-linux-gnu-gcc supports -c -o file.o... yes
checking whether the i686-pc-linux-gnu-gcc linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by i686-pc-linux-gnu-g++... /usr/i686-pc-linux-gnu/bin/ld
checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes
checking whether the i686-pc-linux-gnu-g++ linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes
checking for i686-pc-linux-gnu-g++ option to produce PIC... -fPIC
checking if i686-pc-linux-gnu-g++ PIC flag -fPIC works... yes
checking if i686-pc-linux-gnu-g++ static flag -static works... yes
checking if i686-pc-linux-gnu-g++ supports -c -o file.o... yes
checking whether the i686-pc-linux-gnu-g++ linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for i686-pc-linux-gnu-gfortran option to produce PIC... -fPIC
checking if i686-pc-linux-gnu-gfortran PIC flag -fPIC works... yes
checking if i686-pc-linux-gnu-gfortran static flag -static works... yes
checking if i686-pc-linux-gnu-gfortran supports -c -o file.o... yes
checking whether the i686-pc-linux-gnu-gfortran linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for i686-pc-linux-gnu-gcc... (cached) i686-pc-linux-gnu-gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether i686-pc-linux-gnu-gcc accepts -g... (cached) yes
checking for i686-pc-linux-gnu-gcc option to accept ISO C89... (cached) none needed
checking dependency style of i686-pc-linux-gnu-gcc... (cached) none
checking for strerror in -lcposix... no
checking for i686-pc-linux-gnu-gcc option to accept ISO C99... -std=gnu99
checking for i686-pc-linux-gnu-gcc -std=gnu99 option to accept ISO Standard C... (cached) -std=gnu99
checking for ANSI C header files... (cached) yes
checking whether byte ordering is bigendian... no
checking for vasprintf... yes
checking for gsapi_new_instance in -lgs... no
configure: error: You need libgs in order to compile libspectre

!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/app-text/libspectre-0.2.2/work/libspectre-0.2.2/config.log
*
* ERROR: app-text/libspectre-0.2.2 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 1128: Called econf '--disable-dependency-tracking' '--disable-asserts' '--disable-checks' '--disable-testing'
* ebuild.sh, line 534: Called die
* The specific snippet of code:
* die "econf failed"
* The die message:
* econf failed
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/app-text/libspectre-0.2.2/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/app-text/libspectre-0.2.2/temp/environment

nemilen
() автор топика
Ответ на: комментарий от nemilen

Поставьте app-text/ghostscript-gpl. Там находится нужная либа. не всегда в ебилдах полностью зависимости учитываются, к сожалению.

staseg ★★★★★
()
Ответ на: комментарий от staseg

checking for libgs >= 8.61... no
configure: error: You need libgs >= 8.61 in order to compile libspectre

!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/app-text/libspectre-0.2.2/work/libspectre-0.2.2/config.log
*
* ERROR: app-text/libspectre-0.2.2 failed.

все равно не хочет, грит либы надо
8.61.

nemilen
() автор топика
Ответ на: комментарий от nemilen

Поставьте же версию app-text/ghostscript-gpl >= 8.61.

У меня например стоит 8.64-r3. Она почти для всех архитектур кроме экзотических заявлена стабильной. Может быть давно emerge --sync не делали?

staseg ★★★★★
()
Ответ на: комментарий от nemilen

Вы уж напишите, стоит ли у Вас app-text/ghostscript-gpl

Gary ★★★★★
()
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.
General