public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Johannes Findeisen <mailman@hanez.org>
To: Evan Powers <powers.161@osu.edu>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] very mystic segmentation fault...
Date: Fri, 3 Jan 2003 13:05:32 +0100	[thread overview]
Message-ID: <200301031305.38205.mailman@hanez.org> (raw)
In-Reply-To: <200212271427.26269.powers.161@osu.edu>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

hello evan,

thanks for your help. i reply to this message, to say that everything works 
fine now...

<snip>
> 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.
</snip>

i have started my gcc 2.95.3 system and have chrooted to my gcc 3.2.1. i have 
deleteted my old kernel wchich i used to start the gcc 3.2.1 system and have 
compiled a new one... i have copied the kernel config from my old system to 
the new and have compiled the new kernel. i have copied into my /boot 
directory and started the gcc 3.2.1 system again. and hep: everything works 
again.

i'm so happy, so i must say thank you evan. this was the best thing for me in 
the beginning of 2003. my server is lucky now an emerges what i want...

kind regards
johannes findeisen ... ;-)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+FXyR1e37d/WNRDURAmQpAJ9fUEq0y2krbasMuqJ7M5uwJFsfQwCg3ZK9
hRyXTHvWBJcJPUmUehN+TaE=
=Ma6d
-----END PGP SIGNATURE-----


--
gentoo-dev@gentoo.org mailing list


      reply	other threads:[~2003-01-03 12:07 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
2003-01-03 12:05   ` Johannes Findeisen [this message]

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