public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Evan Powers <powers.161@osu.edu>
To: Johannes Findeisen <mailman@hanez.org>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] very mystic segmentation fault...
Date: Fri, 27 Dec 2002 14:27:26 -0500	[thread overview]
Message-ID: <200212271427.26269.powers.161@osu.edu> (raw)
In-Reply-To: <200212241459.47102.mailman@hanez.org>

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 not 
when booting directly into the 3.2.1 system, my guess is that you have a 
kernel problem.

Theoretically, the only effective difference between the chroot environment 
and the directly booted environment is whether a 2.95.3 compiled or a 3.2.1 
compiled kernel is running.

Consider adding a new boot menu option which boots the gcc 3.2.1 system using 
the kernel from the 2.95.3 system. If you don't have problems with this, your 
3.2.1 system has a bad kernel.

WHY that kernel would be bad is a pretty open question. It probably has 
nothing to do with it being compiled with the newer gcc; perhaps the 
configuration is somehow wrong? Or perhaps Gentoo has started using newer 
kernel versions with slightly different binary interfaces, and you need to 
compile libc against the new kernel so that it uses the new binary interface.

Good luck, in any case.

Evan Powers


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2002-12-27 19:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-24 13:59 [gentoo-dev] very mystic segmentation fault Johannes Findeisen
2002-12-27 19:27 ` Evan Powers [this message]
2003-01-03 12:05   ` Johannes Findeisen

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=200212271427.26269.powers.161@osu.edu \
    --to=powers.161@osu.edu \
    --cc=gentoo-dev@gentoo.org \
    --cc=mailman@hanez.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