From: "Andres Järv" <andresjarv@gmail.com>
To: gentoo-dev@robin.gentoo.org
Subject: [gentoo-dev] gcc-4.0.0_alpha20050213 fails
Date: Sat, 26 Feb 2005 17:58:08 +0200 [thread overview]
Message-ID: <e17e599505022607582f819f63@mail.gmail.com> (raw)
In-Reply-To: <200502260502.12277.anthony@ectrolinux.com>
The failing can be witnessed here:
http://www.rrg.edu.ee/~andres77/gcc-error.png
Here's my emerge info just in case:
Portage 2.0.51-r15 (default-linux/x86/2004.3, gcc-4.0.0-alpha20050130,
glibc-2.3 .4.20050125-r0, 2.6.11-rc4-love1 i686)
=================================================================
System uname: 2.6.11-rc4-love1 i686 AMD Athlon(tm) processor
Gentoo Base System version 1.6.9
Python: dev-lang/python-2.3.5 [2.3.5 (#1, Feb 18 2005, 17:23:13)]
dev-lang/python: 2.3.5
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.4
sys-devel/binutils: 2.15.92.0.2-r3
sys-devel/libtool: 1.5.10-r4
virtual/os-headers: 2.6.8.1-r2
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-march=athlon-tbird -pipe -fomit-frame-pointer -O2 -fPIC -DPIC"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env
/usr/kde/3.3/share /config /usr/kde/3.3/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=athlon-tbird -pipe -fomit-frame-pointer -O2 -fPIC -DPIC"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig candy ccache distlocks nodoc noinfo
sandbox sfpe rms"
GENTOO_MIRRORS="ftp://ftp.estpak.ee/gentoo"
LANG="en_US.UTF-8"
LDFLAGS="-Wl,-O1 -Wl,--sort-common"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage /usr/local/bmg-main"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="x86 3dnow 3dnowex X alsa apm avi berkdb bitmap-fonts bzlib cdr
crypt cups d ivx4linux encode foomaticdb gdbm gif gnome gnutls gpm gtk
gtk2 hal imagemagick i mlib imlib2 jabber jpeg ldap libg++ libwww
mikmod mmx motif mozilla mp3 mpeg msn ncurses nls nptl nptlonly
nvidia oggvorbis opengl pam pdflib perl pic png pytho n quicktime
readline sdl slang ssl svga tcltk tcpd tiff truetype unicode xml2 xp
rint xv xvid zlib"
Unset: ASFLAGS, CBUILD, CTARGET, LC_ALL
It fails in the same spot with the latest ~x86 gcc too (3.4.3).
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-02-26 15:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-26 13:02 [gentoo-dev] Copyright assignment and ownership (again) Anthony Gorecki
2005-02-26 15:58 ` Andres Järv [this message]
2005-02-26 16:37 ` [gentoo-dev] gcc-4.0.0_alpha20050213 fails Stephen P. Becker
2005-02-26 17:50 ` Andres Järv
2005-02-26 17:58 ` Stephen P. Becker
2005-02-27 23:53 ` Luca Barbato
2005-02-27 12:35 ` [gentoo-dev] Copyright assignment and ownership (again) Jon Portnoy
2005-02-27 17:04 ` Joshua Brindle
2005-02-27 17:13 ` Ciaran McCreesh
2005-02-27 17:18 ` Simon Stelling
2005-02-27 17:21 ` Ciaran McCreesh
2005-02-27 23:05 ` Georgi Georgiev
2005-02-28 10:47 ` Simon Stelling
2005-02-28 11:02 ` Krzysiek Pawlik
2005-02-28 2:02 ` Anthony Gorecki
2005-02-28 5:11 ` Donnie Berkholz
2005-02-28 13:14 ` Chris Gianelloni
2005-02-28 12:44 ` Georgi Georgiev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e17e599505022607582f819f63@mail.gmail.com \
--to=andresjarv@gmail.com \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox