erro ao instalar pdfedit

leoCCB
(usa Slackware)

Enviado em 12/12/2012 - 11:42h

Bom dia a todos!!

Mais uma vez preciso da ajuda de vocês!!

Bem, para instalar o pdfedit, eu precisava de uns pacotes, os quais, creio eu, foram baixados, porém gerou um erro, na seguinte tela



checking for g++... g++
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 g++ accepts -g... yes
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether make sets $(MAKE)... yes
checking for ranlib... ranlib
checking whether ln -s works... yes
checking how to run the C++ preprocessor... g++ -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -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 limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for unistd.h... (cached) yes
checking for stdbool.h that conforms to C99... yes
checking for _Bool... no
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for size_t... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for boostlib >= 1.20.0... yes
checking whether the Boost::IOStreams library is available... yes
checking for exit in -lboost_iostreams... no
configure: error: Could not link against boost_iostreams !



Observem: configure: error: Could not link against boost_iostreams ! na última linha

o que fazer??

e também te um "cross compiler" que eu já baixei um cross mas não resolveu

desde já agradeço

danniel-lara
(usa Fedora)

Enviado em 12/12/2012 - 11:47h

tu instalou o pacote libboost-iostreams-dev ?
se não , é só instalar


espero que ajude

lcavalheiro
(usa Slackware)

Enviado em 12/12/2012 - 12:10h

Ensinando a ler: nas linhas que dizem

Ele está reclamando que não tem esse pacote instalado. Instale o pacote (o que o daniel-lara recomendou) que esse problema se resolve.
Para pesquisar o nome de algum pacote no Debian, recomendo o http://www.debian.org/distrib/packages.

leoCCB
(usa Slackware)

Enviado em 12/12/2012 - 12:44h

Obrigado pela rapidez pessoal... vcs são fera!!!

Vou aplicar a instalação e volto a postar!!

leoCCB
(usa Slackware)

Enviado em 12/12/2012 - 13:00h

bem pessoal,instalei o pacote indicado por vcs e mais alguns, mas agora travei de novo...



checking for g++... g++
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 g++ accepts -g... yes
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether make sets $(MAKE)... yes
checking for ranlib... ranlib
checking whether ln -s works... yes
checking how to run the C++ preprocessor... g++ -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -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 limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for unistd.h... (cached) yes
checking for stdbool.h that conforms to C99... yes
checking for _Bool... no
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for size_t... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for boostlib >= 1.20.0... yes
checking whether the Boost::IOStreams library is available... yes
checking for exit in -lboost_iostreams-mt... yes
checking whether we use stack protector... no
checking whether we are releasing... true
checking whether debug info is included... no
checking whether to enable observer debugging... no
checking for error_at_line... yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking whether lstat dereferences a symlink specified with a trailing slash... yes
checking whether stat accepts an empty string... no
checking for strftime... yes
checking for atexit... yes
checking for floor... yes
checking for ftruncate... yes
checking for localtime_r... yes
checking for memset... yes
checking for mkdir... yes
checking for strdup... yes
checking for strerror... yes
checking for strpbrk... yes
checking for strstr... yes
checking for freetype-config... no
checking for FreeType -- version >= 7.0.1... no
configure: WARNING:

The freetype-config script installed by FreeType 2 could not be found.
If FreeType 2 was installed in PREFIX, make sure PREFIX/bin is in
your path, or set the FT2_CONFIG environment variable to the
full path to freetype-config.

checking whether to use t1 library... maybe
checking where to find the t1 header files...
checking t1lib.h usability... yes
checking t1lib.h presence... yes
checking for t1lib.h... yes
checking for T1_InitLib in -lt1... yes
using t1 library
checking whether we want to build PDFedit gui... yes
configure: error: QTDIR environment variable must be set


desculpem minha ignorância, mas tenho medo de começar a fuçar sozinho e ter que reinstalar tudo, como já aconteceram algumas vezes.