Installazione KDE 4 Beta1 su Slackware12
Moderatore: Staff
Regole del forum
1) Citare sempre la versione di Slackware usata, la versione del Kernel e magari anche la versione della libreria coinvolta. Questi dati aiutano le persone che possono rispondere.
2) Per evitare confusione prego inserire in questo forum solo topic che riguardano appunto Slackware, se l'argomento è generale usate il forum Gnu/Linux in genere.
3) Leggere attentamente le risposte ricevute.
4) Scrivere i messaggi con il colore di default, evitare altri colori.
5) Scrivere in Italiano o in Inglese, se possibile grammaticalmente corretto, evitate stili di scrittura poco chiari, quindi nessuna abbreviazione tipo telegramma o scrittura stile SMS o CHAT.
6) Appena registrati è consigliato presentarsi nel forum dedicato.
La non osservanza delle regole porta a provvedimenti di vari tipo da parte dello staff, in particolare la non osservanza della regola 5 porta alla cancellazione del post e alla segnalazione dell'utente. In caso di recidività l'utente rischia il ban temporaneo.
1) Citare sempre la versione di Slackware usata, la versione del Kernel e magari anche la versione della libreria coinvolta. Questi dati aiutano le persone che possono rispondere.
2) Per evitare confusione prego inserire in questo forum solo topic che riguardano appunto Slackware, se l'argomento è generale usate il forum Gnu/Linux in genere.
3) Leggere attentamente le risposte ricevute.
4) Scrivere i messaggi con il colore di default, evitare altri colori.
5) Scrivere in Italiano o in Inglese, se possibile grammaticalmente corretto, evitate stili di scrittura poco chiari, quindi nessuna abbreviazione tipo telegramma o scrittura stile SMS o CHAT.
6) Appena registrati è consigliato presentarsi nel forum dedicato.
La non osservanza delle regole porta a provvedimenti di vari tipo da parte dello staff, in particolare la non osservanza della regola 5 porta alla cancellazione del post e alla segnalazione dell'utente. In caso di recidività l'utente rischia il ban temporaneo.
-
hawake
- Linux 0.x

- Messaggi: 36
- Iscritto il: mer 5 set 2007, 10:17
- Località: A tre micron dal BIOS
- Contatta:
Ok l'ho installato usando l'SVN-Build, mi è comparso un file (vuoto) chiamato built-successfully il quale mi fa pensare che il tutto sia andato correttamente, ma ora, per avviare il tutto come devo fare?
Un classico startkde? Ho provato pure ad usare l'XwmConfig ma nella lista non è presente...
Grazie delle risposte in anticipo e scusate la niubbagine,
Saluti
hawake
Un classico startkde? Ho provato pure ad usare l'XwmConfig ma nella lista non è presente...
Grazie delle risposte in anticipo e scusate la niubbagine,
Saluti
hawake
è evidente che qualcosa ti è andato storto.
kdesvn-build ti crea una directory ~/kdesvn con dentro tutti i sorgenti, una directory dei log, e una con i sorgenti compilati che poi installa in ~/kde
Durante lo script ti avrà pur detto cosa stava facendo no? Tipo se è fallito il download dei sorgenti, se non è riuscito a compilare, o se ha installato. E' un procedimento che richiede almeno un paio d'ore, non è possibile che non ti sia accorto di niente!
kdesvn-build ti crea una directory ~/kdesvn con dentro tutti i sorgenti, una directory dei log, e una con i sorgenti compilati che poi installa in ~/kde
Durante lo script ti avrà pur detto cosa stava facendo no? Tipo se è fallito il download dei sorgenti, se non è riuscito a compilare, o se ha installato. E' un procedimento che richiede almeno un paio d'ore, non è possibile che non ti sia accorto di niente!
-
hawake
- Linux 0.x

- Messaggi: 36
- Iscritto il: mer 5 set 2007, 10:17
- Località: A tre micron dal BIOS
- Contatta:
E' questo quello che mi stupisce! Ha scaricato tutto il necessario e poi ha fatto altre operazioni fatto tutto ciò è ricomparsa la linea di comando:dapuzz ha scritto:Durante lo script ti avrà pur detto cosa stava facendo no? Tipo se è fallito il download dei sorgenti, se non è riuscito a compilare, o se ha installato. E' un procedimento che richiede almeno un paio d'ore, non è possibile che non ti sia accorto di niente!
Questo è il file di configurazione che ho settato:kdeprova@FallenStar ->
Codice: Seleziona tutto
# Sample configuration file for kdesvn-build.
#
# To use this sample configuration file, copy it to ~/.kdesvn-buildrc, and then
# edit it to suit your desires.
# Global settings go in this section. They apply to every module unless
# overridden later.
global
# This option controls whether KDE 3.5 or KDE 4.0 is compiled. If you set this
# option to true, kdesvn-build will automatically select the correct branch of
# a module needed to build KDE 3.5 in most cases. Most modules will come from
# the 3.5 branch, arts will come from 1.5, and qt-copy will come from 3.3.
#
# It is always possible to override the default by using the branch, tag, or
# override-url option yourself.
#
# If you set this option to false, or leave it unset, kdesvn-build will build
# /trunk, which corresponds right now with KDE 4.0. If you set this option to
# true, you should also comment out or remove the branch option which is set
# in the "module kdelibs" section below.
#
# use-stable-kde false
# binpath controls the value of the PATH environment variable during
# compilation. If you have unusual tools that need to be in the path to build
# KDE, add them here. KDE's and Qt's programs are automatically added.
# If you leave this option blank, it will default to the PATH that kdesvn-build had
# when it was started.
binpath /bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
binpath /usr/lib/ccache/bin:/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
# This is the directory that your KDE sources are downloaded to. This
# directory also holds the build and log directories by default.
source-dir ~/kdesvn
# This directory is where everything gets built before it is installed. By
# default it is relative to the value for source-dir. You can specify an
# absolute path if you'd like (begin the path with a slash).
# build-dir build
# This is the directory that KDE will end up installed at. The default is
# appropriate for a single-user installation of KDE, which requires no root
# permissions. If you'd like, you can install and use the sudo program to
# install KDE anywhere on your system, in conjunction with the
# make-install-prefix option.
kdedir ~/kde
#
# You can overwrite the installation directory for a given module using
# the per-module "prefix" option. Note that when doing this you need to
# set KDEDIRS, PATH and LD_LIBRARY_PATH to point to both directories,
# and that you should use separate test users or KDEHOME values to separate
# the ksycoca databases. Only set prefix if you know what you're doing.
# If you would like install KDE to the system (DO NOT INSTALL *over* a prior
# installation!), then you'll probably need to use sudo to install everything.
#
# The -S parameter causes sudo to read from standard input (which is redirected
# by kdesvn-build). This means that if sudo has to ask for your password, it
# will fail, you need to configure sudo to be able to run "make install" and
# "unsermake install" without requesting a password.
# make-install-prefix sudo -S
# This is the Qt installation to use to build KDE. The default is qt-copy
# from Subversion. The ${build-dir} option uses whatever you set for
# build-dir to automatically fill in the value.
# For qt-copy users, this is also the directory to install qt-copy to.
# KDE 4.0 may require qt-copy at times instead of a released Qt so it is
# better to use qt-copy for /trunk users.
qtdir ~/qt4 # Default to installing Qt (Qt 4).
# qtdir ${build-dir}/build/qt-copy # Use built Qt (Qt 3).
# You might want to use your system's built-in Qt already (4.1 or greater for
# KDE 4, 3.3.x for KDE 3.5.) If so, assign the qtdir option appropriately.
# See note above, KDE 4 may require qt-copy at times.
# qtdir /path/to/system/qt
# This is the Subversion server to download the KDE sources from. Developers:
# Don't forget to add your username to the URL if necessary!
# svn-server svn://anonsvn.kde.org/home/kde
# This controls the configure flags passed to every module (except qt-copy) by
# default. If you have module-specific configure flags, they will be placed
# after these flags to allow the module setting to override the global setting.
# This setting only applies to KDE 3 modules.
configure-flags --enable-debug
# KDE 4 uses CMake. The equivalent to configure-flags is cmake-options. BUT
# the same options will not work, CMake expects them in a different format.
# You should probably not need to use cmake-options however. KDE4_BUILD_TESTS
# is provided as an example.
# cmake-options -DKDE4_BUILD_TESTS:BOOL=ON
# These are the compilation flags to use by default when compiling KDE.
# gcc supports a -march option in order to generate specific code for pentium4, athlon-xp,
# etc. See the gcc man page for more information.
# cxxflags -pipe -march=i686 # For standard 32-bit systems.
cxxflags -pipe
# KDE has one of the most extensive translation packages in the world. They
# are stored in the l10n module. kdesvn-build can automatically try to build
# and install languages for you, using this parameter. It should be a list
# of languages to build and install. This option requires the language code
# as present in l10n. You can look these codes up at
# http://i18n.kde.org/teams/
# kde-languages de # German
# kde-languages fr # French
# kde-languages en_GB cs # British English and Czech
# These are the default options passed to the make command. The default tries
# to build with 2 parallel compiles. If you are using distcc or have SMP, you
# should experiment with setting this value higher for best performance.
# make-options -j2
# These are the default options passed to unsermake, which supports some
# options not present with make. The default tries to run 2 compile jobs
# in parallel. The -p option is used to display progress information.
# unsermake can only be used with KDE 3.
# unsermake-options --compile-jobs=2 -p
# unsermake is used by default for KDE 3 modules. However, you may get tired
# of kdesvn-build updating unsermake all the time. In that case, uncomment the
# following. NOTE: You are responsible for updating unsermake after that by
# going to its directory and running 'svn up' when needed. If you have not yet
# downloaded unsermake let kdesvn-build update it before uncommenting.
# use-unsermake self
# You can use the set-env option to add values to the build environment.
# set-env LDFLAGS -Wl,-O1 # Optimize the linker, takes longer.
# If you use software which requires pkg-config, and you need to add entries
# to your pkg-config path, you can also use set-env for that. Some broken
# systems require you to set this to find e.g. glib.
# set-env PKG_CONFIG_PATH /opt/gnome/lib/pkgconfig
end global
# qt-copy is a copy of Trolltech's Qt, optionally with some bugfixes and
# optimizations added. It is the easiest way to get Qt if you don't already
# have it (and you don't want to use your distro's tools to install it.)
module qt-copy
# Configure flags. If you use Qt 3, then uncomment the lines
# below the Qt 3 option line (by removing the # at the beginning) and
# comment the Qt 4 lines which follow.
configure-flags -qt-gif -no-exceptions -fast -qdbus \
-nomake examples -nomake demos
# QT 3 OPTIONS
# configure-flags -system-zlib -qt-gif -system-libjpeg -system-libpng \
# -no-exceptions -fast -thread -debug
# make-options -j2 sub-src sub-tools # Build faster, no examples built
apply-qt-patches true # Works with Qt 3 and 4, recommended as well.
# make-options -j2
end module
# arts is the KDE sound library. It is not expected to be used by the time
# KDE 4 is released.
#module arts
#end module
# kdesupport contains taglib and QCA, and the Strigi library required for
# kdelibs in KDE 4. taglib is required for JuK, amarok, and the meta info
# reader for music files in Konqueror.
module kdesupport
end module
# kdelibs are the base KDE libraries needed by all KDE applications.
module kdelibs
configure-flags --enable-sendfile --enable-mitshm
# KDE 4 uses CMake, if you need to pass options to the cmake command, use this
# option:
# cmake-options -DKDE4_BUILD_TESTS:BOOL=ON
# If you're a programmer you may want to build the API docs. Note that
# it takes some time, and DOES NOT WORK with unsermake (or CMake, yet). :(
# apidox true
end module
# If you are not using KDE 4 then uncomment or remove this module. It is required
# before kdebase in KDE 4.
module kdepimlibs
end module
# kdebase contains useful general-purpose programs, normally people would
# expect a usable desktop to have these.
module kdebase
configure-flags --with-pam --with-shadow
end module
# kdemultimedia contains JuK, noatun, Kaboodle, and other KDE multimedia
# applications. It does not include amarok, which is in extragear/multimedia
module kdemultimedia
end module
# ... Well, they're games. ;)
module kdegames
end module
## Note: The following modules may not have been ported to KDE 4 yet, and may
# have changed significantly from their KDE 3 counterparts as well. Because
# of this, they are commented out, uncomment it if you want to build it.
# kdesdk is a useful module for software developers. It is where kdesvn-build
# is developed.
#module kdesdk
#end module
# kdenetwork has Kopete and other useful applications for the Internet and
# other networks.
#module kdenetwork
#end module
# kdeadmin has system administration tools for your computer.
#module kdeadmin
# configure-flags --with-shadow --with-pam=yes
#end module
# kdebindings is useful for software developers, and for those who wish to run
# some KDE programs that don't use C++. The python bindings are not included
# by default as they never build for me. If you'd like to build all the
# bindings, comment out the checkout-only option below.
#
# This module appears to be on its way to being ported to Qt 4, stay tuned.
#module kdebindings
# checkout-only admin dcopc kalyptus smoke qtruby korundum kjsembed dcoppython
# kdebindings will probably need to use the following option to install successfully.
# You must configure the sudo program first to allow for passwordless operation.
# make-install-prefix sudo
#end module
# kdepim contains KMail, Kontact, KOrganizer, and other insanely useful
# programs that help you keep track of things.
#module kdepim
# configure-flags --disable-exchange
#end module
# kdeutils has miscellaneous programs which can be useful. You probably won't
# die if you remove this from the config file though.
#module kdeutils
#end module
# kdegraphics contains various programs useful for graphics editing. It
# doesn't include Krita, which is part of KOffice, but it is worth it just for
# KolourPaint.
#module kdegraphics
#end module
# kdeaddons are nifty additions to some programs in other KDE modules. For
# example, there are addons for Konqueror, extra Kicker applets, and Noatun
# plugins.
#module kdeaddons
#end module
# Contains nifty diversions of time, which generally aren't games.
#module kdetoys
#end module
# Educational programs. Some are actually quite fun even if you're not trying
# to learn anything.
#module kdeedu
#end module
# The KDE Office Suite. Includes a pretty expansive collection of programs.
# It is rather large, so you can cut download and build times by removing it
# from this file.
module koffice
branch 1.6 # The last released version for KDE 3.
end module
# The KDevelop IDE, useful for developing all kinds of programs. If you don't
# plan on being a software developer you can save time by removing this from
# your configuration.
#
# Note: KDevelop appears to have a port started towards KDE 4. It may be
# usable by now.
#module kdevelop
# use-unsermake false
#end module
# Includes Quanta Plus and other web design tools.
#module kdewebdev
#end module
# Modules in extragear and playground can also be added.
# Note: As of this writing, extragear and playground are for KDE 3.x only,
# so it is commented out.
#
# To see what you can find in the various modules, browse
# http://websvn.kde.org/trunk/extragear and
# http://websvn.kde.org/trunk/playground
# Includes various libraries needed by other applications in extragear.
module extragear/libs
# If you don't like the default name that kdesvn-build gives modules on-disk,
# you can use dest-dir to change it.
dest-dir extragear-libs
end module
# Includes the popular K3B and Amarok programs.
module extragear/multimedia
end module
# Includes various photo management applications.
#module extragear/graphics
# checkout-only digikamimageplugins digikam gwenview kimdaba
#end module
# module extragear/network
# # Options like checkout-only should work as before.
# checkout-only konversation
# end module
# module playground/games
# end module
# Add more modules as needed.-
hawake
- Linux 0.x

- Messaggi: 36
- Iscritto il: mer 5 set 2007, 10:17
- Località: A tre micron dal BIOS
- Contatta:
Eccovi cosa fà e dice...:
kdeprova@FallenStar:~/kdesvn-build-1.4.1$ kdesvn-build
*** kdesvn-build appears to be running. Do you want to:
(Q)uit, (P)roceed anyways?: P
* kdesvn-build run in progress by user request.
Script started processing at Mon Sep 10 16:48:26 2007
<<< Updating Subversion Directories >>>
Updating kdenonbeta
Updating unsermake
Updating qt-copy
Updating kdesupport
Updating kdelibs
Updating kdepimlibs
Updating kdebase
Updating kdemultimedia
Updating kdegames
<<< Update Complete >>>
<<< Build Process >>>
!! You're building qt-copy, but QTDIR isn't set to use qt-copy!
!! Please set your qtdir variable in the global section of your
!! /home/kdeprova/.kdesvn-buildrc to ~/kdesvn/qt-copy
Building qt-copy (1/7)
Compiling, attempt 1...
Couldn't build, going to try again just in case.
Took 0 seconds.
Building qt-copy (1/7)
Compiling, attempt 2...
Still couldn't build, recreating build system (builddir is safe).
Took 0 seconds of time.
Building qt-copy (1/7)
Preparing build system for qt-copy.
Applying recommended Qt patches.
GPL license selected for Qt. See /home/kdeprova/kdesvn/qt-copy/LICENSE.GPL
Running configure...
Unable to configure qt-copy! No such file or directory
Overall time for qt-copy was 4 seconds.
Building kdesupport (2/7)
Preparing build system for kdesupport.
Executing rm -rf /home/kdeprova/kdesvn/build/kdesupport
Old build system cleaned, starting new build system.
Unable to create build system for kdesupport No such file or directory
Unable to create configure system from checkout. No such file or directory
Overall time for kdesupport was 10 seconds.
Building kdelibs (3/7)
Preparing build system for kdelibs.
Executing rm -rf /home/kdeprova/kdesvn/build/kdelibs
Old build system cleaned, starting new build system.
Unable to create build system for kdelibs No such file or directory
Unable to create configure system from checkout. No such file or directory
Overall time for kdelibs was 13 seconds.
Building kdepimlibs (4/7)
Preparing build system for kdepimlibs.
Executing rm -rf /home/kdeprova/kdesvn/build/kdepimlibs
Old build system cleaned, starting new build system.
Unable to create build system for kdepimlibs No such file or directory
Unable to create configure system from checkout. No such file or directory
Overall time for kdepimlibs was 0 seconds.
Building kdebase (5/7)
Preparing build system for kdebase.
Executing rm -rf /home/kdeprova/kdesvn/build/kdebase
Old build system cleaned, starting new build system.
Unable to create build system for kdebase No such file or directory
Unable to create configure system from checkout. No such file or directory
Overall time for kdebase was 34 seconds.
Building kdemultimedia (6/7)
Compiling, attempt 1...
Couldn't build, going to try again just in case.
Took 45 seconds.
Building kdemultimedia (6/7)
Compiling, attempt 2...
Still couldn't build, recreating build system (builddir is safe).
Took 12 seconds of time.
Building kdemultimedia (6/7)
Preparing build system for kdemultimedia.
Running configure...
Compiling, attempt 3...
Unable to build kdemultimedia!
Took 2 minutes, and 49 seconds.
Overall time for kdemultimedia was 3 minutes, and 46 seconds.
Building kdegames (7/7)
Compiling, attempt 1...
Couldn't build, going to try again just in case.
Took 6 seconds.
Building kdegames (7/7)
Compiling, attempt 2...
Still couldn't build, recreating build system (builddir is safe).
Took 5 seconds of time.
Building kdegames (7/7)
Preparing build system for kdegames.
Running configure...
Compiling, attempt 3...
Unable to build kdegames!
Took 2 minutes, and 14 seconds.
Overall time for kdegames was 2 minutes, and 25 seconds.
<<< Build Done >>>
<<< PACKAGES FAILED TO BUILD >>>
qt-copy - ~/kdesvn/log/2007-09-10-02/qt-copy/configure.log
kdesupport - ~/kdesvn/log/2007-09-10-02/kdesupport/build-system.log
kdelibs - ~/kdesvn/log/2007-09-10-02/kdelibs/build-system.log
kdepimlibs - ~/kdesvn/log/2007-09-10-02/kdepimlibs/build-system.log
kdebase - ~/kdesvn/log/2007-09-10-02/kdebase/build-system.log
kdemultimedia - ~/kdesvn/log/2007-09-10-02/kdemultimedia/build-3.log
kdegames - ~/kdesvn/log/2007-09-10-02/kdegames/build-3.log
Script finished processing at Mon Sep 10 16:59:44 2007
Your logs are saved in /home/kdeprova/kdesvn/log/2007-09-10-02
kdeprova@FallenStar:~/kdesvn-build-1.4.1$
Scrivi nel .profile le righe
Rimuovi il file di configurazione che hai creato e lui userà le impostazioni di default che vanno più che bene.
Mi sa che una volta fatto questo dovrebbe anche riuscire a configurare e compilare le qt4, e quindi anche tutto il resto.
Codice: Seleziona tutto
export LD_LIBRARY_PATH=~/kde/lib:~/kdesvn/build/qt-copy/lib:$LD_LIBRARY_PATH
export PATH=~/kde/bin:~/kdesvn/build/qt-copy/bin:$PATH
export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:~/local/lib/pkgconfig
export KDEDIR=$HOME/kde
export KDEHOME=$HOME/.kde4
export KDEDIRS=$KDEDIR
export PKG_CONFIG_PATH=$KDEDIR/lib/pkgconfig:$PKG_CONFIG_PATH
export DISPLAY=:0.0Mi sa che una volta fatto questo dovrebbe anche riuscire a configurare e compilare le qt4, e quindi anche tutto il resto.
-
hawake
- Linux 0.x

- Messaggi: 36
- Iscritto il: mer 5 set 2007, 10:17
- Località: A tre micron dal BIOS
- Contatta:
Dove lo trovo il file .profile? Ho provato con locate, ma mi indica alcuni file nelle directory share e doc...dapuzz ha scritto:Scrivi nel .profile le righeRimuovi il file di configurazione che hai creato e lui userà le impostazioni di default che vanno più che bene.Codice: Seleziona tutto
export LD_LIBRARY_PATH=~/kde/lib:~/kdesvn/build/qt-copy/lib:$LD_LIBRARY_PATH export PATH=~/kde/bin:~/kdesvn/build/qt-copy/bin:$PATH export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:~/local/lib/pkgconfig export KDEDIR=$HOME/kde export KDEHOME=$HOME/.kde4 export KDEDIRS=$KDEDIR export PKG_CONFIG_PATH=$KDEDIR/lib/pkgconfig:$PKG_CONFIG_PATH export DISPLAY=:0.0
Mi sa che una volta fatto questo dovrebbe anche riuscire a configurare e compilare le qt4, e quindi anche tutto il resto.
grazie ancora!
-
hawake
- Linux 0.x

- Messaggi: 36
- Iscritto il: mer 5 set 2007, 10:17
- Località: A tre micron dal BIOS
- Contatta:
Niente... maledizione... ecco cosa mi dice alla fine:
Ma che altro vuole questo script!?!?! Mannaggia... vuole i permessi di root? O cosa?
Codice: Seleziona tutto
<<< PACKAGES FAILED TO BUILD >>>
qt-copy - ~/kdesvn/log/2007-09-22-01/qt-copy/build-1.log
arts - ~/kdesvn/log/2007-09-22-01/arts/configure.log
kdesupport - ~/kdesvn/log/2007-09-22-01/kdesupport/build-system.log
kdelibs - ~/kdesvn/log/2007-09-22-01/kdelibs/configure.log
kdebase - ~/kdesvn/log/2007-09-22-01/kdebase/configure.log
kdeartwork - ~/kdesvn/log/2007-09-22-01/kdeartwork/configure.log
kdemultimedia - ~/kdesvn/log/2007-09-22-01/kdemultimedia/configure.log
kdepim - ~/kdesvn/log/2007-09-22-01/kdepim/configure.log
kdeutils - ~/kdesvn/log/2007-09-22-01/kdeutils/configure.log
kdegraphics - ~/kdesvn/log/2007-09-22-01/kdegraphics/configure.log
kdegames - ~/kdesvn/log/2007-09-22-01/kdegames/configure.log
kdetoys - ~/kdesvn/log/2007-09-22-01/kdetoys/configure.log
kdeedu - ~/kdesvn/log/2007-09-22-01/kdeedu/configure.log
kdeaddons - ~/kdesvn/log/2007-09-22-01/kdeaddons/configure.log
Script finished processing at Sat Sep 22 16:13:48 2007
Your logs are saved in /home/kdeprova/kdesvn/log/2007-09-22-01
kdeprova@FallenStar:~/kdesvn-build-1.4.1$ su -c "kdesvn-build"
Password:
Sorry.
kdeprova@FallenStar:~/kdesvn-build-1.4.1$no, non servono i permessi di root. Ma è strano che cerchi di compilare arts, su kde4 non c'è più. Perchè non provi a ripartire dall'inizio?
Cancelli l'utente kdeprova e la sua home: userdel -r kdeproca
Crei l'utente kdeprova: adduser kdeprova
Accedi come kdeprova: su - kdeprova
Crei il file .profile con quelle informazioni che ti ho dato prima
Scarichi kdesvnbuild: wget http://kdesvn-build.kde.org/releases/kd ... .1.tar.bz2
Estrai kdesvn-build: tar xvf kdesvn-build-1.4.1.tar.bz2
Entri nella directory: cd kdesvn-build-1.4.1
e lo lanci: ./kdesvn-build
Visto che non ha il file di configurazione dovrebbe dirti
e poi continuare normalmente la compilazione di tutti i moduli.
PS: se fallsice l'installazione delle qt-copy allora puoi interrompere lo script con control+c visto che senza le qt non puoi compilare il resto.
Cancelli l'utente kdeprova e la sua home: userdel -r kdeproca
Crei l'utente kdeprova: adduser kdeprova
Accedi come kdeprova: su - kdeprova
Crei il file .profile con quelle informazioni che ti ho dato prima
Scarichi kdesvnbuild: wget http://kdesvn-build.kde.org/releases/kd ... .1.tar.bz2
Estrai kdesvn-build: tar xvf kdesvn-build-1.4.1.tar.bz2
Entri nella directory: cd kdesvn-build-1.4.1
e lo lanci: ./kdesvn-build
Visto che non ha il file di configurazione dovrebbe dirti
Codice: Seleziona tutto
knut@SlackWare:~/kdesvn-build-1.4.1$ ./kdesvn-build
Unable to open configuration file!
We looked for:
./kdesvn-buildrc
/home/knut/.kdesvn-buildrc
kdesvn-build will continue using a default set of options. These options may
not apply to you, so feel free to visit the kdesvn-build homepage
http://kdesvn-build.kde.org/
and use the configuration file generator to guide you through the process of
creating a config file to customize your kdesvn-build process.PS: se fallsice l'installazione delle qt-copy allora puoi interrompere lo script con control+c visto che senza le qt non puoi compilare il resto.
-
hawake
- Linux 0.x

- Messaggi: 36
- Iscritto il: mer 5 set 2007, 10:17
- Località: A tre micron dal BIOS
- Contatta:
Eseguite alla lettera tutte le tue istruzioni ma...
...che succede ora?

Codice: Seleziona tutto
kdeprova@FallenStar:~/kdesvn-build-1.4.1$ ./kdesvn-build
Unable to open configuration file!
We looked for:
./kdesvn-buildrc
/home/kdeprova/.kdesvn-buildrc
kdesvn-build will continue using a default set of options. These options may
not apply to you, so feel free to visit the kdesvn-build homepage
http://kdesvn-build.kde.org/
and use the configuration file generator to guide you through the process of
creating a config file to customize your kdesvn-build process.
Script started processing at Fri Sep 28 17:11:18 2007
<<< Updating Subversion Directories >>>
Installing KDE SSL signature for Subversion. This is to avoid
Subversion warnings about KDE's self-signed SSL certificate for svn.kde.org
Downloading snapshot for qt-copy
* Can't open Net::HTTP module, skipping check for module snapshot.
Unable to download snapshot for module qt-copy
Checking out qt-copy
14183 files were added.
Downloading snapshot for kdesupport
Unable to download snapshot for module kdesupport
Checking out kdesupport