Results 1 to 7 of 7

Thread: Error in install domino, amarok and more aplicattions.

  1. #1
    Just burned his ISO
    Join Date
    Jan 2008
    Posts
    24

    Default Error in install domino, amarok and more aplicattions.

    Hi

    I can not install amarok, dekorator, domino and more aplicattions. I dont have a some package, libpcap?

    LOG ( install domino)
    Code:
    bt domino-0.4 # ./configure
    checking build system type... i686-pc-linux-gnu
    checking host system type... i686-pc-linux-gnu
    checking target system type... i686-pc-linux-gnu
    checking for a BSD-compatible install... /usr/bin/ginstall -c
    checking for -p flag to install... yes
    checking whether build environment is sane... yes
    checking for gawk... gawk
    checking whether make sets $(MAKE)... yes
    checking for kde-config... /opt/kde/bin/kde-config
    checking where to install... /opt/kde (as returned by kde-config)
    checking for style of include used by make... GNU
    checking for gcc... 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 gcc accepts -g... yes
    checking for gcc option to accept ISO C89... none needed
    checking dependency style of gcc... gcc3
    checking how to run the C preprocessor... gcc -E
    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 whether gcc is blacklisted... no
    checking whether g++ supports -Wmissing-format-attribute... yes
    checking whether gcc supports -Wmissing-format-attribute... yes
    checking whether g++ supports -Wundef... yes
    checking whether g++ supports -Wno-long-long... yes
    checking whether g++ supports -Wno-non-virtual-dtor... yes
    checking whether g++ supports -fno-reorder-blocks... yes
    checking whether g++ supports -fno-exceptions... yes
    checking whether g++ supports -fno-check-new... yes
    checking whether g++ supports -fno-common... yes
    checking whether g++ supports -fexceptions... yes
    checking whether system headers can cope with -O2 -fno-inline... irrelevant
    checking how to run the C++ preprocessor... g++ -E
    checking whether g++ supports -O0... yes
    checking whether g++ supports -Wl,--no-undefined... yes
    checking whether g++ supports -Wl,--allow-shlib-undefined... yes
    not using lib directory suffix
    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 ld used by gcc... /usr/i486-slackware-linux/bin/ld
    checking if the linker (/usr/i486-slackware-linux/bin/ld) is GNU ld... yes
    checking for /usr/i486-slackware-linux/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 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 g77... no
    checking for f77... no
    checking for xlf... no
    checking for frt... no
    checking for pgf77... no
    checking for cf77... no
    checking for fort77... no
    checking for fl32... no
    checking for af77... no
    checking for f90... no
    checking for xlf90... no
    checking for pgf90... no
    checking for pghpf... no
    checking for epcf90... no
    checking for gfortran... no
    checking for g95... no
    checking for f95... no
    checking for fort... no
    checking for xlf95... no
    checking for ifort... no
    checking for ifc... no
    checking for efc... no
    checking for pgf95... no
    checking for lf95... no
    checking for ftn... no
    
    bt domino-0.4 # make
    make all-recursive
    make[1]: Entering directory `/root/domino-0.4'
    Making all in domino
    make[2]: Entering directory `/root/domino-0.4/domino'
    make[2]: Nothing to be done for `all'.
    make[2]: Leaving directory `/root/domino-0.4/domino'
    Making all in dominoConfig
    make[2]: Entering directory `/root/domino-0.4/dominoConfig'
    make[2]: Nothing to be done for `all'.
    make[2]: Leaving directory `/root/domino-0.4/dominoConfig'
    Making all in client
    make[2]: Entering directory `/root/domino-0.4/client'
    Making all in .
    make[3]: Entering directory `/root/domino-0.4/client'
    make[3]: Nothing to be done for `all-am'.
    make[3]: Leaving directory `/root/domino-0.4/client'
    Making all in config
    make[3]: Entering directory `/root/domino-0.4/client/config'
    make[3]: Nothing to be done for `all'.
    make[3]: Leaving directory `/root/domino-0.4/client/config'
    make[2]: Leaving directory `/root/domino-0.4/client'
    make[2]: Entering directory `/root/domino-0.4'
    make[2]: Leaving directory `/root/domino-0.4'
    make[1]: Leaving directory `/root/domino-0.4'
    bt domino-0.4 # make install
    Making install in domino
    make[1]: Entering directory `/root/domino-0.4/domino'
    make[2]: Entering directory `/root/domino-0.4/domino'
    make[2]: Nothing to be done for `install-exec-am'.
    test -z "/opt/kde/lib/kde3/plugins/styles" || mkdir -p -- "/opt/kde/lib/kde3/plugins/styles"
    /bin/sh ../libtool --silent --mode=install /usr/bin/ginstall -c -p 'domino.la' '/opt/kde/lib/kde3/plugins/styles/domino.la'
    PATH="$PATH:/sbin" ldconfig -n /opt/kde/lib/kde3/plugins/styles
    test -z "/opt/kde/share/apps/kdisplay/color-schemes" || mkdir -p -- "/opt/kde/share/apps/kdisplay/color-schemes"
    /usr/bin/ginstall -c -p -m 644 'Domino.kcsrc' '/opt/kde/share/apps/kdisplay/color-schemes/Domino.kcsrc'
    test -z "/opt/kde/share/apps/kstyle/themes" || mkdir -p -- "/opt/kde/share/apps/kstyle/themes"
    /usr/bin/ginstall -c -p -m 644 'domino.themerc' '/opt/kde/share/apps/kstyle/themes/domino.themerc'
    make[2]: Leaving directory `/root/domino-0.4/domino'
    make[1]: Leaving directory `/root/domino-0.4/domino'
    Making install in dominoConfig
    make[1]: Entering directory `/root/domino-0.4/dominoConfig'
    make[2]: Entering directory `/root/domino-0.4/dominoConfig'
    test -z "/opt/kde/lib/kde3" || mkdir -p -- "/opt/kde/lib/kde3"
    /bin/sh ../libtool --silent --mode=install /usr/bin/ginstall -c -p 'kstyle_domino_config.la' '/opt/kde/lib/kde3/kstyle_domino_config.la'
    PATH="$PATH:/sbin" ldconfig -n /opt/kde/lib/kde3
    make[2]: Nothing to be done for `install-data-am'.
    make[2]: Leaving directory `/root/domino-0.4/dominoConfig'
    make[1]: Leaving directory `/root/domino-0.4/dominoConfig'
    Making install in client
    make[1]: Entering directory `/root/domino-0.4/client'
    Making install in .
    make[2]: Entering directory `/root/domino-0.4/client'
    make[3]: Entering directory `/root/domino-0.4/client'
    test -z "/opt/kde/lib/kde3" || mkdir -p -- "/opt/kde/lib/kde3"
    /bin/sh ../libtool --silent --mode=install /usr/bin/ginstall -c -p 'kwin3_domino.la' '/opt/kde/lib/kde3/kwin3_domino.la'
    PATH="$PATH:/sbin" ldconfig -n /opt/kde/lib/kde3
    test -z "/opt/kde/share/apps/kwin" || mkdir -p -- "/opt/kde/share/apps/kwin"
    /usr/bin/ginstall -c -p -m 644 'domino.desktop' '/opt/kde/share/apps/kwin/domino.desktop'
    make[3]: Leaving directory `/root/domino-0.4/client'
    make[2]: Leaving directory `/root/domino-0.4/client'
    Making install in config
    make[2]: Entering directory `/root/domino-0.4/client/config'
    make[3]: Entering directory `/root/domino-0.4/client/config'
    test -z "/opt/kde/lib/kde3" || mkdir -p -- "/opt/kde/lib/kde3"
    /bin/sh ../../libtool --silent --mode=install /usr/bin/ginstall -c -p 'kwin_domino_config.la' '/opt/kde/lib/kde3/kwin_domino_config.la'
    PATH="$PATH:/sbin" ldconfig -n /opt/kde/lib/kde3
    make[3]: Nothing to be done for `install-data-am'.
    make[3]: Leaving directory `/root/domino-0.4/client/config'
    make[2]: Leaving directory `/root/domino-0.4/client/config'
    make[1]: Leaving directory `/root/domino-0.4/client'
    make[1]: Entering directory `/root/domino-0.4'
    make[2]: Entering directory `/root/domino-0.4'
    make[2]: Nothing to be done for `install-exec-am'.
    make[2]: Leaving directory `/root/domino-0.4'
    make[1]: Leaving directory `/root/domino-0.4'
    bt domino-0.4 #
    help me...
    ...from Poland...

  2. #2
    Developer balding_parrot's Avatar
    Join Date
    May 2007
    Posts
    3,399

    Default

    Do not double post, when you posted you got a message telling you that your post needed to be approved by a moderator before appearing in the forums, this is also covered in the rules you agreed to when signing up.

    It might be a good idea to read them again.

  3. #3
    Moderator KMDave's Avatar
    Join Date
    Jan 2010
    Posts
    2,281

    Default

    Looks like everything was installed correctly.

    Does the file /opt/kde/share/apps/kstyle/themes/domino.themerc exist?
    Tiocfaidh ár lá

  4. #4
    Just burned his ISO
    Join Date
    Jan 2008
    Posts
    24

    Default

    Quote Originally Posted by KMDave View Post
    Looks like everything was installed correctly.

    Does the file /opt/kde/share/apps/kstyle/themes/domino.themerc exist?
    yes, is exist.
    ...from Poland...

  5. #5
    Moderator KMDave's Avatar
    Join Date
    Jan 2010
    Posts
    2,281

    Default

    Well the log says so too.

    Maybe you should be more precise on what the issue is.
    Tiocfaidh ár lá

  6. #6
    My life is this forum thorin's Avatar
    Join Date
    Jan 2010
    Posts
    2,629

    Default

    Ya I'm not sure what you're after either since your quoted install log doesn't mention anything about libpcap.
    I'm a compulsive post editor, you might wanna wait until my post has been online for 5-10 mins before quoting it as it will likely change.

    I know I seem harsh in some of my replies. SORRY! But if you're doing something illegal or posting something that seems to be obvious BS I'm going to call you on it.

  7. #7
    Just burned his ISO
    Join Date
    Jan 2008
    Posts
    24

    Default

    OK, Log`s in rapidshare.com/files/84257728/log.html

    // sry I must use rapidshre becouse I dont know, what use attachmet this forum ;0

    heh... when, I go amarok :
    bt ~ # amarok
    Amarok: [Loader] Starting amarokapp..
    Amarok: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokapp.
    amarokapp: symbol lookup error: /usr/lib/libamarok.so.0: undefined symbol: _ZN9KLineEdit17mouseReleaseEventEP11QMouseEvent
    bt ~ #
    what this?
    ...from Poland...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •