problema emerge su ppc molti pacchetti masked

[whiterabbit]

Ciao a tutti...
Ho da poco finito di installare il mio nuovo ibookG4 ....ma ho il problema che un sacco di pacchetti non me li fa installare e mi da il seguente messaggio:
bash-2.05b# emerge openoffice-bin
Calculating dependencies
!!! all ebuilds that could satisfy "openoffice-bin" have been masked.
!!! possible candidates are:
- app-office/openoffice-bin-1.0.3.1 (masked by: -keyword)
- app-office/openoffice-bin-1.1.0 (masked by: -keyword)
- app-office/openoffice-bin-1.1.1 (masked by: -keyword)

anche con altri software mi da sempre lo stesso messaggio:
bash-2.05b# emerge tsclient
Calculating dependencies
!!! all ebuilds that could satisfy "tsclient" have been masked.
!!! possible candidates are:
- net-misc/tsclient-0.116 (masked by: missing keyword)
- net-misc/tsclient-0.120 (masked by: missing keyword)
- net-misc/tsclient-0.124 (masked by: missing keyword)
- net-misc/tsclient-0.132 (masked by: missing keyword)

!!! Error calculating dependencies. Please correct.

Che cosa mi manca????

USE="X gtk gnome alsa -qt radeon directfb flash avi samba dvd perl ssl -kde gtk2 fbcon gb cdr java jpeg mpeg ssl crypt ldap samba mozilla xfs truetype xml xml2 pam cups wrappers"

CHOST="powerpc-unknown-linux-gnu"

CFLAGS="-O2 -pipe -mcpu=7400 -maltivec -mabi=altivec"

CXXFLAGS="${CFLAGS}"

ACCEPT_KEYWORDS="~ppc"



Grazie


Matteo

[shev]

Credo non ti manchi nulla, semplicemente il primo pacchetto è masked con il trattino (-ppc) anzichè la tilde, ovvero è unstable dichiarato e non solo in fase di test. Sconsiglio di installare pacchetti con problemi evidenti e dichiarati. Nel caso specifico i binari di oo.org credo siano solo per x86, quindi il meno indica che proprio il pacchetto non va. Il secondo pacchetto invece potrebbe non funzionare con ppc come potrebbe funzionare ma non essere ancora stato segnalato da nessuno: manca infatti la key ppc nell'ebuild, sintomo di quanto detto sopra, o nessuno l'ha testato o tale pacchetto non va su ppc.
_________________
Se per vivere ti dicono "siediti e stai zitto" tu alzati e muori combattendo

[whiterabbit]

Ho trovato una FAQ a riguardo.
Ho provato sia con "ppc", con "-ppc" ma il problema non cambia....
Nel tuo post evedenzi il fatto che forse i due pacchetti che ho messo come esempio forse non sono per ppc...ma me lo fa con tutti....anche con quelli che so di certo che girano su ppc...

In "USE" del make.conf devo aggiungerci ppc o similari???

Grazie

Matteo

[shev]

Mmmm, strano. Considera che sto aggiornando gnome sul pbook proprio in questo istante e di problemi non me ne da, sia con emerge normali che con emerge di pacchetti masked (ACCEPT_KEYWORD=~ppc emerge -vp gnome).
Postami il tuo make.conf completo, così controlliamo se è tutto effettivamente a posto.
_________________
Se per vivere ti dicono "siediti e stai zitto" tu alzati e muori combattendo

[whiterabbit]

# Example:
USE="java X gtk gnome alsa -qt radeon directfb flash avi samba dvd perl ssl -kde gtk2 fbcon gb cdr jpeg mpeg ssl crypt samba krb5 ldap samba mozilla xfs truetype xml xml2 pam cups wrappers"


# Host Setting
# ============
#
# All PowerPC systems should use this host setting:

CHOST="powerpc-unknown-linux-gnu"

# Host and optimization settings
# ==============================
#
# For optimal performance, enable a CFLAGS setting appropriate for your CPU.
#
# Please note that if you experience strange issues with a package, it may be
# due to gcc's optimizations interacting in a strange way. Please test the
# package (and in some cases the libraries it uses) at default optimizations
# before reporting errors to developers.
#
# -mcpu=<cpu-type> for PowerPC systems selects the type of processor you want
# to optimize your code for. Code generated under those options will run best
# on that processor, and may not run at all on others.
#
# GCC 3.2 supports many powerpc processor types including: rios, rios1, rsc,
# rios2, rs64a, 601, 602, 603, 603e, 604, 604e, 620, 630, 740, 7400, 7450, 750,
# power, power2, powerpc, 403, 505, 801, 821, 823, and 860 and common.
#
# Recommended settings for GCC 3.2 only (Gentoo 1.4 or newer) :
#
# -maltivec enables optional (still limited) altivec support and should be used
# only for G4 processors, on GCC 3.2 or newer. It also requires that you have
# the alitvec option compiled into your kernel to take full advantage of this
# feature. Note: you should also include -mabi=altivec flag if using this option.
#
# Long term testing has shown that -O3 opts can be unreliable on G4's but work
# on G3 series processors or earlier. Use on a G4 at your own risk =)
#
# Due to some failures with the cpu string of 7450, the dev team recommends
# using -mcpu=7400 for all G4 series processors until GCC 3.2 is more mature
#
CFLAGS="-O2 -pipe -mcpu=7400 -maltivec -mabi=altivec"

#
#
# All non G4 PPC boxen should choose this next option. It will work fine for
# all G3 and pre machines. (note it will not hurt pre G3 machines either to
# use this mcpu option as it is the default for gcc 3.2.x anyway)
#
#CFLAGS="-O3 -pipe -mcpu=750"

# Recommended settings for GCC 2.95.3 only (Gentoo 1.2 or older):
#
# PowerPC 750 > up: this works on G3's and G4s, gcc 2.95.3 doesn't make the
# distinction between G3 and G4, so this is fine for all NewWorld machines, if
# you use yaboot to boot you should select this option
#
#CFLAGS="-O2 -pipe -mcpu=750 -mpowerpc-gfxopt -mmultiple -mstring"
#
# This will run on all other processors, by building more generic code This is
# safe for all PPC machines running gcc 2.95.3, and works for all OldWorld
# machines - if you use BootX to boot you should select this option
#CFLAGS="-O2 -pipe -mmultiple -mstring"

# If you set a CFLAGS above, then this line will set your default C++ flags to
# the same settings.
CXXFLAGS="${CFLAGS}"

# Advanced Masking
# ================
#
# Gentoo is using a new masking system to allow for easier stability testing
# on packages. KEYWORDS are used in ebuilds to mask and unmask packages based
# on the platform they are set for. A special form has been added that
# indicates packages and revisions that are expected to work, but have not yet
# been approved for the stable set. '~arch' is a superset of 'arch' which
# includes the unstable, in testing, packages. Users of the 'x86' architecture
# would add '~x86' to ACCEPT_KEYWORDS to enable unstable/testing packages.
# '~ppc', '~sparc' are the unstable KEYWORDS for their respective platforms.
#
# Please note that this is not for development, alpha, beta, nor cvs release
# packages. "Broken" packages will not be added to testing and should not be
# requested to be added. Alternative routes are available to developers
# for experimental packages, and it is at their discretion to use them.
#
# DO NOT PUT ANYTHING BUT YOUR SPECIFIC ~ARCHITECTURE IN THE LIST.
# IF YOU ARE UNSURE OF YOUR ARCH, OR THE IMPLICATIONS, DO NOT MODIFY THIS.
#
# Note: this really shouldn't be enabled until _AFTER_ you bootstrap and emerge
# system. If you want the testing things update after these steps are completed.

#ACCEPT_KEYWORDS="~ppc"
ACCEPT_KEYWORDS="ppc"

il resto e' tutto di default...

Sul portatile vecchio ibook G3 per il risolvere il medesimo problema avevo fatto un emerge -ue world ....mi puo' servire secondo te???..visto che sono 174 pacchetti :\)
i

Ciao

Matteo