HOT !!!! >...instalation or gcc3 or bios compiling error?

[gspir2004]

On an AthlonXP2800+(barton),7NJS-ultra-NF2 Chaintech (bios=8/2004)motherboard,1,5G mem DUAL-DDR400(3*0,5G),sata_promise 80G SEAGATE + 120G WD ide + 40G WD ide,cx8800 KWorld+bt878WinTV,CBOX3,NVidia5700 ultra 256M........

when setting FSB of CPU from bios to lower I GET NO ERRORS when compiling....when i set to the safe linit of 166MHz then i can't DO NO compilation at all!!!!!(is GENTOO too fast or what..!!! )
SO WHEN I DO COMPILATION I ALWAYS F..... MY CPU SPEED AND MEM SPEED TOO.xi-xi
Then I GET FULL POWER UP and GENTOO ROCKS!!!!!!!!!

STAGE1-X86.2004.3+Gentoo-dev-sources+gcc3.4+ARCH=~86+(allmost full USE)+"march=athlon-xp -pipe -fomit-frame-point"+MAKEOPTS="-j3 or -j2"

[robet]

Hello, and welcome...
A few tips first off... try to report exactly what the problem is rather than hinting at it. When you say compile error, what do you mean? A bootstrap fails, or compiling a program in a working environment fails? What is the message you get?
Also, try to order your thoughts into "paragraphs" and "sentences." Usage of "periods" is a plus. "Commas" help.
So, to help fix your problem, we'll need a bit more information... post your /etc/make.conf and the errors you get compiling, plus about 20-30 lines before and after, if applicable.
Good luck!
_________________
no software patents in europe! | adopt an unanswered post.

[gspir2004]

i talk about unexpected errors....not depencies erros or comflicts on packages that they are against it's other.
now all are OK!!!
form stage1-x86-2004.3(sh bootstarp.sh)+gentoo-dev-sources+reiserfs4_patch...!!!!!!!!!!! to full working system!!!!!!

# Copyright 2000-2003 Daniel Robbins, Gentoo Technologies, Inc.
# Contains local system settings for Portage system
# $Header: /home/cvsroot/gentoo-src/portage/cnf/make.conf,v 1.70 2004/01/12 07:34:38 carpaski Exp $

# 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/use-howto.html
#
# The available list of use flags with descriptions is in your portage tree.
# Use 'less' to view them: --> less /usr/portage/profiles/use.desc <--
#
# 'ufed' is an ncurses/dialog interface available in portage to make handling
# useflags for you. 'emerge app-admin/ufed'
#
USE="3dnow 3dnowex aac acl acpi activefilter adns aim amd apache2 \
audiofile avantgo bcmath bdf bidi bluetooth bzlib cap cddb cdinstall \
cdparanoia cdrom cgi chroot cjk client cpdflib ctype curl \
curlwrappers dba dio divx4linux djbfft dnd droproot dv dvb dvd dvdr \
dvdread edl eds emacs emacs-w3 erandom exif ext-png ext-zlib \
extensions faac faad fastcgi fbcon ffmpeg flash fluidsynth fmod \
freetype freewnn ftp gb gcl gd geoip gimp gimpprint ginac glade glgd \
glut gmp gmtfull gnomedb gnuplot gps graphviz gs gsl hal hardenedphp \
hbci hdf iconv icq ide idl ieee1394 image imap imlib2 innodb ipv6 \
irda irmc j2ee jabber java javacomm javadoc javamail javascript jbig \
jboss jce jms jmx joystick jp2 jpeg2k jta jython kadu-modules \
kadu-voice kakasi kerberos krb4 latex lcms leim libdsk libgd libgda \
libsamplerate live lm_sensors lua lufsusermount lzo lzw lzw-tiff \
m17n-lib maildir matroska mbox mcal mdb memlimit mhash migemo mime \
mixer mmap mmx mmx2 mng mozcalendar mozdevelop mozp3p mozsvg \
mozxmlterm mp3 mpeg4 mpi mplayer msn mule music nagios-dns nagios-ntp \
nagios-ping nagios-ssh native net network nis nptl ntlm nvidia nviz \
oav objc ocaml offensive ofx openal opie oscar ospfapi parse-clocks \
pcap pcntl pcre pdf pg-hier pg-intdatetime pg-vacuumdelay php physfs \
pic plotutils portaudio posix postgresql ppds print pthreads quotes \
rhino rogue rplay S3TC sasl servlet-2.3 servlet-2.4 session \
sftplogging shaper shared sharedmem sheep silc simplexml skk slp \
smime sndfile sockets socks5 softquota sox sse sse2 stencil-buffer \
stroke svg sysvipc szip t1lib tga theora tidy transcode unicode usb \
v4l v4l2 vda vhosts videos virus-scan wifi wmf wxwin wxwindows X509 \
xatrix xchatdccserver xchattext xemacs xgetdefault xine xmlrpc xosd \
xpm xrandr xscreensaver xsl xvid xvmc yahoo yv12 zvbi -libg"

# Host Setting
# ============
#
# If you are using a Pentium Pro or greater processor, leave this line as-is;
# otherwise, change to i586, i486 or i386 as appropriate. All modern systems
# (even Athlons) should use "i686-pc-linux-gnu". All K6's are i586.
#
# i686 CHOST is for x86 arch above pentium-mmx
# for pentium-mmx comment the chlst below and uncomment
# CHOST="i586-pc-linux-gnu"
#
#
CHOST="i686-pc-linux-gnu"
#
#CHOST="i586-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 (and in some cases the libraries it uses) 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 (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: athlon-xp, athlon-mp,
# athlon-tbird, athlon, k6, k6-2, k6-3, i386, i486, i586 (Pentium), i686
# (PentiumPro), pentium, pentium-mmx, pentiumpro, pentium2 (Celeron),
# pentium3, and pentium4.
#
# Note that Gentoo Linux 1.4 and higher include at least gcc-3.2.
#
# CPU types supported in gcc-2.95*: k6, i386, i486, i586 (Pentium), i686
# (Pentium Pro), pentium, pentiumpro Gentoo Linux 1.2 and below use gcc-2.95*
#
# CRITICAL WARNINGS: ****************************************************** #
# K6 markings are deceptive. Avoid setting -march for them. See Bug #24379. #
# ************************************************************************* #
#
# Decent examples:

# Unset ONE of the cflag examples that best resembles your cpu

#
# Athlon class cpu's below
#
#CFLAGS="-march=athlon -O2 -fomit-frame-pointer -pipe"
#CFLAGS="-march=athlon-tbird -O2 -fomit-frame-pointer -pipe"
CFLAGS="-march=athlon-xp -O2 -fomit-frame-pointer -pipe"
#CFLAGS="-march=athlon-4 -O2 -fomit-frame-pointer -pipe"

#
# Pentium class cpu's below
#
#CFLAGS="-march=pentium2 -O2 -fomit-frame-pointer -pipe"
#CFLAGS="-march=pentium3 -O2 -fomit-frame-pointer -pipe"
#CFLAGS="-march=pentium4 -O2 -fomit-frame-pointer -pipe"


# If you set a CFLAGS above, then this line will set your default C++ flags to
# the same settings.
CXXFLAGS="${CFLAGS}"
#
# Setting LDFLAGS is still experimental use them only if you are truly experienced
#
# man ld to learn how use flags affect gentoo linux
#
#LDFLAGS="-Wl,-O1 -Wl,--relax -Wl,--enable-new-dtags -Wl,--sort-common -s"
#
#
# 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="~x86"

# 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. This directory
# itself can reach 200M. WE DO NOT RECOMMEND that you change this.
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=${PORTDIR}/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=${PORTDIR}/packages
#
# PORT_LOGDIR is the location where portage will store all the logs it
# creates from each individual merge. They are stored as YYMMDD-$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.
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 (5 tries, passive ftp for firewall compatibility)
#FETCHCOMMAND="/usr/bin/wget -t 5 --passive-ftp \${URI} -P \${DISTDIR}"
#RESUMECOMMAND="/usr/bin/wget -c -t 5 --passive-ftp \${URI} -P \${DISTDIR}"
#
# Using wget, ratelimiting downloads
#FETCHCOMMAND="/usr/bin/wget -t 5 --passive-ftp --limit-rate=200k \${URI} -P \${DISTDIR}"
#RESUMECOMMAND="/usr/bin/wget -c -t 5 --passive-ftp --limit-rate=200k \${URI} -P \${DISTDIR}"
#
# Lukemftp (BSD ftp):
#FETCHCOMMAND="/usr/bin/lukemftp -s -a -o \${DISTDIR}/\${FILE} \${URI}"
#RESUMECOMMAND="/usr/bin/lukemftp -s -a -R -o \${DISTDIR}/\${FILE} \${URI}"
#
# Prozilla (turbo downloader)
#FETCHCOMMAND='/usr/bin/proz --no-getch -s ${URI} -P ${DISTDIR}'
#
# Portage uses GENTOO_MIRRORS to specify mirrors to use for source retrieval.
# The list is a space seperated 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.
#
# Portage uses PORTAGE_BINHOST to specify mirrors for prebuilt-binary packages.
# The list is a single extry 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.
#PORTAGE_BINHOST="ftp://login:pass@grp.mirror.site/pub/grp/i686/athlon-xp/"
#PORTAGE_BINHOST="http://grp.mirror.site/gentoo/grp/1.4/i686/athlon-xp/"

# Synchronizing Portage
# =====================
#
# Each of these settings effects 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:
#
# Default: "rsync://rsync.gentoo.org/gentoo-portage"
# North America: "rsync://rsync.namerica.gentoo.org/gentoo-portage"
# South America: "rsync://rsync.samerica.gentoo.org/gentoo-portage"
# Europe: "rsync://rsync.europe.gentoo.org/gentoo-portage"
# Asia: "rsync://rsync.asia.gentoo.org/gentoo-portage"
# Australia: "rsync://rsync.au.gentoo.org/gentoo-portage"
#SYNC="rsync://rsync.gentoo.org/gentoo-portage"
SYNC="rsync://rsync.europe.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 (-j) 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: This is an increment. Running emerge in a niced environment will
# reduce it further. Default is unset.
#PORTAGE_NICENESS=3
#
# 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: "yes" or "no".
# This does not affect the unpacked source. See 'noclean' below.
AUTOCLEAN="yes"
#
# 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 merged.
# 'ccache' enables ccache support via CC.
# 'cvs' feature for developers that causes portage to enable all
# cvs features (commits, adds) and all USE flags in SRC_URI
# will be applied for digests.
# 'digest' autogenerate a digest for packages.
# 'distcc' enables distcc support via CC.
# '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.
# 'keeptemp' prevents the clean phase from deleting the temp files ($T)
# from a merge.
# 'keepwork' prevents the clean phase from deleting the WORKDIR.
# 'noauto' causes ebuild to perform only the action requested and
# not any other required actions like clean or
# 'noclean' prevents portage from removing the source and temporary files
# after a merge -- for debugging purposes only.
# 'nostrip' prevents stripping of binaries.
# 'notitles' disables xterm titlebar updates (which contain status info).
# 'sandbox' enable sandbox-ing when running emerge and ebuild
# 'strict' causes portage to react strongly to conditions that
# have the potential to be dangerous -- like missing or
# incorrect Manifest files.
# 'userpriv' allows portage to drop root privleges while it is compiling
# as a security measure, and as a side effect this can remove
# sandbox access violations for users.
# 'usersandbox' enables sandboxing while portage is running under userpriv.
# unpack -- for debugging purposes only.
FEATURES="sandbox ccache buildpkg"
#
# 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: ${PORTAGE_TMPDIR}/ccache
# (/var/tmp/ccache), and for regular use the default is /root/.ccache.
# Sizes are specified with 'G' 'M' or 'K'.
# '4G' for 4 gigabytes, '4096M' for 4 gigabytes, etc... Default is 2G
CCACHE_SIZE="2G"
#
# DISTCC_DIR sets the temporary space used by distcc.
#DISTCC_DIR="${PORT_TMPDIR}/.distcc"
#
# RSYNC_EXCLUDEFROM is a file that portage will pass to rsync when it updates
# the portage tree. Specific chucks 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

[sarge]

Nice setup gspir2004...
but.. when were you used your mind last ? not all the time the more is better. in case of using USE variable for example. check only things you really want, or your binaries will be big and slow and u got many unneeded libraries and packages installed with your actual settings.

and finally, is your Athlon some special version with built-in SMP and that`s why you use -j3 ?? I bet that your problems with emerging was coz your system got overheated or you was behind DDR`s MHz capability.

sarge