Find the answer to your Linux question:
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 17
Okay, I made the mistake of setting the "~x86" flag in make.conf. I'm pretty sure that's the root of all my problems... I've since removed it, and updated many times...alot ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Aug 2005
    Posts
    11

    Gentoo Exploded


    Okay, I made the mistake of setting the "~x86" flag in make.conf. I'm pretty sure that's the root of all my problems...

    I've since removed it, and updated many times...alot of things were downgraded, but I still have issues. I have constant segmentation faults and arbitrary program crashes, most of which aren't reproducable.

    I've had mplayer, gkrellm, emerge, openoffice, azureus, among a slurry of other programs crash with a segmentation fault.

    I'm using the nitro sources, but even without them, I have many of the same problems.

    What can I do, short of starting from scratch? Can I just DL the stage3 compilation and go from there, and if so, how would I go about doing that?

    A_T

  2. #2
    Linux User Stefann's Avatar
    Join Date
    Nov 2004
    Location
    Boise, ID
    Posts
    340
    Does Gentoo come with a repair mode like most other distros???? Never used it before, but I'm pretty sure that or starting from scratch is your only course of action, not to be mean but next time you edit a important config file you should be absolutley sure on what your doing(most have self-documentation inside them too) and double check everything before you save and exit your editor. But unless anyone else has a stroke of genious, starting from scratch seems to be your only option.
    Nothing is worse than ten penguins fighting over which is better, vi or emacs.
    Registered Linux User #404402
    Finally I'm back on LF after a long while.

  3. #3
    Linux Newbie
    Join Date
    Oct 2004
    Posts
    133
    Were you having problems right from installation, or did it start happening later?
    What arch cpu do you have (pentium, athlon, ppc, etc), and which stage tarball did you use?

    Post the contents of your make.conf
    universally unmasking ~x86 is kind of risky, but it shouldn't be causing seg faults. I have about 50 or so unmasked packages installed, with no problems. I suspect that it's something else, like improperly set CFLAGS or something

  4. #4
    Linux User Stefann's Avatar
    Join Date
    Nov 2004
    Location
    Boise, ID
    Posts
    340
    Quote Originally Posted by mjman
    Were you having problems right from installation, or did it start happening later?
    What arch cpu do you have (pentium, athlon, ppc, etc), and which stage tarball did you use?

    Post the contents of your make.conf
    universally unmasking ~x86 is kind of risky, but it shouldn't be causing seg faults. I have about 50 or so unmasked packages installed, with no problems. I suspect that it's something else, like improperly set CFLAGS or something
    If you read his post, he used stage 3.
    Nothing is worse than ten penguins fighting over which is better, vi or emacs.
    Registered Linux User #404402
    Finally I'm back on LF after a long while.

  5. #5
    Just Joined!
    Join Date
    May 2005
    Location
    Huntington Beach, CA USA
    Posts
    22
    Do an emerge --info and post the results.

    Have you tried doing the following:

    emerge --update --deep --newuse world
    emerge --depclean
    revdep-rebuild

    Just make sure you have the gentoolkit installed first. It may also be a good idea to use both the -p and -av options as well. You should not need to reinstall. As my friend who got me started with gentoo has told me a thousand times, almost everything in gentoo is fixable once you understand the problem.

  6. #6
    Linux Enthusiast
    Join Date
    Jun 2005
    Location
    Odessa, FL
    Posts
    586
    it's probably somewhat irrelevant, but i'm using ACCEPT_KEYWORDS="~86" in my make.conf without any problems...have been for a few months now

    you can reinstall it without starting over if you'd like (sort of).

    "emerge --emptytree world" would reinstall everything on your system with your current make.conf

  7. #7
    Linux Guru
    Join Date
    May 2004
    Location
    forums.gentoo.org
    Posts
    1,817
    Quote Originally Posted by Stefann
    ...but next time you edit a important config file you should be absolutley sure on what your doing...
    C'mon, this is Linux, not the shroud of Turin.
    /IMHO
    //got nothin'
    ///this use to look better

  8. #8
    Just Joined!
    Join Date
    Aug 2005
    Posts
    11

    more seg faults

    Okay, I recompiled the kernel because my boot partition went on the fritz. But after that, I tried emerge -vuNDa world again, and it fails on cdrdao (syntax error), or it segfaults...sometimes one, sometimes the other.

    I did the emerge --depclean, and revdep-rebuild. revdep-rebuild segfaults on one of the gnome packages.

    I'm trying revdep-rebuild again, and reguardless of whether or not it fails, I'll try unmerge a bunch of things, so as to skip cdrdao, and try emerge -vuNDa world again.

    Here's emerge --info:
    Code:
    Gentoo Base System version 1.6.13
    Portage 2.0.51.22-r3 (default-linux/x86/2005.1, gcc-3.3.6, glibc-2.3.5-r2, 2.6.13.2-nitro1 i686)
    =================================================================
    System uname: 2.6.13.2-nitro1 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz
    distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
    dev-lang/python:     2.3.5, 2.4.2
    sys-apps/sandbox:    1.2.12
    sys-devel/autoconf:  2.13, 2.59-r6
    sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
    sys-devel/binutils:  2.15.92.0.2-r10
    sys-devel/libtool:   1.5.20
    virtual/os-headers:  2.6.11-r2
    ACCEPT_KEYWORDS="x86"
    AUTOCLEAN="yes"
    CBUILD="i686-pc-linux-gnu"
    CFLAGS="-march=pentium4 -O3 -pipe -fomit-frame-pointer"
    CHOST="i686-pc-linux-gnu"
    CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control"
    CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
    CXXFLAGS="-march=pentium4 -O3 -pipe -fomit-frame-pointer"
    DISTDIR="/usr/portage/distfiles"
    FEATURES="autoconfig distlocks sandbox sfperms strict"
    GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
    PKGDIR="/usr/portage/packages"
    PORTAGE_TMPDIR="/var/tmp"
    PORTDIR="/usr/portage"
    SYNC="rsync://rsync.gentoo.org/gentoo-portage"
    USE="x86 X aac acpi alsa apm arts avi bash-completion berkdb bitmap-fonts cdr chroot crypt cups curl dvd dvdr dvdread eds emboss encode esd fam firefox fluxbox foomaticdb fortran gdbm gif gnome gpm gstreamer gtk gtk2 imlib ipv6 java jpeg junit kde libg++ libwww mad mikmod mmx motif mozilla mp3 mpeg mpeg4 mplayer ncurses nls ogg oggvorbis opengl oss pam pdflib perl png python qt quicktime readline real sdl spell sse sse2 ssl tcpd tiff truetype truetype-fonts type1-fonts udev usb userlocales vorbis win32codecs xml xml2 xmms xv xvid zlib userland_GNU kernel_linux elibc_glibc"
    Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS, PORTDIR_OVERLAY
    Here's make.conf:
    Code:
    # Copyright 1999-2004 Gentoo Foundation
    # Distributed under the terms of the GNU General Public License v2
    # $Header: /var/cvsroot/gentoo-src/portage/cnf/make.conf.x86,v 1.5.2.5 2005/04/13 15:28:38 jstubbs Exp $
    # Contains local system settings for Portage system
    
    # Please review 'man make.conf' for more information.
    
    # Build-time functionality
    # ========================
    #
    # The USE variable is used to enable optional build-time functionality. For
    # example, quite a few packages have optional X, gtk or GNOME functionality
    # that can only be enabled or disabled at compile-time. Gentoo Linux has a
    # very extensive set of USE variables described in our USE variable HOWTO at
    # http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1
    #
    # The available list of use flags with descriptions is in your portage tree.
    # Use 'less' to view them&#58;  --> less /usr/portage/profiles/use.desc <--
    #
    # 'ufed' is an ncurses/dialog interface available in portage to make handling
    # useflags for you. 'emerge app-portage/ufed'
    #
    # Example&#58;
    USE="X gtk2 fluxbox gnome alsa kde chroot ssl mmx sse sse2 
    divx4linux win32codecs real quicktime xvid cups firefox acpi 
    dvdread dvd dvdr mpeg4 mplayer aac avi bash-completion userlocales cdr crypt usb"
    
    # Host Setting
    # ============
    #
    # DO NOT CHANGE THIS SETTING UNLESS YOU ARE USING STAGE1!
    # Change this line as appropriate &#40;i686, i586, i486 or i386&#41;.
    # All modern systems &#40;even Athlons&#41; should use "i686-pc-linux-gnu".
    # All K6's are i586.
    CHOST="i686-pc-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 &#40;and in some cases the libraries it uses&#41; at default optimizations
    # before reporting errors to developers.
    #
    # -mcpu=<cpu-type> means optimize code for the particular type of CPU without
    # breaking compatibility with other CPUs.
    #
    # -march=<cpu-type> means to take full advantage of the ABI and instructions
    # for the particular CPU; this will break compatibility with older CPUs &#40;for
    # example, -march=athlon-xp code will not run on a regular Athlon, and
    # -march=i686 code will not run on a Pentium Classic.
    #
    # CPU types supported in gcc-3.2 and higher&#58; athlon-xp, athlon-mp,
    # athlon-tbird, athlon, k6, k6-2, k6-3, i386, i486, i586 &#40;Pentium&#41;, i686
    # &#40;PentiumPro&#41;, pentium, pentium-mmx, pentiumpro, pentium2 &#40;Celeron&#41;,
    # pentium3, and pentium4.
    #
    # Note that Gentoo Linux 1.4 and higher include at least gcc-3.2.
    # 
    # CPU types supported in gcc-2.95*&#58; k6, i386, i486, i586 &#40;Pentium&#41;, i686
    # &#40;Pentium Pro&#41;, pentium, pentiumpro Gentoo Linux 1.2 and below use gcc-2.95*
    #
    # CRITICAL WARNINGS&#58; ****************************************************** #
    # K6 markings are deceptive. Avoid setting -march for them. See Bug #24379. #
    # Pentium-M CPU's should not enable sse2 until at least gcc-3.4. Bug 50616. #
    # ************************************************************************* #
    #
    # Decent examples&#58;
    #
    #CFLAGS="-mcpu=athlon-xp -O3 -pipe"
    CFLAGS="-march=pentium4 -O3 -pipe -fomit-frame-pointer"
    
    # If you set a CFLAGS above, then this line will set your default C++ flags to
    # the same settings.
    CXXFLAGS="$&#123;CFLAGS&#125;"
    
    # 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.
    #
    #ACCEPT_KEYWORDS=
    
    # Portage Directories
    # ===================
    #
    # Each of these settings controls an aspect of portage's storage and file
    # system usage. If you change any of these, be sure it is available when
    # you try to use portage. *** DO NOT INCLUDE A TRAILING "/" ***
    #
    # PORTAGE_TMPDIR is the location portage will use for compilations and
    #     temporary storage of data. This can get VERY large depending upon
    #     the application being installed.
    #PORTAGE_TMPDIR=/var/tmp
    #
    # PORTDIR is the location of the portage tree. This is the repository
    #     for all profile information as well as all ebuilds. If you change
    #     this, you must update your /etc/make.profile symlink accordingly.
    #PORTDIR=/usr/portage
    #
    # DISTDIR is where all of the source code tarballs will be placed for
    #     emerges. The source code is maintained here unless you delete
    #     it. The entire repository of tarballs for gentoo is 9G. This is
    #     considerably more than any user will ever download. 2-3G is
    #     a large DISTDIR.
    #DISTDIR=$&#123;PORTDIR&#125;/distfiles
    #
    # PKGDIR is the location of binary packages that you can have created
    #     with '--buildpkg' or '-b' while emerging a package. This can get
    #     upto several hundred megs, or even a few gigs.
    #PKGDIR=$&#123;PORTDIR&#125;/packages
    #
    # PORT_LOGDIR is the location where portage will store all the logs it
    #     creates from each individual merge. They are stored as NNNN-$PF.log
    #     in the directory specified. This is disabled until you enable it by
    #     providing a directory. Permissions will be modified as needed IF the
    #     directory exists, otherwise logging will be disabled. NNNN is the
    #     increment at the time the log is created. Logs are thus sequential.
    #PORT_LOGDIR=/var/log/portage
    #
    # PORTDIR_OVERLAY is a directory where local ebuilds may be stored without
    #     concern that they will be deleted by rsync updates. Default is not
    #     defined.
    #PORTDIR_OVERLAY=/usr/local/portage
    
    # Fetching files 
    # ==============
    #
    # If you need to set a proxy for wget or lukemftp, add the appropriate "export
    # ftp_proxy=<proxy>" and "export http_proxy=<proxy>" lines to /etc/profile if
    # all users on your system should use them.
    #
    # Portage uses wget by default. Here are some settings for some alternate
    # downloaders -- note that you need to merge these programs first before they
    # will be available.
    #
    # Default fetch command &#40;5 tries, passive ftp for firewall compatibility&#41;
    #FETCHCOMMAND="/usr/bin/wget -t 5 --passive-ftp \$&#123;URI&#125; -P \$&#123;DISTDIR&#125;"
    #RESUMECOMMAND="/usr/bin/wget -c -t 5 --passive-ftp \$&#123;URI&#125; -P \$&#123;DISTDIR&#125;"
    #
    # Using wget, ratelimiting downloads
    #FETCHCOMMAND="/usr/bin/wget -t 5 --passive-ftp --limit-rate=200k \$&#123;URI&#125; -P \$&#123;DISTDIR&#125;"
    #RESUMECOMMAND="/usr/bin/wget -c -t 5 --passive-ftp --limit-rate=200k \$&#123;URI&#125; -P \$&#123;DISTDIR&#125;"
    #
    # Lukemftp &#40;BSD ftp&#41;&#58;
    #FETCHCOMMAND="/usr/bin/lukemftp -s -a -o \$&#123;DISTDIR&#125;/\$&#123;FILE&#125; \$&#123;URI&#125;"
    #RESUMECOMMAND="/usr/bin/lukemftp -s -a -R -o \$&#123;DISTDIR&#125;/\$&#123;FILE&#125; \$&#123;URI&#125;"
    #
    # Portage uses GENTOO_MIRRORS to specify mirrors to use for source retrieval.
    # The list is a space separated list which is read left to right. If you use
    # another mirror we highly recommend leaving the default mirror at the end of
    # the list so that portage will fall back to it if the files cannot be found
    # on your specified mirror. We _HIGHLY_ recommend that you change this setting
    # to a nearby mirror by merging and using the 'mirrorselect' tool.
    #GENTOO_MIRRORS="<your_mirror_here> http&#58;//distfiles.gentoo.org http&#58;//www.ibiblio.org/pub/Linux/distributions/gentoo"
    #
    # Portage uses PORTAGE_BINHOST to specify mirrors for prebuilt-binary packages.
    # The list is a single entry specifying the full address of the directory
    # serving the tbz2's for your system. Running emerge with either '--getbinpkg'
    # or '--getbinpkgonly' will cause portage to retrieve the metadata from all
    # packages in the directory specified, and use that data to determine what will
    # be downloaded and merged. '-g' or '-gK' are the recommend parameters. Please
    # consult the man pages and 'emerge --help' for more information. For FTP, the
    # default connection is passive -- If you require an active connection, affix
    # an asterisk &#40;*&#41; to the end of the host&#58;port string before the path.
    #PORTAGE_BINHOST="http&#58;//grp.mirror.site/gentoo/grp/1.4/i686/athlon-xp/"
    # This ftp connection is passive ftp.
    #PORTAGE_BINHOST="ftp&#58;//login&#58;pass@grp.mirror.site/pub/grp/i686/athlon-xp/"
    # This ftp connection is active ftp.
    #PORTAGE_BINHOST="ftp&#58;//login&#58;pass@grp.mirror.site&#58;21*/pub/grp/i686/athlon-xp/"
    
    # Synchronizing Portage
    # =====================
    #
    # Each of these settings affects how Gentoo synchronizes your Portage tree.
    # Synchronization is handled by rsync and these settings allow some control
    # over how it is done.
    #
    #
    # SYNC is the server used by rsync to retrieve a localized rsync mirror
    #     rotation. This allows you to select servers that are geographically
    #     close to you, yet still distribute the load over a number of servers.
    #     Please do not single out specific rsync mirrors. Doing so places undue
    #     stress on particular mirrors.  Instead you may use one of the following
    #     continent specific rotations&#58;
    #
    #   Default&#58;       "rsync&#58;//rsync.gentoo.org/gentoo-portage"
    #   North America&#58; "rsync&#58;//rsync.namerica.gentoo.org/gentoo-portage"
    #   South America&#58; "rsync&#58;//rsync.samerica.gentoo.org/gentoo-portage"
    #   Europe&#58;        "rsync&#58;//rsync.europe.gentoo.org/gentoo-portage"
    #   Asia&#58;          "rsync&#58;//rsync.asia.gentoo.org/gentoo-portage"
    #   Australia&#58;     "rsync&#58;//rsync.au.gentoo.org/gentoo-portage"
    #SYNC="rsync&#58;//rsync.gentoo.org/gentoo-portage"
    #
    # RSYNC_RETRIES sets the number of times portage will attempt to retrieve
    #     a current portage tree before it exits with an error. This allows
    #     for a more successful retrieval without user intervention most times.
    #RSYNC_RETRIES="3"
    #
    # RSYNC_TIMEOUT sets the length of time rsync will wait before it times out
    #     on a connection. Most users will benefit from this setting as it will
    #     reduce the amount of 'dead air' they experience when they run across
    #     the occasional, unreachable mirror. Dialup users might want to set this
    #     value up around the 300 second mark.
    #RSYNC_TIMEOUT=180
    
    # Advanced Features
    # =================
    #
    # MAKEOPTS provides extra options that may be passed to 'make' when a
    #     program is compiled. Presently the only use is for specifying
    #     the number of parallel makes &#40;-j&#41; to perform. The suggested number
    #     for parallel makes is CPUs+1.
    MAKEOPTS="-j3"
    #
    # PORTAGE_NICENESS provides a default increment to emerge's niceness level.
    #     Note&#58; This is an increment. Running emerge in a niced environment will
    #     reduce it further. Default is unset.
    PORTAGE_NICENESS=19
    #
    # AUTOCLEAN enables portage to automatically clean out older or overlapping
    #     packages from the system after every successful merge. This is the
    #     same as running 'emerge -c' after every merge. Set with&#58; "yes" or "no".
    #     This does not affect the unpacked source. See 'noclean' below.
    AUTOCLEAN="yes"
    #
    # PORTAGE_TMPFS is a location where portage may create temporary files.
    #     If specified, portage will use this directory whenever possible
    #     for all rapid operations such as lockfiles and transient data.
    #     It is _highly_ recommended that this be a tmpfs or ramdisk. Do not
    #     set this to anything that does not give a significant performance
    #     enhancement and proper FS compliance for locks and read/write.
    #     /dev/shm is a glibc mandated tmpfs, and should be a reasonable
    #     setting for all linux kernel+glibc based systems.
    #PORTAGE_TMPFS="/dev/shm"
    #
    # FEATURES are settings that affect the functionality of portage. Most of
    #     these settings are for developer use, but some are available to non-
    #     developers as well. 
    #
    #  'autoaddcvs'  causes portage to automatically try to add files to cvs
    #                that will have to be added later. Done at generation times
    #                and only has an effect when 'cvs' is also set.
    #  'buildpkg'    causes binary packages to be created of all packages that 
    #                are being merged.
    #  'ccache'      enables ccache support via CC.
    #  'collision-protect'
    #                prevents packages from overwriting files that are owned by
    #                another package or by no package at all.
    #  'cvs'         causes portage to enable all cvs features &#40;commits, adds&#41;,
    #                and to apply all USE flags in SRC_URI for digests -- for
    #                developers only.
    #  'digest'      causes digests to be generated for all packages being merged.
    #  'distcc'      enables distcc support via CC.
    #  'distlocks'   enables distfiles locking using fcntl or hardlinks. This
    #                is enabled by default. Tools exist to help clean the locks
    #                after crashes&#58; /usr/lib/portage/bin/clean_locks.
    #  'fixpackages' allows portage to fix binary packages that are stored in
    #                PKGDIR. This can consume a lot of time. 'fixpackages' is
    #                also a script that can be run at any given time to force
    #                the same actions.
    #  'gpg'         enables basic verification of Manifest files using gpg.
    #                This features is UNDER DEVELOPMENT and reacts to features
    #                of strict and severe. Heavy use of gpg sigs is coming.
    #  'keeptemp'    prevents the clean phase from deleting the temp files &#40;$T&#41; 
    #                from a merge.
    #  'keepwork'    prevents the clean phase from deleting the WORKDIR.
    #  'maketest'    causes ebuilds to perform testing phases if they are capable
    #                of it. Some packages support this automaticaly via makefiles.
    #  'noauto'      causes ebuild to perform only the action requested and 
    #                not any other required actions like clean or unpack -- for
    #                debugging purposes only.
    #  'noclean'     prevents portage from removing the source and temporary files 
    #                after a merge -- for debugging purposes only. 
    #  'nostrip'     prevents the stripping of binaries.
    #  'notitles'    disables xterm titlebar updates &#40;which contain status info&#41;. 
    #  'sandbox'     enables sandboxing when running emerge and ebuild.
    #  'strict'      causes portage to react strongly to conditions that are
    #                potentially dangerous, like missing/incorrect Manifest files.
    #  'userpriv'    allows portage to drop root privileges while it is compiling,
    #                as a security measure.  As a side effect this can remove 
    #                sandbox access violations for users. 
    #  'usersandbox' enables sandboxing while portage is running under userpriv.
    #FEATURES="sandbox buildpkg ccache distcc userpriv usersandbox notitles noclean noauto cvs keeptemp keepwork autoaddcvs"
    #FEATURES="sandbox ccache distcc distlocks autoaddcvs"
    #
    # CCACHE_SIZE sets the space use limitations for ccache. The default size is
    #     2G, and will be set if not defined otherwise and ccache is in features. 
    #     Portage will set the default ccache dir if it is not present in the
    #     user's environment, for userpriv it sets&#58; $&#123;PORTAGE_TMPDIR&#125;/ccache
    #     &#40;/var/tmp/ccache&#41;, and for regular use the default is /root/.ccache.
    #     Sizes are specified with 'G' 'M' or 'K'.
    #     '2G' for 2 gigabytes, '2048M' for 2048 megabytes &#40;same as 2G&#41;.
    #CCACHE_SIZE="512M"
    #
    # DISTCC_DIR sets the temporary space used by distcc.
    #DISTCC_DIR="$&#123;PORTAGE_TMPDIR&#125;/.distcc"
    #
    # RSYNC_EXCLUDEFROM is a file that portage will pass to rsync when it updates
    #     the portage tree. Specific chunks of the tree may be excluded from
    #     consideration. This may cause dependency failures if you are not careful.
    #     The file format is one pattern per line, blanks and ';' or '#' lines are
    #     comments. See 'man rsync' for more details on the exclude-from format.
    #RSYNC_EXCLUDEFROM=/etc/portage/rsync_excludes
    
    ALSA_CARDS="via82xx"
    If you guys don't see anything here, I'm going to go with emerge --emptytree world. And if that fails, I'll go back to a suspend2 source.

    A_T

  9. #9
    Just Joined!
    Join Date
    Aug 2005
    Posts
    11

    Hardware

    FYI, this is a 3Ghz P4 with HT. It has all the sse and sse2, and all that crap.

    Here's the asus site:
    http://usa.asus.com/products.aspx?l1...11&modelmenu=1

    Also, I found some oddities in my kernel config...I did it remotely last time I compiled it, so I'm wondering if I got confused and set options for the system I was on, and not this one...

    I'll fill you all in. Any other ideas would be appreciated.

    A_T

  10. #10
    Linux Enthusiast
    Join Date
    Dec 2004
    Location
    Rockin' in the USA!!!
    Posts
    603
    I had a thought.... if he's using ~x86, could that have installed a buggy version of gcc, or (since I've never done stage3) is that already installed?

Page 1 of 2 1 2 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •