From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31242 invoked by uid 1002); 27 Dec 2002 19:29:06 -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 8274 invoked from network); 27 Dec 2002 19:29:06 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Evan Powers To: Johannes Findeisen , gentoo-dev@gentoo.org Date: Fri, 27 Dec 2002 14:27:26 -0500 User-Agent: KMail/1.4.3 References: <200212241459.47102.mailman@hanez.org> In-Reply-To: <200212241459.47102.mailman@hanez.org> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200212271427.26269.powers.161@osu.edu> X-Apparently-From: EPTheCoder@aol.com Subject: Re: [gentoo-dev] very mystic segmentation fault... X-Archives-Salt: 1471571f-86a5-42b9-a328-e1e3c0821211 X-Archives-Hash: c411c1c7a16cbc1a99585a90a9410c8f On Tuesday 24 December 2002 08:59 am, Johannes Findeisen wrote: > short again: i can compile in my gcc 2.95.3 system and in the chrooted > gcc 3.2.1 but only when i'm chrooting from my gcc 2.95.3 system. i > defenitly could not compile when the gcc 3.2.* system is runing. If you can compile when chrooting from 2.95.3 to the 3.2.1 system, but no= t=20 when booting directly into the 3.2.1 system, my guess is that you have a=20 kernel problem. Theoretically, the only effective difference between the chroot environme= nt=20 and the directly booted environment is whether a 2.95.3 compiled or a 3.2= =2E1=20 compiled kernel is running. Consider adding a new boot menu option which boots the gcc 3.2.1 system u= sing=20 the kernel from the 2.95.3 system. If you don't have problems with this, = your=20 3.2.1 system has a bad kernel. WHY that kernel would be bad is a pretty open question. It probably has=20 nothing to do with it being compiled with the newer gcc; perhaps the=20 configuration is somehow wrong? Or perhaps Gentoo has started using newer= =20 kernel versions with slightly different binary interfaces, and you need t= o=20 compile libc against the new kernel so that it uses the new binary interf= ace. Good luck, in any case. Evan Powers -- gentoo-dev@gentoo.org mailing list