From: Karim Yaghmour <karim@opersys.com>
To: Dan Kegel <dank@kegel.com>
Cc: John Bradford <john@grabjohn.com>, linux-kernel@vger.kernel.org
Subject: Re: Recommended compiler version
Date: Sat, 29 May 2004 20:38:42 -0400 [thread overview]
Message-ID: <40B92D12.5040107@opersys.com> (raw)
In-Reply-To: <40B922D5.5090609@opersys.com>
Karim Yaghmour wrote:
...
> kernels as well, to see if they too would work. I noticed that
> some that actually failed as above (causing a fault very early
> at boot time), now didn't fail with 3.3.2, but printed nothing
> to the terminal and the system would eventually reboot -- as if
> console=ttyS0,9600 had no effect and the kernel panicked as
> expected because of the missing rootfs.
This just above is actually due pilot error. I had been trying so
many different kernels that I had forgotten to check whether
console on serial was enabled ... No wonder nothing was displayed.
To recap, I've also got the 2.4.25-ben1 and 2.6.6 working with
gcc 3.3.2. 2.4.25-ben1 still has the same problem as described
earlier with gcc 3.4.0, but 2.6.6 works fine with gcc 3.4.0.
I'm probably going to stick to 3.3.2, though, as I have no
intention of chasing gcc 3.4.0's breaking of some user-space
stuff.
Karim
--
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 1-866-677-4546
next prev parent reply other threads:[~2004-05-30 0:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-29 14:42 Recommended compiler version Dan Kegel
2004-05-29 23:55 ` Karim Yaghmour
2004-05-29 23:20 ` Dan Kegel
2004-05-30 0:40 ` Karim Yaghmour
2004-05-30 0:38 ` Karim Yaghmour [this message]
2004-05-30 10:37 ` John Bradford
[not found] <218aB-15c-17@gated-at.bofh.it>
2004-05-29 10:51 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2004-05-29 9:16 Francois Romieu
2004-05-29 9:52 ` Francois Romieu
2004-05-29 13:30 ` John Bradford
2004-05-29 14:12 ` Francois Romieu
2004-05-29 14:31 ` Adrian Bunk
2004-05-29 14:57 ` John Bradford
2004-05-30 1:18 ` George Georgalis
2004-05-29 14:53 ` John Bradford
2004-05-29 16:58 ` Francois Romieu
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=40B92D12.5040107@opersys.com \
--to=karim@opersys.com \
--cc=dank@kegel.com \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.