Probleme bei erster Gentoo Installation

Diskutiere Probleme bei erster Gentoo Installation im Gentoo Forum im Bereich Linux Distributionen; Hallo ihr, Bin gerade dabei mein erstes Gentoo zu kompilieren/installieren... Hab nen Samsung R40Plus mit Intel Core Duo und Intel Radeon X1250...

  1. #1 LayC, 12.03.2009
    Zuletzt bearbeitet: 12.03.2009
    LayC

    LayC Grünschnabel

    Dabei seit:
    12.03.2009
    Beiträge:
    9
    Zustimmungen:
    0
    Hallo ihr,
    Bin gerade dabei mein erstes Gentoo zu kompilieren/installieren...
    Hab nen Samsung R40Plus mit Intel Core Duo und Intel Radeon X1250 GraKa...

    bin gerade bei der make.conf...

    bis jetzt sieht sie so aus:
    Code:
    CFLAGS="-march=prescott -O2 -pipe -fomit-frame-pointer"
    CXXFLAGS="$(CFLAGS)" (auch wenn ich noch nicht so ganz verstehe wofür man CFLAGS und CXXFLAGS braucht)
    CHOST="i686-pc-linux-gnu"
    VIDEO_CARDS="fglrx"
    ACCEPT_KEYWORDS="x86"
    MAKEOPTS="-j3"
    INPUT_DEVICES="keyboard mouse synaptics" (synaptics hab ich mal als Touchpad interpretiert...)
    
    Die Frage ist nun was ich bei Features und Use reinschreiben soll/kann, da ich dazu nichts finde.

    Ich hoffe ihr könnt mir helfen.
    .
    .
    .
    EDIT (autom. Beitragszusammenführung) :
    .

    Hab das o.g. Problem gelöst... nun ist mein Problem ein anderes...
    bei "emerge -uDN world" kommt folgender Fehler:

    Code:
    >>> Installing virtual/jre-1.6.0
    
    >>> Emerging (153 of 249) sys-libs/db-4.5.20_p2-r1
     * db-4.5.20.tar.gz RMD160 SHA1 SHA256 size ;-) ...                                                                                                   [ ok ]
     * patch.4.5.20.1 RMD160 SHA1 SHA256 size ;-) ...                                                                                                     [ ok ]
     * patch.4.5.20.2 RMD160 SHA1 SHA256 size ;-) ...                                                                                                     [ ok ]
     * checking ebuild checksums ;-) ...                                                                                                                  [ ok ]
     * checking auxfile checksums ;-) ...                                                                                                                 [ ok ]
     * checking miscfile checksums ;-) ...                                                                                                                [ ok ]
    Traceback (most recent call last):
      File "/usr/bin/java-config-2", line 8, in <module>
        from java_config_2 import __version__
    ImportError: No module named java_config_2
     * 
     * Can't run java-config --help
     * Have you upgraded python recently but haven't
     * run python-updater yet?
     * 
     * ERROR: sys-libs/db-4.5.20_p2-r1 failed.
     * Call stack:
     *               ebuild.sh, line   49:  Called pkg_setup
     *               ebuild.sh, line 1286:  Called java-pkg-opt-2_pkg_setup
     *   java-pkg-opt-2.eclass, line   45:  Called java-pkg_init
     *     java-utils-2.eclass, line 2101:  Called die
     * The specific snippet of code:
     *   		die "Can't run java-config --help"
     *  The die message:
     *   Can't run java-config --help
     * 
     * If you need support, post the topmost build error, and the call stack if relevant.
     * A complete build log is located at '/var/tmp/portage/sys-libs/db-4.5.20_p2-r1/temp/build.log'.
     * The ebuild environment file is located at '/var/tmp/portage/sys-libs/db-4.5.20_p2-r1/temp/die.env'.
     * 
    !!! When you file a bug report, please include the following information:
    GENTOO_VM=  CLASSPATH="" JAVA_HOME=""
    JAVACFLAGS="" COMPILER=""
    and of course, the output of emerge --info
    
    >>> Failed to emerge sys-libs/db-4.5.20_p2-r1, Log file:
    
    >>>  '/var/tmp/portage/sys-libs/db-4.5.20_p2-r1/temp/build.log'
    
     * Messages for package dev-libs/expat-2.0.1-r1:
    
     * Please note that the soname of the library changed!
     * If you are upgrading from a previous version you need
     * to fix dynamic linking inconsistencies by executing:
     * revdep-rebuild -X --library libexpat.so.0
    
     * Messages for package app-portage/portage-utils-0.1.29:
    
     * //etc/portage/postsync.d/q-reinitialize has been installed for convenience
     * If you wish for it to be automatically run at the end of every --sync simply chmod +x //etc/portage/postsync.d/q-reinitialize
     * Normally this should only take a few seconds to run but file systems such as ext3 can take a lot longer.
     * If ever you find this to be an inconvenience simply chmod -x //etc/portage/postsync.d/q-reinitialize
    
     * Messages for package app-text/libpaper-1.1.23:
    
     * run "paperconfig -p letter" as root to use letter-pagesizes
     * or paperconf with normal user privileges.
    
     * Messages for package sys-libs/timezone-data-2008i:
    
     * You do not have TIMEZONE set in /etc/conf.d/clock.
     * Skipping auto-update of /etc/localtime.
    
     * Messages for package sys-kernel/linux-headers-2.6.27-r2:
    
     * Kernel headers are usually only used when recompiling your system libc, as
     * such, following the installation of newer headers, it is advised that you
     * re-merge your system libc.
     * Failure to do so will cause your system libc to not make use of newer
     * features present in the updated kernel headers.
    
     * Messages for package sys-apps/xinetd-2.3.14:
    
     * 
     * PLEASE NOTE: Everything is off by default with access restricted to localhost.
     * 
    
     * Messages for package sys-fs/udev-124-r1:
    
     * 
     * 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,
     * as the helper apps udevinfo, udevtrigger, ... are now
     * only symlinks to udevadm.
     * 
     * mount options for directory /dev are no longer
     * set in /etc/udev/udev.conf, but in /etc/fstab
     * as for other directories.
     * 
     * 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 dev-libs/openssl-0.9.8j:
    
     * Due to the way openssl is architected, you cannot
     * switch between optimized versions without breaking
     * ABI.  The default i686 0.9.8 ABI was an unoptimized
     * version with horrible performance.  This version uses
     * the optimized ABI.  If you experience segfaults when
     * using ssl apps (like openssh), just re-emerge the
     * offending package.
    
     * Messages for package sys-devel/binutils-2.18-r3:
    
     * Sorry, but binutils does not support the LINGUAS: en
    
     * Messages for package media-libs/alsa-lib-1.0.17a:
    
     * Starting from alsa 1.0.11_rc3 the configuration for dmix is changed.
     * Leaving around old asound.conf or ~/.asoundrc might make all apps
     * using ALSA output crash.
     * Note that dmix output is enabled by default on the 'default' device
     * since ALSA 1.0.9.
     * 
     * Please try in-kernel ALSA drivers instead of the alsa-drivers ebuild.
     * If alsa-drivers works for you where a recent kernel does not, we want 
     * to know about this. Our e-mail address is alsa-bugs@gentoo.org
     * However, if you notice no sound output or instability, please try to 
     * upgrade your kernel to a newer version first.
    
     * Messages for package sys-kernel/gentoo-sources-2.6.27-r8:
    
     * If you are upgrading from a previous kernel, you may be interested
     * in the following document:
     *   - General upgrade guide: http://www.gentoo.org/doc/en/kernel-upgrade.xml
    
     * Messages for package dev-lang/python-2.5.2-r7:
    
     * 
     * If you have just upgraded from an older version of python you will
     * need to run:
     * 
     * /usr/sbin/python-updater
     * 
     * This will automatically rebuild all the python dependent modules
     * to run with python-2.5.
     * 
     * Your original Python is still installed and can be accessed via
     * /usr/bin/python2.x.
     * 
    
     * Messages for package media-libs/tiff-3.8.2-r4:
    
     * JBIG support is intended for Hylafax fax compression, so we
     * really need more feedback in other areas (most testing has
     * been done with fax).  Be sure to recompile anything linked
     * against tiff if you rebuild it with jbig support.
    
     * Messages for package sys-apps/acl-2.2.47:
    
     * Sorry, but acl does not support the LINGUAS: de en
    
     * Messages for package sys-apps/coreutils-6.10-r2:
    
     * Make sure you run 'hash -r' in your active shells.
    
     * Messages for package app-misc/ca-certificates-20080809:
    
     * You should run update-ca-certificates manually after etc-update
     * Broken symlink for a certificate at /etc/ssl/certs/5f5e5caa.0
     * Broken symlink for a certificate at /etc/ssl/certs/1e49180d.0
     * Broken symlink for a certificate at /etc/ssl/certs/6c55cf77.0
     * Broken symlink for a certificate at /etc/ssl/certs/SPI_CA_2006-cacert.pem
     * Broken symlink for a certificate at /etc/ssl/certs/c53f52eb.0
     * Broken symlink for a certificate at /etc/ssl/certs/Verisign_Secure_Server_OCSP_Responder.pem
     * Broken symlink for a certificate at /etc/ssl/certs/cdd7aee7.0
     * Broken symlink for a certificate at /etc/ssl/certs/878cf4c6.0
     * Broken symlink for a certificate at /etc/ssl/certs/7a9820c1.0
     * Broken symlink for a certificate at /etc/ssl/certs/843b6c51.0
     * Broken symlink for a certificate at /etc/ssl/certs/aad3d04d.0
     * Broken symlink for a certificate at /etc/ssl/certs/Verisign_Class_3_Public_Primary_OCSP_Responder.pem
     * Broken symlink for a certificate at /etc/ssl/certs/a3c60019.0
     * Broken symlink for a certificate at /etc/ssl/certs/408e388a.0
     * Broken symlink for a certificate at /etc/ssl/certs/6adf0799.0
     * Broken symlink for a certificate at /etc/ssl/certs/d4e39186.0
     * Broken symlink for a certificate at /etc/ssl/certs/spi-ca.pem
     * Broken symlink for a certificate at /etc/ssl/certs/2edf7016.1
     * Broken symlink for a certificate at /etc/ssl/certs/56e607f4.0
     * Broken symlink for a certificate at /etc/ssl/certs/Verisign_Class_1_Public_Primary_OCSP_Responder.pem
     * Broken symlink for a certificate at /etc/ssl/certs/e28f6bbc.0
     * Broken symlink for a certificate at /etc/ssl/certs/Verisign_Class_2_Public_Primary_OCSP_Responder.pem
     * Broken symlink for a certificate at /etc/ssl/certs/61f6c934.0
     * You MUST remove the above broken symlinks
     * Otherwise any SSL validation that use the directory may fail!
     * To batch-remove them, run:
     * find -L /etc/ssl/certs/ -type l -exec rm {} +
    
     * Messages for package dev-libs/apr-1.3.3:
    
     * We are now using the system's libtool rather than bundling
     * our own. You will need to rebuild Apache and possibly other
     * software if you get a message similiar to the following:
     * 
     *    /usr/share/apr-1/build-1/libtool: No such file or directory
     * 
    
     * Messages for package x11-misc/shared-mime-info-0.51:
    
     * 
     * The database format has changed between 0.30 and 0.40.
     * You may need to update all your local databases and caches.
     * To do so, please run the following commands:
     * (for each user) $ update-mime-database ~/.local/share/mime/
     * (as root)       # update-mime-database /usr/local/share/mime/
     * 
    
     * Messages for package sys-apps/attr-2.4.43:
    
     * Sorry, but attr does not support the LINGUAS: de en
    
     * Messages for package media-libs/freetype-2.3.8:
    
     * The utilities and demos previously bundled with freetype are now
     * optional.  Enable the utils USE flag if you would like them
     * to be installed.
    
     * Messages for package sys-apps/dbus-1.2.3-r1:
    
     * To start the D-Bus system-wide messagebus by default
     * you should add it to the default runlevel :
     * `rc-update add dbus default`
     * 
     * Some applications require a session bus in addition to the system
     * bus. Please see `man dbus-launch` for more information.
     * 
     * 
     * You MUST run 'revdep-rebuild' after emerging this package
     * 
     * If you are currently running X with the hal useflag enabled
     * restarting the dbus service WILL restart X as well
     * 
     * You must restart D-Bus `/etc/init.d/dbus restart` to run
     * the new version of the daemon. For many people, this means
     * exiting X as well.
    
     * Messages for package x11-libs/libXi-1.1.3:
    
     * Some special keys and keyboard layouts may stop working.
     * To fix them, recompile xorg-server.
    
     * Messages for package x11-libs/libXdamage-1.1.1:
    
     * Compositing managers may stop working.
     * To fix them, recompile xorg-server.
    
     * Messages for package dev-java/sun-jdk-1.6.0.12:
    
     * Fallback PaX marking -m
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/appletviewer
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/apt
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/extcheck
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/idlj
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/jar
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/jarsigner
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/java
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/javac
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/javadoc
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/javah
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/javap
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/javaws
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/jconsole
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/jdb
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/jhat
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/jinfo
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/jmap
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/jps
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/jrunscript
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/jsadebugd
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/jstack
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/jstat
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/jstatd
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/keytool
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/native2ascii
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/orbd
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/pack200
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/policytool
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/rmic
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/rmid
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/rmiregistry
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/schemagen
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/serialver
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/servertool
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/tnameserv
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/unpack200
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/wsgen
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/wsimport
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/bin/xjc
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/jre/bin/java
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/jre/bin/java_vm
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/jre/bin/javaws
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/jre/bin/keytool
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/jre/bin/orbd
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/jre/bin/pack200
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/jre/bin/policytool
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/jre/bin/rmid
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/jre/bin/rmiregistry
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/jre/bin/servertool
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/jre/bin/tnameserv
     *      /var/tmp/portage/dev-java/sun-jdk-1.6.0.12/work/jdk1.6.0_12/jre/bin/unpack200
     * Disabling generation-1 compatibility...
     * A revdep-rebuild control file was installed to prevent reinstalls due to
     * missing dependencies (see bug #177925 for more info). Note that some parts
     * of the JVM may require dependencies that are pulled only through respective
     * USE flags (typically X, alsa, odbc) and some Java code may fail without them.
     * Please reinstall eclipse-sdk if you have it installed and want
     * workaround for bug #215150.
    
     * Messages for package sys-libs/db-4.5.20_p2-r1:
    
     * 
     * Can't run java-config --help
     * Have you upgraded python recently but haven't
     * run python-updater yet?
     * 
     * ERROR: sys-libs/db-4.5.20_p2-r1 failed.
     * Call stack:
     *               ebuild.sh, line   49:  Called pkg_setup
     *               ebuild.sh, line 1286:  Called java-pkg-opt-2_pkg_setup
     *   java-pkg-opt-2.eclass, line   45:  Called java-pkg_init
     *     java-utils-2.eclass, line 2101:  Called die
     * The specific snippet of code:
     *   		die "Can't run java-config --help"
     *  The die message:
     *   Can't run java-config --help
     * 
     * If you need support, post the topmost build error, and the call stack if relevant.
     * A complete build log is located at '/var/tmp/portage/sys-libs/db-4.5.20_p2-r1/temp/build.log'.
     * The ebuild environment file is located at '/var/tmp/portage/sys-libs/db-4.5.20_p2-r1/temp/die.env'.
     * 
    
     * Regenerating GNU info directory index...
     * Processed 82 info files.
    
     * IMPORTANT: 7 config files in '/etc' need updating.
     * See the CONFIGURATION FILES section of the emerge
     * man page to learn how to update config files.
    
    
     
  2. brb.

    brb. Grünschnabel

    Dabei seit:
    23.02.2009
    Beiträge:
    3
    Zustimmungen:
    0
    Du musst noch /etc updaten. Mit etc-update, wenn du nichts geaendert hast oder am besten gleich mit einem guten Tool dispatch-conf aus dem Paket gentoolkit.
    Ansonsten schaut da nichts fatal aus.

    Gentoo-Dokumentation ;) Safe Cflags, Portage Features
    CXXFLAGS="{CFLAGS}" ...
     
Thema:

Probleme bei erster Gentoo Installation

Die Seite wird geladen...

Probleme bei erster Gentoo Installation - Ähnliche Themen

  1. grub-pc Probleme bei upgrade

    grub-pc Probleme bei upgrade: Hallo, ich habe beim dist-upgrade folgendes Problem: ---------- Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt. Trigger für...
  2. Probleme mit YUM

    Probleme mit YUM: Hallo, ich habe CentOs 7 als Dualboot mit Windows 7 auf einen Dell Latitude E5510 installiert. Dies hat soweit auch alles geklappt. Leider habe...
  3. Forscher analysieren Durchsatzprobleme im Linux-Scheduler

    Forscher analysieren Durchsatzprobleme im Linux-Scheduler: Eine Gruppe von Forschern hat Fälle identifiziert, in denen der Scheduler im Linux-Kernel falsche Entscheidungen trifft und die CPUs nicht so gut...
  4. München: LiMux als Sündenbock für IT-Probleme?

    München: LiMux als Sündenbock für IT-Probleme?: Im Münchner Stadtrat soll später in diesem Jahr erneut über den Einsatz von Linux in der Stadtverwaltung diskutiert werden. Die Grünen vermuten,...
  5. BSI-Audit findet keine akuten Probleme in OpenSSL

    BSI-Audit findet keine akuten Probleme in OpenSSL: Das Bundesamt für Sicherheit in der Informationstechnik hat OpenSSL auf seine Sicherheit untersuchen lassen. Die Analyse zeigt vor allem, dass die...