[Risolto] Linux sul mio PC: Il Ritorno... è Gentoo!

Sistemi operativi Linux e software open source
Rispondi
Avatar utente
Zievatron
Messaggi: 1657
Iscritto il: mercoledì 21 dicembre 2011, 23:49

Re: Linux sul mio PC: Il Ritorno... è Gentoo!

Messaggio da Zievatron »

conoscenza ha scritto:Quando si inceppa... posta tutto...tranne le scritte di compilazione... ;)
Tutto cosa?
Le scritte di compilazione quali sono? :hmm:

Ecco il blocco:

Codice: Seleziona tutto

>>> Emerging (11 of 55) net-nds/openldap-2.4.28-r1
 * openldap-2.4.28.tgz RMD160 SHA1 SHA256 size ;-) ...                   [ ok ]
 * rfc2307bis.schema-20100722 RMD160 SHA1 SHA256 size ;-) ...            [ ok ]
 * ERROR: net-nds/openldap-2.4.28-r1 failed (setup phase):
 *   To build the ldapc++ library you must emerge openldap with sasl support
 * 
 * Call stack:
 *                   ebuild.sh, line  85:  Called pkg_setup
 *   openldap-2.4.28-r1.ebuild, line 215:  Called die
 * The specific snippet of code:
 *   		die "To build the ldapc++ library you must emerge openldap with sasl support"
 * 
 * If you need support, post the output of 'emerge --info =net-nds/openldap-2.4.28-r1',
 * the complete build log and the output of 'emerge -pqv =net-nds/openldap-2.4.28-r1'.
 * The complete build log is located at '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/die.env'.
 * S: '/var/tmp/portage/net-nds/openldap-2.4.28-r1/work/openldap-2.4.28'

>>> Failed to emerge net-nds/openldap-2.4.28-r1, Log file:

>>>  '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/build.log'

 * Messages for package sys-auth/polkit-0.104-r1:

 * If you don't use GDM or KDM for logging in,
 * you must start your desktop environment (DE) as follows:
 * 	ck-launch-session $STARTGUI
 * Where $STARTGUI is a DE-starting command such as 'gnome-session'.
 * You should add this to your ~/.xinitrc if you use startx.

 * Messages for package sys-auth/consolekit-0.4.5-r1:

 * You need to restart ConsoleKit to get the new features.
 * This can be done with /etc/init.d/consolekit restart
 * but make sure you do this and then restart your session
 * otherwise you will get access denied for certain actions

 * Messages for package sys-auth/pambase-20101024-r2:

 * Starting from version 20080801, pambase optionally enables
 * SHA512-hashed passwords. For this to work, you need sys-libs/pam-1.0.1
 * built against sys-libs/glibc-2.7 or later.
 * If you don't have support for this, it will automatically fallback
 * to MD5-hashed passwords, just like before.
 * 
 * Please note that the change only affects the newly-changed passwords
 * and that SHA512-hashed passwords will not work on earlier versions
 * of glibc or Linux-PAM.

 * Messages for package net-nds/openldap-2.4.28-r1:

 * ERROR: net-nds/openldap-2.4.28-r1 failed (setup phase):
 *   To build the ldapc++ library you must emerge openldap with sasl support
 * 
 * Call stack:
 *                   ebuild.sh, line  85:  Called pkg_setup
 *   openldap-2.4.28-r1.ebuild, line 215:  Called die
 * The specific snippet of code:
 *   		die "To build the ldapc++ library you must emerge openldap with sasl support"
 * 
 * If you need support, post the output of 'emerge --info =net-nds/openldap-2.4.28-r1',
 * the complete build log and the output of 'emerge -pqv =net-nds/openldap-2.4.28-r1'.
 * The complete build log is located at '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/die.env'.
 * S: '/var/tmp/portage/net-nds/openldap-2.4.28-r1/work/openldap-2.4.28'

 * Regenerating GNU info directory index...
 * Processed 84 info files.

 * IMPORTANT: config file '/etc/pam.d/system-login' needs updating.
 * See the CONFIGURATION FILES section of the emerge
 * man page to learn how to update config files.
Zievatron

Avatar utente
conoscenza
Messaggi: 3821
Iscritto il: venerdì 2 dicembre 2011, 23:27
Località: Parma

Re: Linux sul mio PC: Il Ritorno... è Gentoo!

Messaggio da conoscenza »

Mentre emerge non vedi scorrere tante righe in stile "matrix"?
Quella è la compilazione! Postare quell'output non ha senso!
Ha senso invece postare da dove iniziano gli errori in poi...

Mi fai vedere:
emerge -pqv =net-nds/openldap-2.4.28-r1

Ad ogni modo dai:
etc-update (-5 se te lo chiede)
emerge --sync
emerge --depclean
revdep-rebuild
emerge -DNu world
emerge xfce4-meta
Sono allergico a mele morsicate e a finestre con tende.

Segnalate qui le vostre offerte di smartphone e tablet!!!

Avatar utente
Zievatron
Messaggi: 1657
Iscritto il: mercoledì 21 dicembre 2011, 23:49

Re: Linux sul mio PC: Il Ritorno... è Gentoo!

Messaggio da Zievatron »

Ehm,... Mentre aspettavo, ho provato a ripetere direttamente il solito ciclo di:
etc-update (-5 se te lo chiede)
emerge --sync
revdep-rebuild
emerge xfce4-meta :D

Ora si è fermato quì:

Codice: Seleziona tutto

>>> Emerging (3 of 95) net-nds/openldap-2.4.28-r1
 * openldap-2.4.28.tgz RMD160 SHA1 SHA256 size ;-) ...                   [ ok ]
 * rfc2307bis.schema-20100722 RMD160 SHA1 SHA256 size ;-) ...            [ ok ]
 * ERROR: net-nds/openldap-2.4.28-r1 failed (setup phase):
 *   To build the ldapc++ library you must emerge openldap with sasl support
 * 
 * Call stack:
 *                   ebuild.sh, line  85:  Called pkg_setup
 *   openldap-2.4.28-r1.ebuild, line 215:  Called die
 * The specific snippet of code:
 *   		die "To build the ldapc++ library you must emerge openldap with sasl support"
 * 
 * If you need support, post the output of 'emerge --info =net-nds/openldap-2.4.28-r1',
 * the complete build log and the output of 'emerge -pqv =net-nds/openldap-2.4.28-r1'.
 * The complete build log is located at '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/die.env'.
 * S: '/var/tmp/portage/net-nds/openldap-2.4.28-r1/work/openldap-2.4.28'

>>> Failed to emerge net-nds/openldap-2.4.28-r1, Log file:

>>>  '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/build.log'

 * Messages for package net-nds/openldap-2.4.28-r1:

 * ERROR: net-nds/openldap-2.4.28-r1 failed (setup phase):
 *   To build the ldapc++ library you must emerge openldap with sasl support
 * 
 * Call stack:
 *                   ebuild.sh, line  85:  Called pkg_setup
 *   openldap-2.4.28-r1.ebuild, line 215:  Called die
 * The specific snippet of code:
 *   		die "To build the ldapc++ library you must emerge openldap with sasl support"
 * 
 * If you need support, post the output of 'emerge --info =net-nds/openldap-2.4.28-r1',
 * the complete build log and the output of 'emerge -pqv =net-nds/openldap-2.4.28-r1'.
 * The complete build log is located at '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/die.env'.
 * S: '/var/tmp/portage/net-nds/openldap-2.4.28-r1/work/openldap-2.4.28'

 * GNU info directory index is up-to-date.
Proseguo con l'ultimo ciclo che hai postato. ;)

Edit:
Ecco:

Codice: Seleziona tutto

 # emerge -pqv =net-nds/openldap-2.4.28-r1
[ebuild  N    ] net-nds/openldap-2.4.28-r1  USE="berkdb crypt cxx gnutls icu ipv6 minimal perl ssl syslog tcpd -debug -experimental -iodbc -kerberos -odbc -overlays -samba -sasl (-selinux) -slp -smbkrb5passwd" 
 
xfce si è fermato quì:

Codice: Seleziona tutto

>>> Emerging (3 of 93) net-nds/openldap-2.4.28-r1
 * openldap-2.4.28.tgz RMD160 SHA1 SHA256 size ;-) ...                   [ ok ]
 * rfc2307bis.schema-20100722 RMD160 SHA1 SHA256 size ;-) ...            [ ok ]
 * ERROR: net-nds/openldap-2.4.28-r1 failed (setup phase):
 *   To build the ldapc++ library you must emerge openldap with sasl support
 * 
 * Call stack:
 *                   ebuild.sh, line  85:  Called pkg_setup
 *   openldap-2.4.28-r1.ebuild, line 215:  Called die
 * The specific snippet of code:
 *   		die "To build the ldapc++ library you must emerge openldap with sasl support"
 * 
 * If you need support, post the output of 'emerge --info =net-nds/openldap-2.4.28-r1',
 * the complete build log and the output of 'emerge -pqv =net-nds/openldap-2.4.28-r1'.
 * The complete build log is located at '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/die.env'.
 * S: '/var/tmp/portage/net-nds/openldap-2.4.28-r1/work/openldap-2.4.28'

>>> Failed to emerge net-nds/openldap-2.4.28-r1, Log file:

>>>  '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/build.log'

 * Messages for package net-nds/openldap-2.4.28-r1:

 * ERROR: net-nds/openldap-2.4.28-r1 failed (setup phase):
 *   To build the ldapc++ library you must emerge openldap with sasl support
 * 
 * Call stack:
 *                   ebuild.sh, line  85:  Called pkg_setup
 *   openldap-2.4.28-r1.ebuild, line 215:  Called die
 * The specific snippet of code:
 *   		die "To build the ldapc++ library you must emerge openldap with sasl support"
 * 
 * If you need support, post the output of 'emerge --info =net-nds/openldap-2.4.28-r1',
 * the complete build log and the output of 'emerge -pqv =net-nds/openldap-2.4.28-r1'.
 * The complete build log is located at '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/die.env'.
 * S: '/var/tmp/portage/net-nds/openldap-2.4.28-r1/work/openldap-2.4.28'

 * GNU info directory index is up-to-date.
E mi fermo pure io.
Ad oggi! ;)
Zievatron

Avatar utente
conoscenza
Messaggi: 3821
Iscritto il: venerdì 2 dicembre 2011, 23:27
Località: Parma

Re: Linux sul mio PC: Il Ritorno... è Gentoo!

Messaggio da conoscenza »

Vai ancora:
etc-update (-5 se te lo chiede)
emerge --sync
emerge --depclean
revdep-rebuild
emerge -DNu world
emerge xfce4-meta

Riporta gli errori se ci sono ad ogni comando! ;)
Sono allergico a mele morsicate e a finestre con tende.

Segnalate qui le vostre offerte di smartphone e tablet!!!

Avatar utente
Zievatron
Messaggi: 1657
Iscritto il: mercoledì 21 dicembre 2011, 23:49

Re: Linux sul mio PC: Il Ritorno... è Gentoo!

Messaggio da Zievatron »

Codice: Seleziona tutto

emerge --depclean

 * Depclean may break link level dependencies. Thus, it is
 * recommended to use a tool such as `revdep-rebuild` (from
 * app-portage/gentoolkit) in order to detect such breakage.
 * 
 * Always study the list of packages to be cleaned for any obvious
 * mistakes. Packages that are part of the world set will always
 * be kept.  They can be manually added to this set with
 * `emerge --noreplace <atom>`.  Packages that are listed in
 * package.provided (see portage(5)) will be removed by
 * depclean, even if they are part of the world set.
 * 
 * As a safety measure, depclean will not remove any packages
 * unless *all* required dependencies have been resolved.  As a
 * consequence, it is often necessary to run `emerge --update
 * --newuse --deep @world` prior to depclean.

Calculating dependencies... done!
 * Dependencies could not be completely resolved due to
 * the following required packages not being installed:
 * 
 *   >=gnome-extra/polkit-gnome-0.104 pulled in by:
 *     sys-auth/polkit-0.104-r1
 * 
 *   ~x11-libs/qt-qt3support-4.7.4[-aqua,-debug] pulled in by:
 *     x11-libs/qt-gui-4.7.4-r1
 * 
 *   >=dev-db/libdbi-drivers-0.8.3 pulled in by:
 *     dev-db/libdbi-0.8.3
 * 
 * Have you forgotten to do a complete update prior to depclean? The
 * most comprehensive command for this purpose is as follows:
 * 
 *   emerge --update --newuse --deep --with-bdeps=y @world
 * 
 * Note that the --with-bdeps=y option is not required in many
 * situations. Refer to the emerge manual page (run `man emerge`)
 * for more information about --with-bdeps.
 * 
 * Also, note that it may be necessary to manually uninstall
 * packages that no longer exist in the portage tree, since it may
 * not be possible to satisfy their dependencies.
Mi spieghi la differenza tra asterischi gialli ed asterischi rossi? :)

Uuhh! Questo si è bloccato subito

Codice: Seleziona tutto

emerge -DNu world
Calculating dependencies... done!

>>> Verifying ebuild manifests

>>> Starting parallel fetch

>>> Emerging (1 of 46) net-nds/openldap-2.4.28-r1
 * openldap-2.4.28.tgz RMD160 SHA1 SHA256 size ;-) ...                        [ ok ]
 * rfc2307bis.schema-20100722 RMD160 SHA1 SHA256 size ;-) ...                 [ ok ]
 * ERROR: net-nds/openldap-2.4.28-r1 failed (setup phase):
 *   To build the ldapc++ library you must emerge openldap with sasl support
 * 
 * Call stack:
 *                   ebuild.sh, line  85:  Called pkg_setup
 *   openldap-2.4.28-r1.ebuild, line 215:  Called die
 * The specific snippet of code:
 *   		die "To build the ldapc++ library you must emerge openldap with sasl support"
 * 
 * If you need support, post the output of 'emerge --info =net-nds/openldap-2.4.28-r1',
 * the complete build log and the output of 'emerge -pqv =net-nds/openldap-2.4.28-r1'.
 * The complete build log is located at '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/die.env'.
 * S: '/var/tmp/portage/net-nds/openldap-2.4.28-r1/work/openldap-2.4.28'

>>> Failed to emerge net-nds/openldap-2.4.28-r1, Log file:

>>>  '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/build.log'

 * Messages for package net-nds/openldap-2.4.28-r1:

 * ERROR: net-nds/openldap-2.4.28-r1 failed (setup phase):
 *   To build the ldapc++ library you must emerge openldap with sasl support
 * 
 * Call stack:
 *                   ebuild.sh, line  85:  Called pkg_setup
 *   openldap-2.4.28-r1.ebuild, line 215:  Called die
 * The specific snippet of code:
 *   		die "To build the ldapc++ library you must emerge openldap with sasl support"
 * 
 * If you need support, post the output of 'emerge --info =net-nds/openldap-2.4.28-r1',
 * the complete build log and the output of 'emerge -pqv =net-nds/openldap-2.4.28-r1'.
 * The complete build log is located at '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/die.env'.
 * S: '/var/tmp/portage/net-nds/openldap-2.4.28-r1/work/openldap-2.4.28'
Ed anche questo:

Codice: Seleziona tutto

emerge xfce4-meta
Calculating dependencies... done!

>>> Verifying ebuild manifests

>>> Starting parallel fetch

>>> Emerging (1 of 91) net-nds/openldap-2.4.28-r1
 * openldap-2.4.28.tgz RMD160 SHA1 SHA256 size ;-) ...                        [ ok ]
 * rfc2307bis.schema-20100722 RMD160 SHA1 SHA256 size ;-) ...                 [ ok ]
 * ERROR: net-nds/openldap-2.4.28-r1 failed (setup phase):
 *   To build the ldapc++ library you must emerge openldap with sasl support
 * 
 * Call stack:
 *                   ebuild.sh, line  85:  Called pkg_setup
 *   openldap-2.4.28-r1.ebuild, line 215:  Called die
 * The specific snippet of code:
 *   		die "To build the ldapc++ library you must emerge openldap with sasl support"
 * 
 * If you need support, post the output of 'emerge --info =net-nds/openldap-2.4.28-r1',
 * the complete build log and the output of 'emerge -pqv =net-nds/openldap-2.4.28-r1'.
 * The complete build log is located at '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/die.env'.
 * S: '/var/tmp/portage/net-nds/openldap-2.4.28-r1/work/openldap-2.4.28'

>>> Failed to emerge net-nds/openldap-2.4.28-r1, Log file:

>>>  '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/build.log'

 * Messages for package net-nds/openldap-2.4.28-r1:

 * ERROR: net-nds/openldap-2.4.28-r1 failed (setup phase):
 *   To build the ldapc++ library you must emerge openldap with sasl support
 * 
 * Call stack:
 *                   ebuild.sh, line  85:  Called pkg_setup
 *   openldap-2.4.28-r1.ebuild, line 215:  Called die
 * The specific snippet of code:
 *   		die "To build the ldapc++ library you must emerge openldap with sasl support"
 * 
 * If you need support, post the output of 'emerge --info =net-nds/openldap-2.4.28-r1',
 * the complete build log and the output of 'emerge -pqv =net-nds/openldap-2.4.28-r1'.
 * The complete build log is located at '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/die.env'.
 * S: '/var/tmp/portage/net-nds/openldap-2.4.28-r1/work/openldap-2.4.28'
Qual'è lo scoglio?
Zievatron

Avatar utente
Zievatron
Messaggi: 1657
Iscritto il: mercoledì 21 dicembre 2011, 23:49

Re: Linux sul mio PC: Il Ritorno... è Gentoo!

Messaggio da Zievatron »

Ho provato a ripetere il ciclo di istruzioni, ma non ho fatto neanche mezzo passo avanti.
Però, non vedo nessun rigo che richiede di eseguire un rc-update qualcosa.
Il punto cruciale sembra essere un certo "openldap" con supporto "sasl", ma non so bene come muovermi per cercare di farlo emergere.
Attendo nuove.

Edit.:
Ho esplorato i passi che abbiamo compiuto fin'ora in cerca di un'intuizione.

Ho visto che un po' di passi indietro mi hai chiesto di provare a dare questo comando:

Codice: Seleziona tutto

    USE=sals emerge openldap
Io ho provato e ti ho postato il risultato, comando compreso. Non hai fatto commenti al riguardo. Semplicemente siamo andati avanti.
Ma, riguardalo.
Io nei messaggi di Gentoo leggo "sasl" non "sals", non è che è sbagliato?
Riprovo quel comando con la correzione.
Zievatron

Avatar utente
conoscenza
Messaggi: 3821
Iscritto il: venerdì 2 dicembre 2011, 23:27
Località: Parma

Re: Linux sul mio PC: Il Ritorno... è Gentoo!

Messaggio da conoscenza »

Eccomi!
Oggi giornataccia!!!

Allora hai ragione ho sbagliato a digitare... invertendo le consonanti.
Prova a dare:
USE=sasl emerge openldap
cosa ti risponde?
revdep-rebuild tutto ok?
Sono allergico a mele morsicate e a finestre con tende.

Segnalate qui le vostre offerte di smartphone e tablet!!!

Avatar utente
Zievatron
Messaggi: 1657
Iscritto il: mercoledì 21 dicembre 2011, 23:49

Re: Linux sul mio PC: Il Ritorno... è Gentoo!

Messaggio da Zievatron »

Fatto! con la correzione ha emerso 6 pacchetti su 6 senza nessun messaggio di errore.
Anche revdep-rebuild tutto OK. :)
Zievatron

Avatar utente
conoscenza
Messaggi: 3821
Iscritto il: venerdì 2 dicembre 2011, 23:27
Località: Parma

Re: Linux sul mio PC: Il Ritorno... è Gentoo!

Messaggio da conoscenza »

Zievatron ha scritto:Fatto! con la correzione ha emerso 6 pacchetti su 6 senza nessun messaggio di errore.
Oramai sei più bravo del maestro! ;)

continua con:
etc-update (l'opzione non te la indico più)
emerge --sync
emerge xfce4-meta
emerge -DNu world
revdep-rebuild
emerge --depclean
Sono allergico a mele morsicate e a finestre con tende.

Segnalate qui le vostre offerte di smartphone e tablet!!!

Avatar utente
Zievatron
Messaggi: 1657
Iscritto il: mercoledì 21 dicembre 2011, 23:49

Re: Linux sul mio PC: Il Ritorno... è Gentoo!

Messaggio da Zievatron »

Ho fatto partire prima emerge -DNu world che xfce.
Ha installato un altro pacchetto concludendo così:

Codice: Seleziona tutto

>>> Emerging (2 of 42) net-nds/openldap-2.4.28-r1
 * openldap-2.4.28.tgz RMD160 SHA1 SHA256 size ;-) ...                   [ ok ]
 * rfc2307bis.schema-20100722 RMD160 SHA1 SHA256 size ;-) ...            [ ok ]
 * ERROR: net-nds/openldap-2.4.28-r1 failed (setup phase):
 *   To build the ldapc++ library you must emerge openldap with sasl support
 * 
 * Call stack:
 *                   ebuild.sh, line  85:  Called pkg_setup
 *   openldap-2.4.28-r1.ebuild, line 215:  Called die
 * The specific snippet of code:
 *   		die "To build the ldapc++ library you must emerge openldap with sasl support"
 * 
 * If you need support, post the output of 'emerge --info =net-nds/openldap-2.4.28-r1',
 * the complete build log and the output of 'emerge -pqv =net-nds/openldap-2.4.28-r1'.
 * The complete build log is located at '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/die.env'.
 * S: '/var/tmp/portage/net-nds/openldap-2.4.28-r1/work/openldap-2.4.28'

>>> Failed to emerge net-nds/openldap-2.4.28-r1, Log file:

>>>  '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/build.log'

 * Messages for package net-nds/openldap-2.4.28-r1:

 * ERROR: net-nds/openldap-2.4.28-r1 failed (setup phase):
 *   To build the ldapc++ library you must emerge openldap with sasl support
 * 
 * Call stack:
 *                   ebuild.sh, line  85:  Called pkg_setup
 *   openldap-2.4.28-r1.ebuild, line 215:  Called die
 * The specific snippet of code:
 *   		die "To build the ldapc++ library you must emerge openldap with sasl support"
 * 
 * If you need support, post the output of 'emerge --info =net-nds/openldap-2.4.28-r1',
 * the complete build log and the output of 'emerge -pqv =net-nds/openldap-2.4.28-r1'.
 * The complete build log is located at '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/net-nds/openldap-2.4.28-r1/temp/die.env'.
 * S: '/var/tmp/portage/net-nds/openldap-2.4.28-r1/work/openldap-2.4.28'

 * GNU info directory index is up-to-date.
 * After world updates, it is important to remove obsolete packages with
 * emerge --depclean. Refer to `man emerge` for more information.
Sembra non avere ancora, o non sapere di avere, il supporto sasl.
Ho mancato di dirgli qualcosa? :hmm:

l'emersione di xfce, invece, è andata avanti di 30 pacchetti. Poi ha dato qualche errore:

Codice: Seleziona tutto

make: *** [all] Errore 2
emake failed
 * ERROR: app-misc/lirc-0.8.7 failed (compile phase):
 *   Unable to emake HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS=-m elf_x86_64   all
 * 
 * Call stack:
 *     ebuild.sh, line   85:  Called src_compile
 *   environment, line 4069:  Called linux-mod_src_compile
 *   environment, line 3126:  Called die
 * The specific snippet of code:
 *               eval "emake HOSTCC=\"$(tc-getBUILD_CC)\" 			CROSS_COMPILE=${CHOST}- 						LDFLAGS=\"$(get_abi_LDFLAGS)\" 						${BUILD_FIXES} 		${BUILD_PARAMS} 						${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}";
 * 
 * If you need support, post the output of 'emerge --info =app-misc/lirc-0.8.7',
 * the complete build log and the output of 'emerge -pqv =app-misc/lirc-0.8.7'.
 * The complete build log is located at '/var/tmp/portage/app-misc/lirc-0.8.7/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-misc/lirc-0.8.7/temp/environment'.
 * S: '/var/tmp/portage/app-misc/lirc-0.8.7/work/lirc-0.8.7'

>>> Failed to emerge app-misc/lirc-0.8.7, Log file:

>>>  '/var/tmp/portage/app-misc/lirc-0.8.7/temp/build.log'

 * Messages for package sys-fs/udev-171-r5:

 * 
 * udev-171 does not support Linux kernel before version 2.6.32!
 * 
 * persistent-net does assigning fixed names to network devices.
 * If you have problems with the persistent-net rules,
 * just delete the rules file
 * 	rm /etc/udev/rules.d/70-persistent-net.rules
 * and then reboot.
 * 
 * This may however number your devices in a different way than they are now.
 * 
 * If you build an initramfs including udev, then please
 * make sure that the /sbin/udevadm binary gets included,
 * and your scripts changed to use it,as it replaces the
 * old helper apps udevinfo, udevtrigger, ...
 * 
 * mount options for directory /dev are no longer
 * set in /etc/udev/udev.conf, but in /etc/fstab
 * as for other directories.
 * 
 * If you use /dev/md/*, /dev/loop/* or /dev/rd/*,
 * then please migrate over to using the device names
 * /dev/md*, /dev/loop* and /dev/ram*.
 * The devfs-compat rules have been removed.
 * For reference see Bug #269359.
 * 
 * Rules for /dev/hd* devices have been removed
 * Please migrate to libata.
 * 
 * For more information on udev on Gentoo, writing udev rules, and
 *          fixing known issues visit:
 *          http://www.gentoo.org/doc/en/udev-guide.xml

 * Messages for package app-misc/lirc-0.8.7:

 * If your LIRC device requires modules, you'll need MODULE_UNLOAD
 * support in your kernel.
 * 
 * Compiling only the lirc-applications, but no drivers.
 * Enable drivers with LIRC_DEVICES if you need them.
 * Setting default lirc-device to /dev/lirc0
 * Disabling lirc_gpio driver as it does no longer work Kernel 2.6.22+
 * ERROR: app-misc/lirc-0.8.7 failed (compile phase):
 *   Unable to emake HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS=-m elf_x86_64   all
 * 
 * Call stack:
 *     ebuild.sh, line   85:  Called src_compile
 *   environment, line 4069:  Called linux-mod_src_compile
 *   environment, line 3126:  Called die
 * The specific snippet of code:
 *               eval "emake HOSTCC=\"$(tc-getBUILD_CC)\" 			CROSS_COMPILE=${CHOST}- 						LDFLAGS=\"$(get_abi_LDFLAGS)\" 						${BUILD_FIXES} 		${BUILD_PARAMS} 						${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}";
 * 
 * If you need support, post the output of 'emerge --info =app-misc/lirc-0.8.7',
 * the complete build log and the output of 'emerge -pqv =app-misc/lirc-0.8.7'.
 * The complete build log is located at '/var/tmp/portage/app-misc/lirc-0.8.7/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-misc/lirc-0.8.7/temp/environment'.
 * S: '/var/tmp/portage/app-misc/lirc-0.8.7/work/lirc-0.8.7'

 * Regenerating GNU info directory index...
 * Processed 86 info files.
revdep-rebuild tutto OK
emerge --depclean dà i soliti messaggi.
Provo a ripetere tutto.
Zievatron

Rispondi