From: <wsy@merl.com>
To: marco.roeland@xs4all.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: compile-time error in 2.6.0-test9
Date: Sun, 26 Oct 2003 18:19:13 -0500 [thread overview]
Message-ID: <200310262319.h9QNJDr13814@localhost.localdomain> (raw)
In-Reply-To: <20031026171650.GD23792@localhost> (message from Marco Roeland on Sun, 26 Oct 2003 18:16:50 +0100)
From: Marco Roeland <marco.roeland@xs4all.nl>
[...]
Just recently gcc 3.3.2 was released, so that or the latest from one's
distribution is 'current' and should work fine. Be warned though that
although they produce better code (and even that is sometimes disputed!)
and give better warnings, compilation is a lot slower.
Yeah, I saw that on the GCC homepage. Not sure if that's the way to go,
as it only went out like a week ago.
The Linux kernel has a lot of handcrafted optimised code, so no gcc
version is going to outsmart that easily anyway, and also very important
is the amount of testing a kernel gets. Better a somewhat less optimal
compiler but which has had a lot of testing, and so has it bugs known
and 'workarounded', than a potential 'flyer' with unknown new bugs.
But for userspace applications I'd recommend gcc 3.x wholeheartedly,
for g++ especially.
I'm still in straight C mode.
Now, to figure out why I've got a bunch of unresolved symbols in
when I do "make modules_install".
I am beginning to suspect that there's a particular bit of sequence that
I'm not doing quite right.
It's:
make
make bzImage
make install
make modules
make modules_install
and I've read the obvious things on the kernel.org web page and
googled, even manually created /lib/modules/2.6.0-test9, but failed
to achieve enlightenment.
Any suggestions? I've looked into upgrading to GCC 3.mumble, but that
looks to be a bit of an adventure unless I want to upgrade *everything*
as well.
-Bill Yerazunis
next prev parent reply other threads:[~2003-10-26 23:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-26 15:53 wsy
2003-10-26 16:24 ` Marco Roeland
2003-10-26 16:35 ` wsy
2003-10-26 17:16 ` Marco Roeland
2003-10-26 23:19 ` wsy [this message]
2003-10-26 23:51 ` David Rees
2003-10-27 0:09 ` wsy
2003-10-27 2:26 ` Guy
2003-10-27 11:21 ` Ookhoi
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=200310262319.h9QNJDr13814@localhost.localdomain \
--to=wsy@merl.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.roeland@xs4all.nl \
/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
all inboxes | Powered by JetHome®