Jump to content
Sign in to follow this  
margon

Kompilacja Pgl ( Peerguardian Linux ) Fedora 18

Recommended Posts

Witam
nie jestem dość biegły w instalacji ze źródeł - moźe ze 3 udało mi się dopiać, ale tej bardzo mi zależy
 
ściągłem pgl 2.2.2
czytam plik INSTALL

3.) Build dependencies and runtime environment
==============================================

Build dependencies:
- autotools (autoconf, automake, libtoolize)
- nfnetlink development files
- libnetfilter-queue development files
- libdbus development files (optional, required for the GUI)
- Qt4 development files including Qt4 dbus (optional, required for the GUI)
- zlib development files (optional, for loading gz compressed blocklists
  directly)

instalowałem po kolei intuicyjnie wszystko po kolei,
jednak problem mialem z poszukaniem pakietu libdbus
 
./configure

[[email protected] pgl-2.2.2]$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking how to print strings... printf
checking for style of include used by make... GNU
checking for gcc... gcc
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 gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm - B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert i686-pc-linux-gnu file names to i686-pc-linux-gnu format... func_convert_file_noop
checking how to convert i686-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... no
checking if : is a manifest tool... no
checking how to run the C preprocessor... 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 for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... no
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/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... no
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... no
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for pkg-config... /usr/bin/pkg-config
checking arpa/inet.h usability... yes
checking arpa/inet.h presence... yes
checking for arpa/inet.h... yes
checking for inttypes.h... (cached) yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking for unistd.h... (cached) yes
checking for stdbool.h that conforms to C99... yes
checking for _Bool... yes
checking for inline... inline
checking for size_t... yes
checking for uint16_t... yes
checking for uint32_t... yes
checking for uint8_t... yes
checking for error_at_line... yes
checking for pid_t... yes
checking vfork.h usability... no
checking vfork.h presence... no
checking for vfork.h... no
checking for fork... yes
checking for vfork... yes
checking for working fork... yes
checking for working vfork... (cached) yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible realloc... yes
checking for memchr... yes
checking for memmove... yes
checking for memset... yes
checking for strdup... yes
checking for strerror... yes
checking for strstr... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for libnetfilterqueue... yes
checking for ZLIB... yes
checking for DBUS... no
configure: error: Package requirements (dbus-1) were not met:

No package 'dbus-1' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables DBUS_CFLAGS
and DBUS_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

 
komunikatów z dbus-1 w google jest mnóstwo i dotyczną różnych kompilacji, wiec myślę ze jest coś wcześniej na co należy zwrócić uwagę. Za mało mam doświadczenia żeby dobrze wnioskować w tym temacie.

Share this post


Link to post
Share on other sites

Może dbus-devel?

tak :) 

to jednak nie koniec

 

teraz mam taki stan

 

 [[email protected] pgl-2.2.2]# ./configure |grep "... no"

checking whether we are cross compiling... no

checking for gcc option to accept ISO C89... none needed

checking for a sed that does not truncate output... /usr/bin/sed

checking for dlltool... no

checking for sysroot... no

checking for mt... no

checking if : is a manifest tool... no

checking if gcc supports -fno-rtti -fno-exceptions... no

checking if gcc static flag -static works... no

checking whether -lc should be explicitly linked in... no

checking whether to build static libraries... no

checking if g++ static flag -static works... no

checking for gcc option to accept ISO C89... (cached) none needed

checking vfork.h usability... no

checking vfork.h presence... no

checking for vfork.h... no

checking for moc... no

checking for moc4... no

checking for uic... no

checking for uic4... no

checking for lupdate... no

checking for lupdate4... no

checking for lrelease... no

checking for lrelease4... no

checking for qmake... no

checking for qmake4... no

checking for QT4... no

configure: error: Package requirements (QtCore QtGui polkit-qt-1) were not met:

 

No package 'polkit-qt-1' found

 

Consider adjusting the PKG_CONFIG_PATH environment variable if you

installed software in a non-standard prefix.

 

Alternatively, you may set the environment variables QT4_CFLAGS

and QT4_LIBS to avoid the need to call pkg-config.

See the pkg-config man page for more details.

[[email protected] pgl-2.2.2]#

 

 

podobny problem wygooglowałem tu: http://sourceforge.net/p/peerguardian/bugs/314/

w tym poście jednak pomoje pomysły na to, który pakiet jest "Qt4 development" się kończą.

Linkowałem nawet wg tego postu :

ln -s /usr/bin/qmake-qt4 qmake

ln -s /usr/bin/lrelease-qt4 lrelease

ale to chyba ruchy ślepego we mgle.

Share this post


Link to post
Share on other sites

@margon - tak ogólnie szukaj pakietów *-devel.

A jak szukać? Korzystaj z yum provides, yum search. "provides" przyjmuje metaznaki, czyli np.

yum provides polkit\*
Jak masz w odnalezionej ścieżce "include" to duża szansa, że trafiłeś na właściwy pakiet.

Share this post


Link to post
Share on other sites

qt-devel ?

polkit-qt-devel ?

polkit-qt-devel

:) tak !

dzięki

 

 

@margon - tak ogólnie szukaj pakietów *-devel.

A jak szukać? Korzystaj z yum provides, yum search. "provides" przyjmuje metaznaki, czyli np.

yum provides polkit\*
Jak masz w odnalezionej ścieżce "include" to duża szansa, że trafiłeś na właściwy pakiet.

dzięki wielkie

search owszem, ale provides przegapiałem z premedytacją

 

Bardzo dziękuje za pomoc, PeerGuardian działa :)

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...