Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Problem on bootstrap gcc unable to produce output files
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
unclefu
Tux's lil' helper
Tux's lil' helper


Joined: 24 Nov 2002
Posts: 85
Location: Herdecke, NRW, GERMANY

PostPosted: Tue Dec 07, 2004 1:52 pm    Post subject: Problem on bootstrap gcc unable to produce output files Reply with quote

I've got a Pentium-m System with a big problem:

running bootstrab.sh from 2004.3
i get:

Code:
>>> original instance of package unmerged safely.
 * Kernel headers are usually only used when recompiling glibc, as such, following the installation
 * of newer headers, it is advised that you re-merge glibc as follows:
 * emerge glibc
 * Failure to do so will cause glibc to not make use of newer features present in the updated kernel
 * headers.
>>> Regenerating /etc/ld.so.cache...
>>> sys-kernel/linux26-headers-2.6.8.1-r1 merged.
>>> emerge (2 of 6) sys-devel/gettext-0.14.1 to /
>>> md5 src_uri ;-) gettext-0.14.1.tar.gz
>>> md5 src_uri ;-) gettext-0.14.1-bootstrap.patch.bz2
>>> Unpacking source...
>>> Unpacking gettext-0.14.1.tar.gz to /var/tmp/portage/gettext-0.14.1/work
>>> Unpacking gettext-0.14.1-bootstrap.patch.bz2 to /var/tmp/portage/gettext-0.14.1/work
 * Applying gettext-0.14.1-bootstrap.patch ...                                                                         [ ok ]
 * Applying gettext-0.14.1-without_java.patch ...                                                                      [ ok ]
 * Applying gettext-0.14.1-no-java-tests.patch ...                                                                     [ ok ]
 * Patching ${S}/gettext-tools/examples/hello-c++-kde/admin/ltmain.sh ...
 *   Applying portage-1.4.1.patch ...
 *   Could not apply relink.patch!
 *   Applying max_cmd_len-1.5.0.patch ...
 *   Applying sed-1.4.3.patch ...
 *   Applying tmp-1.3.5.patch ...
 * Patching ${S}/config/ltmain.sh ...
 *   Applying portage-1.4.1.patch ...
 *   Applying max_cmd_len-1.5.0.patch ...
 *   Applying sed-1.4.3.patch ...
 *   Applying tmp-1.3.5.patch ...
 *   Applying fix-relink-1.4.0.patch ...
 * Applying uClibc/libtool patches ...
 * Using GNU config files from /usr/share/gnuconfig
 *  Updating gettext-tools/examples/hello-c++-kde/admin/config.sub                                                     [ ok ]
 *  Updating config/config.sub                                                                                         [ ok ]
 *  Updating gettext-tools/examples/hello-c++-kde/admin/config.guess                                                   [ ok ]
 *  Updating config/config.guess                                                                                       [ ok ]
>>> Source unpacked.
 * econf: updating /var/tmp/portage/gettext-0.14.1/work/gettext-0.14.1/gettext-tools/examples/hello-c++-kde/admin/config.guess with /usr/share/gnuconfig/config.guess
 * econf: updating /var/tmp/portage/gettext-0.14.1/work/gettext-0.14.1/gettext-tools/examples/hello-c++-kde/admin/config.sub with /usr/share/gnuconfig/config.sub
 * econf: updating /var/tmp/portage/gettext-0.14.1/work/gettext-0.14.1/config/config.guess with /usr/share/gnuconfig/config.guess
 * econf: updating /var/tmp/portage/gettext-0.14.1/work/gettext-0.14.1/config/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --without-java --without-included-gettext --enable-nls
configure: WARNING: If you wanted to set the --build type, don't use --host.
    If a cross compiler is detected then cross compile mode will be used.
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for i686-pc-linux-gnu-strip... no
checking for strip... strip
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
configure: creating ./config.status
config.status: creating Makefile
configure: configuring in autoconf-lib-link
configure: running /bin/sh './configure' --prefix=/usr  '--prefix=/usr' '--host=i686-pc-linux-gnu' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--datadir=/usr/share' '--sysconfdir=/etc' '--localstatedir=/var/lib' '--without-java' '--without-included-gettext' '--enable-nls' 'CC=gcc' 'CFLAGS=-O3 -march=pentium-m -mtune=pentium-m -pipe -ftracer -fomit-frame-pointer -ffast-math -momit-leaf-frame-pointers' 'CXXFLAGS=-O3 -march=pentium-m -mtune=pentium-m -pipe -ftracer -fomit-frame-pointer -ffast-math -momit-leaf-frame-pointers' 'CXX=gcc' 'host_alias=i686-pc-linux-gnu' --cache-file=/dev/null --srcdir=.
configure: WARNING: If you wanted to set the --build type, don't use --host.
    If a cross compiler is detected then cross compile mode will be used.
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for i686-pc-linux-gnu-strip... no
checking for strip... strip
checking for i686-pc-linux-gnu-gcc... gcc
checking for C compiler default output file name... configure: error: C compiler cannot create executables
See `config.log' for more details.
configure: error: /bin/sh './configure' failed for autoconf-lib-link

!!! ERROR: sys-devel/gettext-0.14.1 failed.
!!! Function econf, Line 447, Exitcode 1
!!! econf failed
!!! If you need support, post the topmost build error, NOT this status message.


i already emerged gcc 3.4.3 and glibc by myself.

what mistake could fault this error?
Back to top
View user's profile Send private message
unclefu
Tux's lil' helper
Tux's lil' helper


Joined: 24 Nov 2002
Posts: 85
Location: Herdecke, NRW, GERMANY

PostPosted: Tue Dec 07, 2004 1:56 pm    Post subject: Reply with quote

This is the complete message... bootstrap emerges linux26-headers every time... is this ok?

Code:
livecd gettext-0.14.1 # /usr/portage/scripts/bootstrap.sh
shell-init: could not get current directory: getcwd: cannot access parent directories: No such file or directory

Gentoo Linux; http://www.gentoo.org/
Copyright 1999-2004 Gentoo Foundation; Distributed under the GPLv2
Starting Bootstrap of base system ...
-------------------------------------------------------------------------------
 * Using baselayout : >=sys-apps/baselayout-1.9.4-r3
 * Using portage    : >=sys-apps/portage-2.0.51
 * Using os-headers : >=sys-kernel/linux26-headers-2.6.8.1-r1
 * Using binutils   : >=sys-devel/binutils-2.14.90.0.8-r1
 * Using gcc        : >=sys-devel/gcc-3.3.4-r1
 * Using gettext    : sys-devel/gettext
 * Using libc       : virtual/libc
 * Using texinfo    : sys-apps/texinfo
 * Using zlib       : sys-libs/zlib
 * Using ncurses    : sys-libs/ncurses
-------------------------------------------------------------------------------
Configuring environment ...
 * GENTOO_MIRRORS='http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror/ ftp://linux.rz.ruhr-uni-bochum.de/gentoo-mirror/ http://ftp.uni-erlangen.de/pub/mirrors/gentoo ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo ftp://ftp.join.uni-muenster.de/pub/linux/distributions/gentoo ftp://ftp.wh2.tu-dresden.de/pub/mirrors/gentoo ftp://ftp.join.uni-muenster.de/pub/linux/distributions/gentoo ftp://ftp6.uni-muenster.de/pub/linux/distributions/gentoo http://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ ftp://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ ftp://ftp.gentoo.mesh-solutions.com/gentoo/ ftp://files.gentoo.gr'
 * PORTDIR='/usr/portage'
 * DISTDIR='/usr/portage/distfiles'
 * PKGDIR='/usr/portage/packages'
 * PORTAGE_TMPDIR='/var/tmp'
 * CFLAGS='-O3 -march=pentium-m -mtune=pentium-m -pipe -ftracer -fomit-frame-pointer -ffast-math -momit-leaf-frame-pointers'
 * CHOST='i686-pc-linux-gnu'
 * CXXFLAGS='-O3 -march=pentium-m -mtune=pentium-m -pipe -ftracer -fomit-frame-pointer -ffast-math -momit-leaf-frame-pointers'
 * MAKEOPTS='-j2'
 * ACCEPT_KEYWORDS='x86 ~x86'
 * FEATURES='autoaddcvs autoconfig ccache distlocks sandbox sfperms'
-------------------------------------------------------------------------------
Calculating dependencies ...done!
>>> emerge (1 of 6) sys-kernel/linux26-headers-2.6.8.1-r1 to /
>>> md5 src_uri ;-) linux-2.6.8.1.tar.bz2
>>> Unpacking source...
>>> Unpacking linux-2.6.8.1.tar.bz2 to /var/tmp/portage/linux26-headers-2.6.8.1-r1/work

...

>>> original instance of package unmerged safely.
 * Kernel headers are usually only used when recompiling glibc, as such, following the installation
 * of newer headers, it is advised that you re-merge glibc as follows:
 * emerge glibc
 * Failure to do so will cause glibc to not make use of newer features present in the updated kernel
 * headers.
>>> Regenerating /etc/ld.so.cache...
>>> sys-kernel/linux26-headers-2.6.8.1-r1 merged.
>>> emerge (2 of 6) sys-devel/gettext-0.14.1 to /
>>> md5 src_uri ;-) gettext-0.14.1.tar.gz
>>> md5 src_uri ;-) gettext-0.14.1-bootstrap.patch.bz2
>>> Unpacking source...
>>> Unpacking gettext-0.14.1.tar.gz to /var/tmp/portage/gettext-0.14.1/work
>>> Unpacking gettext-0.14.1-bootstrap.patch.bz2 to /var/tmp/portage/gettext-0.14.1/work
 * Applying gettext-0.14.1-bootstrap.patch ...                                                                         [ ok ]
 * Applying gettext-0.14.1-without_java.patch ...                                                                      [ ok ]
 * Applying gettext-0.14.1-no-java-tests.patch ...                                                                     [ ok ]
 * Patching ${S}/gettext-tools/examples/hello-c++-kde/admin/ltmain.sh ...
 *   Applying portage-1.4.1.patch ...
 *   Could not apply relink.patch!
 *   Applying max_cmd_len-1.5.0.patch ...
 *   Applying sed-1.4.3.patch ...
 *   Applying tmp-1.3.5.patch ...
 * Patching ${S}/config/ltmain.sh ...
 *   Applying portage-1.4.1.patch ...
 *   Applying max_cmd_len-1.5.0.patch ...
 *   Applying sed-1.4.3.patch ...
 *   Applying tmp-1.3.5.patch ...
 *   Applying fix-relink-1.4.0.patch ...
 * Applying uClibc/libtool patches ...
 * Using GNU config files from /usr/share/gnuconfig
 *  Updating gettext-tools/examples/hello-c++-kde/admin/config.sub                                                     [ ok ]
 *  Updating config/config.sub                                                                                         [ ok ]
 *  Updating gettext-tools/examples/hello-c++-kde/admin/config.guess                                                   [ ok ]
 *  Updating config/config.guess                                                                                       [ ok ]
>>> Source unpacked.
 * econf: updating /var/tmp/portage/gettext-0.14.1/work/gettext-0.14.1/gettext-tools/examples/hello-c++-kde/admin/config.guess with /usr/share/gnuconfig/config.guess
 * econf: updating /var/tmp/portage/gettext-0.14.1/work/gettext-0.14.1/gettext-tools/examples/hello-c++-kde/admin/config.sub with /usr/share/gnuconfig/config.sub
 * econf: updating /var/tmp/portage/gettext-0.14.1/work/gettext-0.14.1/config/config.guess with /usr/share/gnuconfig/config.guess
 * econf: updating /var/tmp/portage/gettext-0.14.1/work/gettext-0.14.1/config/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --without-java --without-included-gettext --enable-nls
configure: WARNING: If you wanted to set the --build type, don't use --host.
    If a cross compiler is detected then cross compile mode will be used.
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for i686-pc-linux-gnu-strip... no
checking for strip... strip
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
configure: creating ./config.status
config.status: creating Makefile
configure: configuring in autoconf-lib-link
configure: running /bin/sh './configure' --prefix=/usr  '--prefix=/usr' '--host=i686-pc-linux-gnu' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--datadir=/usr/share' '--sysconfdir=/etc' '--localstatedir=/var/lib' '--without-java' '--without-included-gettext' '--enable-nls' 'CC=gcc' 'CFLAGS=-O3 -march=pentium-m -mtune=pentium-m -pipe -ftracer -fomit-frame-pointer -ffast-math -momit-leaf-frame-pointers' 'CXXFLAGS=-O3 -march=pentium-m -mtune=pentium-m -pipe -ftracer -fomit-frame-pointer -ffast-math -momit-leaf-frame-pointers' 'CXX=gcc' 'host_alias=i686-pc-linux-gnu' --cache-file=/dev/null --srcdir=.
configure: WARNING: If you wanted to set the --build type, don't use --host.
    If a cross compiler is detected then cross compile mode will be used.
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for i686-pc-linux-gnu-strip... no
checking for strip... strip
checking for i686-pc-linux-gnu-gcc... gcc
checking for C compiler default output file name... configure: error: C compiler cannot create executables
See `config.log' for more details.
configure: error: /bin/sh './configure' failed for autoconf-lib-link

!!! ERROR: sys-devel/gettext-0.14.1 failed.
!!! Function econf, Line 447, Exitcode 1
!!! econf failed
!!! If you need support, post the topmost build error, NOT this status message.
Back to top
View user's profile Send private message
yaneurabeya
Veteran
Veteran


Joined: 13 May 2004
Posts: 1754
Location: Seattle

PostPosted: Tue Dec 07, 2004 3:00 pm    Post subject: Reply with quote

Try running gcc-config -l and then run gcc-config 1 if a compiler is listed with the -l flag. I dunno, it solved part of my issues, but I can't seem to compile with distcc ;(...
Back to top
View user's profile Send private message
yaneurabeya
Veteran
Veteran


Joined: 13 May 2004
Posts: 1754
Location: Seattle

PostPosted: Tue Dec 07, 2004 3:18 pm    Post subject: Reply with quote

Also make sure that your compiler prefix in CCHOST fits your output in gcc-config -l. That's what was screwing me up. Lol. I didn't know that they didn't have a gcc-i586... version installed
Back to top
View user's profile Send private message
unclefu
Tux's lil' helper
Tux's lil' helper


Joined: 24 Nov 2002
Posts: 85
Location: Herdecke, NRW, GERMANY

PostPosted: Tue Dec 07, 2004 5:49 pm    Post subject: Reply with quote

i have
i386-pc-linux-gnu-3.3.4
...
but where is the cchost file?
in make.conf?
Back to top
View user's profile Send private message
robet
l33t
l33t


Joined: 06 Sep 2004
Posts: 807
Location: Earth/NorthAmerica/USA/NY

PostPosted: Tue Dec 07, 2004 6:03 pm    Post subject: Reply with quote

Can you write as much of your make.conf as possible here? I'd bet the problem's there.
_________________
no software patents in europe! | adopt an unanswered post.
Back to top
View user's profile Send private message
unclefu
Tux's lil' helper
Tux's lil' helper


Joined: 24 Nov 2002
Posts: 85
Location: Herdecke, NRW, GERMANY

PostPosted: Tue Dec 07, 2004 6:29 pm    Post subject: Here comes a big one Reply with quote

Code:

# 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 flags in this make.conf have been pre-set at the bottom of the file
# - ali3nx

# 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="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 (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=pentium-m -O3 -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.eliteitminds.com/gentoo-portage"
SYNC="rsync://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 (-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"
#
# 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

#############
#
#  Use the USE= below during bootstrap to ensure you have no problems during bootstrap
#  IMPORTANT!!!  Adjust mmx, mmx2, sse, sse2, 3dnow, 3dnowext use flags appropriately
#                for your cpu type or you will have a bad day
#                public service message from ali3nx
#
#  USE adjusted to reflect gcj gcc ebuild bug. 29/09/2004

USE="nptl -X  acpi"
GENTOO_MIRRORS="http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror/ ftp://linux.rz.ruhr-uni-bochum.de/gentoo-mirror/ http://ftp.uni-erlangen.de/pub/mirrors/gentoo ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo ftp://ftp.join.uni-muenster.de/pub/linux/distributions/gentoo ftp://ftp.wh2.tu-dresden.de/pub/mirrors/gentoo ftp://ftp.join.uni-muenster.de/pub/linux/distributions/gentoo ftp://ftp6.uni-muenster.de/pub/linux/distributions/gentoo http://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ ftp://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ ftp://ftp.gentoo.mesh-solutions.com/gentoo/ ftp://files.gentoo.gr"


thats all....

btw he's doin it again, even after a complete new start
Back to top
View user's profile Send private message
unclefu
Tux's lil' helper
Tux's lil' helper


Joined: 24 Nov 2002
Posts: 85
Location: Herdecke, NRW, GERMANY

PostPosted: Tue Dec 07, 2004 6:31 pm    Post subject: Reply with quote

i emerged gcc myself and did a gcc-config 2 think it is working...
(hope so)

when im sure ill mark the topic solved
Back to top
View user's profile Send private message
NismoC32
Apprentice
Apprentice


Joined: 07 Apr 2003
Posts: 214

PostPosted: Tue Dec 07, 2004 10:37 pm    Post subject: Reply with quote

Have the same problem here.
Using AMD64 LiveCD 2004.03.

Anyone found a solution ?
Back to top
View user's profile Send private message
unclefu
Tux's lil' helper
Tux's lil' helper


Joined: 24 Nov 2002
Posts: 85
Location: Herdecke, NRW, GERMANY

PostPosted: Wed Dec 08, 2004 1:14 pm    Post subject: Reply with quote

i had the problem solved yesterday.. but at emerge system.... there was a crash.

now i tried it with ACCEPT_KEYWORDS="x86" and /etc/portage/accept.packages.
Back to top
View user's profile Send private message
saintdev
n00b
n00b


Joined: 13 Jul 2004
Posts: 60
Location: CO, USA

PostPosted: Thu Dec 09, 2004 12:36 am    Post subject: Reply with quote

Nismo, I had the same problem as well. My problem turned out to be having -mtune in my CFLAGS when the LiveCD was only using GCC 3.3.4. So GCC failed, if you look in the configure.log for distcc you will see what the exact problem with GCC is. I replaced -mtune with -mcpu and everything went fine! So post your CFLAGS and we can probably figure it out.

unclefu: your probelm was probably the -march=pentium-m. As far as GCC 3.3.4 is concerned there is no march pentium-m. You'll probably need to bootstrap with pentium3 then once you have a working GCC 3.4 recompile with pentium-m.
_________________
> SELECT `signature` FROM `members` WHERE `user_name`='saintdev';
0 rows returned.
Back to top
View user's profile Send private message
yaneurabeya
Veteran
Veteran


Joined: 13 May 2004
Posts: 1754
Location: Seattle

PostPosted: Thu Dec 09, 2004 3:14 am    Post subject: Reply with quote

Uhm, remember to do the AMD64 specific flags in make.conf. I remember there being harsh notices about NOT doing athlon-xp, etc.

What architecture are you running unclefu?
Back to top
View user's profile Send private message
smokeslikeapoet
Tux's lil' helper
Tux's lil' helper


Joined: 03 Apr 2003
Posts: 96
Location: Cordova, TN USA

PostPosted: Thu Dec 09, 2004 3:42 am    Post subject: Reply with quote

Yeah mtune in my cflags killed my bootstrap. I replaced it with mcpu for the bootstrap, then did an emerge system -e to get to stage3.
_________________
-SmokesLikeaPoet

Folding@Home
Back to top
View user's profile Send private message
saintdev
n00b
n00b


Joined: 13 Jul 2004
Posts: 60
Location: CO, USA

PostPosted: Thu Dec 09, 2004 9:16 am    Post subject: Reply with quote

yaneurabeya wrote:
What architecture are you running unclefu?


From the looks of it he's running a Pentium-M....
_________________
> SELECT `signature` FROM `members` WHERE `user_name`='saintdev';
0 rows returned.
Back to top
View user's profile Send private message
To
Veteran
Veteran


Joined: 12 Apr 2003
Posts: 1145
Location: Coimbra, Portugal

PostPosted: Thu Dec 09, 2004 9:24 am    Post subject: Reply with quote

saintdev wrote:
yaneurabeya wrote:
What architecture are you running unclefu?


From the looks of it he's running a Pentium-M....


He said that on the first post...


_________________

------------------------------------------------
Linux Gandalf 3.2.35-grsec
Gentoo Base System version 2.2
------------------------------------------------
Back to top
View user's profile Send private message
valkyrite
Apprentice
Apprentice


Joined: 19 Sep 2002
Posts: 241

PostPosted: Thu Dec 09, 2004 10:24 am    Post subject: same problem here but solved Reply with quote

I had a similar problem "C compiler cannot create executables". After going through the posts on these forums, I decided to dig the problem out.

The prolem was with CFLAGS (in make.conf)
The flag -mtune=pentium4 was the cause of error. (It was working previsouly, but now it does not).

Any idea what might be wrong.

--
Tiwaris

If you want to experience pure linux, experience Gentoo Linux.
Back to top
View user's profile Send private message
saintdev
n00b
n00b


Joined: 13 Jul 2004
Posts: 60
Location: CO, USA

PostPosted: Thu Dec 09, 2004 10:32 am    Post subject: Reply with quote

tiwaris, version of GCC do you get with
Code:

gcc --version

_________________
> SELECT `signature` FROM `members` WHERE `user_name`='saintdev';
0 rows returned.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum