Pagina 1 di 1
kdewebdev3 sulla nostra slackware a 64bit...
Inviato: ven 2 ott 2009, 20:58
da danix
come da oggetto, mi serve avere di nuovo quanta+ e siccome ho di recente fatto il salto a 64bit (e mi sto trovando da dio), mi chiedevo come fare... chi ha più esperienza su questo ramo mi saprebbe dare qualche dritta??
Grazie mille a tutti

Re: kdewebdev3 sulla nostra slackware a 64bit...
Inviato: dom 4 ott 2009, 11:22
da danix
up

Re: kdewebdev3 sulla nostra slackware a 64bit...
Inviato: dom 4 ott 2009, 12:00
da Blallo
allora...ci sono i pacchetti in /extra del cd di kde3compact...installando solo quelli dovresti poi poter installare kdewebdev3...ricordati di ricompilare le qt3 dallo slackbuild di Pat in modo da abilitare l'anti-aliasing
Re: kdewebdev3 sulla nostra slackware a 64bit...
Inviato: dom 4 ott 2009, 12:03
da conraid
Re: kdewebdev3 sulla nostra slackware a 64bit...
Inviato: dom 11 ott 2009, 13:25
da danix
Scusate se non mi sono fatto più sentire sull'argomento...
Codice: Seleziona tutto
tidy/
tidy/CVSROOT/
tidy/CVSROOT/checkoutlist
tidy/CVSROOT/commitinfo
tidy/CVSROOT/config
tidy/CVSROOT/cvswrappers
tidy/CVSROOT/editinfo
tidy/CVSROOT/loginfo
tidy/CVSROOT/modules
tidy/CVSROOT/notify
tidy/CVSROOT/rcsinfo
tidy/CVSROOT/taginfo
tidy/CVSROOT/verifymsg
tidy/build/
tidy/build/gmake/
tidy/build/gmake/Makefile
tidy/build/gmake/readme.txt
tidy/build/readme.txt
tidy/build/gnuauto/
tidy/build/gnuauto/console/
tidy/build/gnuauto/console/Makefile.am
tidy/build/gnuauto/Makefile.am
tidy/build/gnuauto/configure.in
tidy/build/gnuauto/readme.txt
tidy/build/gnuauto/setup.sh
tidy/build/gnuauto/include/
tidy/build/gnuauto/include/Makefile.am
tidy/build/gnuauto/src/
tidy/build/gnuauto/src/Makefile.am
tidy/build/msvc/
[...]
tidy/test/input/in_679135.html
tidy/test/input/in_680664.xhtml
tidy/test/input/in_688746.html
tidy/test/input/in_695408.html
tidy/test/input/in_696799.html
tidy/test/input/in_706260.html
tidy/test/input/in_765852.html
tidy/test/input/in_795643-1.html
tidy/test/input/in_795643-2.html
tidy/test/input/in_836462-2.html
tidy/test/input/in_836462-3.html
tidy/test/input/in_836462.html
tidy/test/input/in_837023.html
tidy/test/input/in_978947.html
tidy/test/input/in_996484.html
tidy/test/output/
tidy/test/output/out_427820.html
tidy/test/output/out_427826.html
tidy/test/output/out_431721.html
tidy/test/output/out_480701.html
tidy/test/output/out_533233.html
tidy/test/output/out_540571.html
Generating the build system in /tmp/tidy
copying files into place: cd build/gnuauto && cp -R -f * /tmp/tidy
running: libtoolize --force --copy
You should add the contents of `/usr/share/aclocal/libtool.m4' to `aclocal.m4'.
running: aclocal
/usr/share/aclocal/imlib.m4:9: warning: underquoted definition of AM_PATH_IMLIB
/usr/share/aclocal/imlib.m4:9: run info '(automake)Extending aclocal'
/usr/share/aclocal/imlib.m4:9: or see http://sources.redhat.com/automake/automake.html#Extending-aclocal
running: automake -a -c --foreign
configure.in:49: installing `./install-sh'
configure.in:49: installing `./missing'
console/Makefile.am: installing `./depcomp'
running: autoconf
If the above commands were successful you should now be able
to build in the usual way:
$ ./configure --prefix=/usr
$ make
$ make install
to get a list of configure options type: ./configure --help
Alternatively, you should be able to build outside of the source
tree. e.g.:
$ mkdir ../build-tidy
$ cd ../build-tidy
$ ../tidy/configure --prefix=/usr
$ make
$ make install
configure: WARNING: you should use --build, --host, --target
checking for a BSD-compatible install... /bin/ginstall -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for i486-slackware-linux-gcc... no
checking for gcc... gcc
checking for C compiler default output file name...
configure: error: in `/tmp/tidy':
configure: error: C compiler cannot create executables
See `config.log' for more details.
make: *** No targets specified and no makefile found. Stop.
Building kdewebdev-3.5.10.tar.bz2...
tar: /home/danix/downloads/kdewebdev3/kdewebdev-3.5.10.tar.bz2: funzione "open" non riuscita: No such file or directory
tar: Errore irrimediabile: uscita immediata
tar: Child returned status 2
tar: Uscita con stato di fallimento in base agli errori precedenti
Questo è il risultato del tentativo fatto con lo slackbuild di Corrado
Ho modificato solo $ARCH e $TARGET ad x86_64, $CPUOPT ho messo "-O2 -fPIC" nello slackbuild di kdewebdev3 e nient'altro... dove sta l'errore??
Re: kdewebdev3 sulla nostra slackware a 64bit...
Inviato: dom 11 ott 2009, 13:28
da conraid
passa ARCH="x86_64" direttamente dallo script di kdewebdev anche per tidy
Codice: Seleziona tutto
# First, build and install Tidy:
( cd tidy ; ARCH="x86_64" sh ./tidy.build $PKG )
poi guarda se ci vuole libdir etc...
io ho preso i vecchi build i Pat, non li ho fatti io, e Pat a quei tempi non ci pensava proprio a fare la compatibilità a 64bit
Magari prendi quelli nuovi che ha messo per kde3, e cambia il percorso di prefix
Re: kdewebdev3 sulla nostra slackware a 64bit...
Inviato: dom 11 ott 2009, 13:55
da danix
gli script nuovi di PJV sono uguali a quelli che hai tu, comunque ho seguito il tuo consiglio ma mi restituisce sempre un errore
Codice: Seleziona tutto
mv -f .deps/tidy.Tpo .deps/tidy.Po
/bin/sh ../libtool --tag=CC --mode=link x86_64-slackware-linux-gcc -O2 -O2 -Wall -Wno-switch -Wno-parentheses -Wno-unused -o tidy tidy.o ../src/libtidy.la
x86_64-slackware-linux-gcc -O2 -O2 -Wall -Wno-switch -Wno-parentheses -Wno-unused -o .libs/tab2space tab2space.o ../src/.libs/libtidy.so
creating tab2space
x86_64-slackware-linux-gcc -O2 -O2 -Wall -Wno-switch -Wno-parentheses -Wno-unused -o .libs/tidy tidy.o ../src/.libs/libtidy.so
creating tidy
make[1]: Leaving directory `/tmp/tidy/console'
Making all in include
make[1]: Entering directory `/tmp/tidy/include'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/tmp/tidy/include'
make[1]: Entering directory `/tmp/tidy'
make[1]: Nothing to be done for `all-am'.
make[1]: Leaving directory `/tmp/tidy'
Making install in src
make[1]: Entering directory `/tmp/tidy/src'
make[2]: Entering directory `/tmp/tidy/src'
test -z "/usr/lib" || /bin/mkdir -p "/tmp/tgz/package-kdewebdev/usr/lib"
/bin/sh ../libtool --mode=install /bin/ginstall -c 'libtidy.la' '/tmp/tgz/package-kdewebdev/usr/lib/libtidy.la'
/bin/ginstall -c .libs/libtidy-0.99.so.0.0.0 /tmp/tgz/package-kdewebdev/usr/lib/libtidy-0.99.so.0.0.0
(cd /tmp/tgz/package-kdewebdev/usr/lib && { ln -s -f libtidy-0.99.so.0.0.0 libtidy-0.99.so.0 || { rm -f libtidy-0.99.so.0 && ln -s libtidy-0.99.so.0.0.0 libtidy-0.99.so.0; }; })
(cd /tmp/tgz/package-kdewebdev/usr/lib && { ln -s -f libtidy-0.99.so.0.0.0 libtidy.so || { rm -f libtidy.so && ln -s libtidy-0.99.so.0.0.0 libtidy.so; }; })
/bin/ginstall -c .libs/libtidy.lai /tmp/tgz/package-kdewebdev/usr/lib/libtidy.la
libtool: install: warning: remember to run `libtool --finish /usr/lib'
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/tmp/tidy/src'
make[1]: Leaving directory `/tmp/tidy/src'
Making install in console
make[1]: Entering directory `/tmp/tidy/console'
make[2]: Entering directory `/tmp/tidy/console'
test -z "/usr/bin" || /bin/mkdir -p "/tmp/tgz/package-kdewebdev/usr/bin"
/bin/sh ../libtool --mode=install /bin/ginstall -c 'tidy' '/tmp/tgz/package-kdewebdev/usr/bin/tidy'
/bin/ginstall -c .libs/tidy /tmp/tgz/package-kdewebdev/usr/bin/tidy
/bin/sh ../libtool --mode=install /bin/ginstall -c 'tab2space' '/tmp/tgz/package-kdewebdev/usr/bin/tab2space'
/bin/ginstall -c .libs/tab2space /tmp/tgz/package-kdewebdev/usr/bin/tab2space
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/tmp/tidy/console'
make[1]: Leaving directory `/tmp/tidy/console'
Making install in include
make[1]: Entering directory `/tmp/tidy/include'
make[2]: Entering directory `/tmp/tidy/include'
make[2]: Nothing to be done for `install-exec-am'.
test -z "/usr/include" || /bin/mkdir -p "/tmp/tgz/package-kdewebdev/usr/include"
/bin/ginstall -c -m 644 'platform.h' '/tmp/tgz/package-kdewebdev/usr/include/platform.h'
/bin/ginstall -c -m 644 'tidy.h' '/tmp/tgz/package-kdewebdev/usr/include/tidy.h'
/bin/ginstall -c -m 644 'tidyenum.h' '/tmp/tgz/package-kdewebdev/usr/include/tidyenum.h'
/bin/ginstall -c -m 644 'buffio.h' '/tmp/tgz/package-kdewebdev/usr/include/buffio.h'
make[2]: Leaving directory `/tmp/tidy/include'
make[1]: Leaving directory `/tmp/tidy/include'
make[1]: Entering directory `/tmp/tidy'
make[2]: Entering directory `/tmp/tidy'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/tmp/tidy'
make[1]: Leaving directory `/tmp/tidy'
Making install in src
make[1]: Entering directory `/tmp/tidy/src'
make[2]: Entering directory `/tmp/tidy/src'
test -z "/usr/lib" || /bin/mkdir -p "/usr/lib"
/bin/sh ../libtool --mode=install /bin/ginstall -c 'libtidy.la' '/usr/lib/libtidy.la'
/bin/ginstall -c .libs/libtidy-0.99.so.0.0.0 /usr/lib/libtidy-0.99.so.0.0.0
(cd /usr/lib && { ln -s -f libtidy-0.99.so.0.0.0 libtidy-0.99.so.0 || { rm -f libtidy-0.99.so.0 && ln -s libtidy-0.99.so.0.0.0 libtidy-0.99.so.0; }; })
(cd /usr/lib && { ln -s -f libtidy-0.99.so.0.0.0 libtidy.so || { rm -f libtidy.so && ln -s libtidy-0.99.so.0.0.0 libtidy.so; }; })
/bin/ginstall -c .libs/libtidy.lai /usr/lib/libtidy.la
PATH="$PATH:/sbin" ldconfig -n /usr/lib
----------------------------------------------------------------------
Libraries have been installed in:
/usr/lib
If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,--rpath -Wl,LIBDIR' linker flag
- have your system administrator add LIBDIR to `/etc/ld.so.conf'
See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/tmp/tidy/src'
make[1]: Leaving directory `/tmp/tidy/src'
Making install in console
make[1]: Entering directory `/tmp/tidy/console'
make[2]: Entering directory `/tmp/tidy/console'
test -z "/usr/bin" || /bin/mkdir -p "/usr/bin"
/bin/sh ../libtool --mode=install /bin/ginstall -c 'tidy' '/usr/bin/tidy'
/bin/ginstall -c .libs/tidy /usr/bin/tidy
/bin/sh ../libtool --mode=install /bin/ginstall -c 'tab2space' '/usr/bin/tab2space'
/bin/ginstall -c .libs/tab2space /usr/bin/tab2space
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/tmp/tidy/console'
make[1]: Leaving directory `/tmp/tidy/console'
Making install in include
make[1]: Entering directory `/tmp/tidy/include'
make[2]: Entering directory `/tmp/tidy/include'
make[2]: Nothing to be done for `install-exec-am'.
test -z "/usr/include" || /bin/mkdir -p "/usr/include"
/bin/ginstall -c -m 644 'platform.h' '/usr/include/platform.h'
/bin/ginstall -c -m 644 'tidy.h' '/usr/include/tidy.h'
/bin/ginstall -c -m 644 'tidyenum.h' '/usr/include/tidyenum.h'
/bin/ginstall -c -m 644 'buffio.h' '/usr/include/buffio.h'
make[2]: Leaving directory `/tmp/tidy/include'
make[1]: Leaving directory `/tmp/tidy/include'
make[1]: Entering directory `/tmp/tidy'
make[2]: Entering directory `/tmp/tidy'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/tmp/tidy'
make[1]: Leaving directory `/tmp/tidy'
Building kdewebdev-3.5.10.tar.bz2...
tar: /home/danix/downloads/kdewebdev3/kdewebdev-3.5.10.tar.bz2: funzione "open" non riuscita: No such file or directory
tar: Errore irrimediabile: uscita immediata
tar: Child returned status 2
tar: Uscita con stato di fallimento in base agli errori precedenti
che fo'??
Re: kdewebdev3 sulla nostra slackware a 64bit...
Inviato: dom 11 ott 2009, 14:01
da conraid
ma i sorgenti ce li hai nella directory?
comunque per tidy metti anche --libdir nel configure
Re: kdewebdev3 sulla nostra slackware a 64bit...
Inviato: dom 11 ott 2009, 15:02
da Vic Steele
Oltre a scaricare il
sorgente, dallo slackbuild di conraid cambia la riga di CPUOPT con:
ed, importante, non dimenticare la direttiva di libdir.
Re: kdewebdev3 sulla nostra slackware a 64bit...
Inviato: mar 13 ott 2009, 18:25
da danix
il sorgente è al suo posto, per --libdir che devo mettere??
Re: kdewebdev3 sulla nostra slackware a 64bit...
Inviato: mar 13 ott 2009, 18:29
da conraid
beh, mettendo le cose in /opt qualcosa come
--libdir=/opt/kde3/lib64
per tidy dipende da come hai dichiarato prefix, se usr allora /usr/lib64
ma guarda qualche slackbuild no?

Re: kdewebdev3 sulla nostra slackware a 64bit...
Inviato: mar 13 ott 2009, 18:30
da Vic Steele
--libdir=/usr/lib${LIBDIRSUFFIX}
Dove LIBDIRSUFFIX=64 la dichiari da qualche parte (tipicamente si fa in un if [ "$ARCH" = "x86_64" ]; ).
Nulla ti vieta di scrivere --libdir=/usr/lib64, se poi non hai intenzione di distribuire lo slackbuild o ricompilarlo su altre macchine... ma se fai così, in caso dovessi poi compilare su un x86, basterebbe solo cambiare il flag ARCH senza cambiare o compromettere nient'altro.