public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stef van der Made <svdmade@planet.nl>
To: Sebastian Piecha <spi@gmxpro.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [INFO] gcc versions used to compile a kernel
Date: Mon, 13 Oct 2003 21:50:22 +0200	[thread overview]
Message-ID: <3F8B01FE.3050505@planet.nl> (raw)
In-Reply-To: <3F8ACFA0.10239.10815846@localhost>


Dear Sebastian,

This is very interesting as I've been compiling kernels with GCC 3.2.0 
and higher since the first beta I compiled. I've never had the issues 
that you are describing with kernel 2.5.70 and higher and 2.6.0 test 1> 
6. This most likly is a machine related problem. Which Linux distibution 
are you using and how uptodate is the rest of the machine.

Best regards,

Stef

Sebastian Piecha wrote:

>The last days I had a lot of trouble getting different kernel 
>versions to run. Enclosed is a short report of the experience I made.
>
>First I tried to compile all kernels with gcc 3.3.1.
>
>2.4.20 I even couldn't compile.
>2.4.22-ac4 compiled well but oopsed immediately after booting.
>2.6.0-test4 and test5 compiled well but didn't boot and froze with a 
>blank screen.
>2.6.0-test6 compiled well but froze after starting /sbin/init.
>
>Then I used gcc 2.95.3 for compiling 2.4.20, 2.4.22-ac4 and 2.6.0-
>test7 and all kernels booted smoothly.
>
>It's seems that at least in my configuration gcc 3.3.1 is doing a bad 
>job.
>
>Mit freundlichen Gruessen/Best regards,
>Sebastian Piecha
>
>EMail: spi@gmxpro.de
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>
>  
>



  parent reply	other threads:[~2003-10-13 19:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-13 14:15 [INFO] gcc versions used to compile a kernel Sebastian Piecha
2003-10-13 14:41 ` raid1.c and gcc problem/oops (was: " Thomas Steudten
2003-10-13 15:12   ` Falk Hueffner
2003-10-13 19:50 ` Stef van der Made [this message]
2003-10-13 22:20   ` Sebastian Piecha
  -- strict thread matches above, loose matches on Subject: below --
2003-10-13 22:22 Andrew_Purtell
2003-10-13 22:43 ` Sebastian Piecha

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=3F8B01FE.3050505@planet.nl \
    --to=svdmade@planet.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spi@gmxpro.de \
    /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