From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2986 invoked by uid 1002); 17 Dec 2002 10:13:39 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 23783 invoked from network); 17 Dec 2002 10:13:38 -0000 Date: Tue, 17 Dec 2002 11:10:43 +0100 (CET) Message-Id: <20021217.111043.48529161.csabi@rubin.hu> To: azarah@gentoo.org Cc: gentoo-core@gentoo.org, gentoo-dev@gentoo.org, gentoo-user@gentoo.org From: Csaba Paradi In-Reply-To: <1040077275.15406.31.camel@nosferatu.lan> References: <1040077275.15406.31.camel@nosferatu.lan> X-Mailer: Mew version 3.1 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [gentoo-dev] Re: Possible isses with gcc, *please* read! X-Archives-Salt: 3dbfff8b-60b7-4a0f-a3f0-7082def29a6e X-Archives-Hash: 1f0abae73917f6972d674fb83bd219b0 Hi, > From: Martin Schlemmer > Subject: Possible isses with gcc, *please* read! > Date: 17 Dec 2002 00:21:15 +0200 > Sorry for the inconvenience, but if you experience problems > where builds fail due to /lib/cpp or /usr/bin/cc not being > executable: It's our fault, we selected the ACCEPT_KEYWORDS="~x86" in make.conf ... :-) > > Please do the following: > > # emerge rsync > # rm -f /lib/cpp /usr/bin/cc > # cp /usr/portage/sys-devel/gcc/files/cpp /lib > # cp /usr/portage/sys-devel/gcc/files/cc /usr/bin > # chmod +x /lib/cpp /usr/bin/cc > It didn't help. If say: export PATH=$PATH:`/usr/sbin/gcc-config --get-bin-path` then gcc works as a normal user too. It's enough for me till the gcc ebuild get fixed ! Regards, Csaba Paradi ps. Dear Gentoo guys, thanks for this great distribution !! -- gentoo-dev@gentoo.org mailing list