Re: [Pdfedit-support] installing PDFedit the source code, step by step?

[George D. M. <geo...@gm...>]

Marcos, I'm sorry because I don't know how I became listed as if I were an
expert. I am not. I probably know much less than you.

George Del Monte

On Wednesday, April 29, 2015, marcos antonio domingues do amaral <
mdo...@gm...> wrote:

> Marte pdfedit-0.4.5 # ./configure
> checking for g++... g++
> checking whether the C++ compiler works... yes
> checking for C++ compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... no
> 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 how to run the C preprocessor... gcc -E
> checking if zlib is wanted... checking for inflateEnd in -lz... yes
> checking zlib.h usability... yes
> checking zlib.h presence... yes
> checking for zlib.h... yes
> checking for inflateEnd in -lz... (cached) yes
> checking zlib in /usr... ok
> checking for boostlib >= 1.20.0... yes
> configure: Using default COPY="cp -f"
> configure: Using default DEL_FILE="rm -f"
> configure: Using default DEL_DIR="sh $(ROOT)/tools/rmdir.sh"
> configure: Using default DEL_FORCE_DIR="rm -rf"
> configure: Using default SYMLINK="ln -s"
> configure: Using default MOVE="mv -f"
> configure: Using default CHK_DIR_EXISTS="test -d"
> configure: Using default MKDIR="mkdir -p"
> configure: Using default ARCH=""
> configure: Using default C_EXTRA="-fmessage-length=0 -D_FORTIFY_SOURCE=2
> -fno-strict-aliasing"
> configure: Using default EXTRA_UTILS_CFLAGS=""
> configure: Using default EXTRA_KERNEL_CFLAGS=""
> configure: Using default EXTRA_TESTS_CFLAGS=""
> configure: Using default EXTRA_XPDF_CFLAGS=""
> configure: Using default CXX_EXTRA="-fmessage-length=0 -D_FORTIFY_SOURCE=2
> -fno-strict-aliasing -fexceptions"
> configure: Using default EXTRA_UTILS_CXXFLAGS=""
> configure: Using default EXTRA_KERNEL_CXXFLAGS=""
> configure: Using default EXTRA_TESTS_CXXFLAGS=""
> configure: Using default EXTRA_GUI_CXXFLAGS=""
> configure: Using default EXTRA_XPDF_CXXFLAGS=""
> configure: Using default AR="ar cqs"
> configure: Using default LIBPREFIX="lib"
> 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 correctly handles 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... no
> checking t1lib.h presence... no
> checking for t1lib.h... no
> not using t1 library
> checking whether we want to prepare pdfedit-core-dev package... no
> checking whether we want to build PDFedit gui... yes
> configure: error: QTDIR environment variable must be set
>
> 2015-04-29 15:42 GMT-03:00 marcos antonio domingues do amaral <
> mdo...@gm...
> <javascript:_e(%7B%7D,'cvml','mdo...@gm...');>>:
>
>> Hello nice to meet you.
>> I am new to Linux and have difficulties installing PDFedit through the source
>> code using the command ./configure, make and make install.
>> I use Linux Mint 17, 3.13.0-24-generic kernel, x86_64 architecture x86_64
>> GNU / Linux.
>> ./configure command indicates some flaws that I can not solve.
>> as definiri the QTDIR directory? You can carry out installation using qt4
>> ? (my system does not use qt3).
>> I need a guide or tutorial step by step to install the PDFedit.
>> if anyone can help, thank you!
>> sorry my english, I'm using google translator.
>>
>> thank you!
>>
>> Marcos
>>
>
>