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

[Zievatron]

rc è praticamente quello che gestisce i servizi/demoni del sistema.
Quindi man mano che te li compilava te li facevo aggiungere con la sintassi:
"rc-update add nome_servizio quando_deve_partire"

Ma come fai a sapere quando serve dargli prima un rc-update e per aggiungere cosa?
E quando invece si può procedere senza dargli questo rc-update?

Ora si è fermato qui:

Codice: Seleziona tutto

>>> Emerging (1 of 110) 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'

[conoscenza]

Ma come fai a sapere quando serve dargli prima un rc-update e per aggiungere cosa?
E quando invece si può procedere senza dargli questo rc-update?

quando viene emerso qualcosa da aggiungere a rc è il terminale stesso a dirti che sono da aggiungere (riguarda i post precedenti a quando ti dicevo fai "rc-update add ...." e vedrai che in quel che hai postato c'è scritto il da farsi)....
Non sono un mago!

rc-update va sempre dato, altrimenti poi quando avvii il sistema che avvii?

Prova a dare:

Codice: Seleziona tutto

USE=sals emerge openldap

che ti dice?

[Zievatron]

rc-update va sempre dato, altrimenti poi quando avvii il sistema che avvii?

Come, sempre? Io vedo che a volte mi dici di darlo (con qualcosa da aggiungere) altre volte no.

Codice: Seleziona tutto

    USE=sals emerge openldap
Calculating dependencies... done!

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) 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'
darkstar / # 

[conoscenza]

ho frainteso il sempre!
Allora quando ti viene detto di aggiungere un servizio/demone devi farlo sempre!
Non in tutti i tuoi output era detto, quindi la mia risposta dipendeva dal tuo output.

Prova a dare:
etc-update (-5 se serve)
emerge --sync
revdep-rebuild
emerge xfce4-meta

[Zievatron]

Allora quando ti viene detto di aggiungere un servizio/demone devi farlo sempre!

Qual'è il messaggio che avverte di questa necessità?

Direi che si è fermato di nuovo subito:

Codice: Seleziona tutto

>>> Emerging (1 of 110) 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'

[conoscenza]

Vai ad esempio qui: http://www.bitsandchips.it/forum/viewto ... 230#p11634
Nel tuo output tra le varie cose c'è scritto:
"....
....
....
To take advantage of the init script, and automate the process of
* saving and restoring sound-card mixer levels you should
* add alsasound to the boot runlevel. You can do this as
* root like so:
* # rc-update add alsasound boot
...
...
..."

è scritto negli output.

Prova a vedere (posta qui):

Codice: Seleziona tutto

cat /var/log/emerge.log | grep -i rc-update

EDIT:
revdep-rebuild cosa fa?
prova a dare:

Codice: Seleziona tutto

emerge -uDN system

e posta gli errori

[Zievatron]

Prova a vedere (posta qui):

Codice: Seleziona tutto

cat /var/log/emerge.log | grep -i rc-update

Questo mi restituisce subito la riga di comando senza fare niente.
Poi:
revdep-rebuild
fa il suo lavoro lentino, ma completa senza nessun messaggio di errore.
emerge -uDN system
cos'è?
Sta emergendo (1 of 55)

[conoscenza]

emerge -uDN system
cos'è?

è simile a "emerge -DNu world"...aggiornando il sistema!

[Zievatron]

Ah! Ecco perchè sta tirando su roba a non finire!

[conoscenza]

Quando si inceppa... posta tutto...tranne le scritte di compilazione...