From: "Witek Krecicki" <adasi@kernel.pl>
To: "Jose Luis Domingo Lopez" <linux-kernel@24x7linux.org>,
"Linux-Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [Build Errors] kernel version 2.5.27
Date: Tue, 23 Jul 2002 14:37:57 +0200 [thread overview]
Message-ID: <018c01c23245$c8434820$0201a8c0@witek> (raw)
In-Reply-To: <20020723091438.GB3455@localhost>
----- Original Message -----
From: "Jose Luis Domingo Lopez" <linux-kernel@24x7linux.org>
> Hi:
>
> Don't know if this can be helpful at all, but having a "powerful" (AMD XP
> 1700+, 256 MB DDR and 7200 rpm IDE disk) PC doing nothing most of the
> time, I thought it could be doing something useful for the ongoing
> development of the linux kernel. So I decided to do a full kernel compile
> (that is, a compile of the linux kernel with _all_ options enabled to be
> compiled built-in, just a few as modules, those that can't be built
> otherwise). And report errors that can happen, in the hope to unveil
> them and make maintainers aware of them, should they still aren't.
>
> .config file was created the "easy" way: going to all options shown in a
> "make menuconfig" session, enabling everything to be built-in (when
> possible), and making a second pass to check if some options were
> activated by enabling some others. The file is 2206 lines long, but is
> NOT attached, to help save bandwidth.
IMHO building everything as a module is much better in this case. Some
things are working built-in but not working as modules (eg.
probably-still-not-fixed 2.5 IDE with 2 symbols not exported properly). It
would be better to build everything as a module and then check it with
depmod so any unresolved deps could be shown
WK
next prev parent reply other threads:[~2002-07-23 12:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 9:14 Jose Luis Domingo Lopez
2002-07-23 12:37 ` Witek Krecicki [this message]
2002-07-23 12:58 ` Adrian Bunk
2002-07-24 7:03 ` Keith Owens
2002-07-24 20:03 ` Greg KH
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='018c01c23245$c8434820$0201a8c0@witek' \
--to=adasi@kernel.pl \
--cc=linux-kernel@24x7linux.org \
--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 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®