[Pluto-help] Aiuto installazione theme Liquid in kde

[Alessandro Toso]

Che distribuzione usi?
Ho letto sul sito di liquid che ci sono ancora problemi per farlo funzionare
su Suse!
Ciao
----- Original Message -----
From: "rian" <rian a quipo.it>
To: <pluto-help a lists.pluto.linux.it>
Sent: Tuesday, July 23, 2002 10:49 PM
Subject: [Pluto-help] Aiuto installazione theme Liquid in kde


sì, sono sempre io...scusate!
allora, vorrei installare il theme Liquid 0.9.5 per kde 3.0 ma non riesco.
ho scaricato il sorgente e l'ho scompattato: nelle istruzioni c'è scritto
semplicemente di seguire la procedura standard per la compilazione, ma
ricevo
un errore...
riporto qui sotto tutta la procedura (scusate la lunghezza)

# ./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/install -c
checking for -p flag to install... yes
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... missing
checking for working autoconf... missing
checking for working automake... missing
checking for working autoheader... missing
checking for working makeinfo... missing
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for executable suffix...
checking for object suffix... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
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 whether g++ supports -fno-exceptions... yes
checking whether g++ supports -fno-check-new... yes
checking whether g++ supports -fexceptions... yes
checking how to run the C++ preprocessor... g++ -E
checking whether g++ supports -frepo... yes
checking for ld used by GCC... /usr/i486-suse-linux/bin/ld
checking if the linker (/usr/i486-suse-linux/bin/ld) is GNU ld... yes
checking for /usr/i486-suse-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 dependant libraries... pass_all
checking for ranlib... ranlib
checking for strip... strip
checking whether -lc should be explicitly linked in... yes
checking for objdir... .libs
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... yes
finding the maximum length of command line arguments... 73729
checking if gcc supports -c -o file.o... yes
checking if gcc supports -fno-rtti -fno-exceptions ... yes
checking whether the linker (/usr/i486-suse-linux/bin/ld) supports shared
libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking command to parse /usr/bin/nm -B output... ok
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for dlopen in -ldl... yes
checking for dlfcn.h... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... no
creating libtool
updating cache /dev/null
checking host system type... i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
ltcf-cxx: with_gcc=yes ; with_gnu_ld=yes
checking for objdir... .libs
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... yes
finding the maximum length of command line arguments... 73729
checking if g++ supports -c -o file.o... yes
checking if g++ supports -fno-rtti -fno-exceptions ... yes
checking whether the linker (/usr/i486-suse-linux/bin/ld) supports shared
libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking command to parse /usr/bin/nm -B output... ok
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for dlopen in -ldl... yes
checking for dlfcn.h... yes
checking whether a program can dlopen itself... no
appending configuration tag "CXX" to libtool
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
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 main in -lutil... yes
checking for main in -lcompat... no
checking for crypt in -lcrypt... yes
checking for socklen_t... socklen_t
checking for dnet_ntoa in -ldnet... no
checking for dnet_ntoa in -ldnet_stub... no
checking for inet_ntoa... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for res_init... no
checking for killpg in -lucb... no
checking for int... yes
checking size of int... 4
checking for long... yes
checking size of long... 4
checking for char *... yes
checking size of char *... 4
checking for char... yes
checking size of char... 1
checking for dlopen in -ldl... yes
checking for shl_unload in -ldld... no
checking for X... configure: error: Can't find X includes. Please check your
installation and add the correct paths!

cosa devo aggiungere?
secondo me parecchie cose...
help!

saluti,
Riccardo


_______________________________________________
pluto-help mailing list
pluto-help a lists.pluto.linux.it
http://lists.pluto.linux.it/mailman/listinfo/pluto-help