From: Sam Ravnborg <sam@ravnborg.org>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Sam Ravnborg <sam@ravnborg.org>,
"Adam J. Richter" <adam@yggdrasil.com>,
linux-kernel@vger.kernel.org
Subject: Re: Various kbuild problems in 2.5.22
Date: Tue, 18 Jun 2002 22:09:10 +0200 [thread overview]
Message-ID: <20020618220910.A3001@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0206181417230.5695-100000@chaos.physics.uiowa.edu>; from kai@tp1.ruhr-uni-bochum.de on Tue, Jun 18, 2002 at 02:28:02PM -0500
On Tue, Jun 18, 2002 at 02:28:02PM -0500, Kai Germaschewski wrote:
> Nitpick:
> [kai@chaos linux-2.5.make]$ make bzImage && ls bzImage
> [..]
> ls: bzImage: No such file or directory
>
> So you that bzImage isn't a real target (arch/i386/boot/bzImage would be).
Which actually annoy me a lot!
Maybe that just me, but I cannot see why I have to go down deep
in the architecture specific directory to locate the kernel.
But I have no brilliant idea how to solve it right away.
> make,
> make all -> compile vmlinux + modules as a general default,
> on i386 build bzImage + modules.
> (other archs can change the behavior as they wish)
I would like an easy way to do a full build, including supporting stuff
such as documentation. Think about doing regression on new kernels?
Today you have to specify a lot of different targets to accomplish
this - something that many people simply do not do.
Make it easy, and people will do it - and see more errors fixed earlier.
allyes, allmodules, allno were introduced for regression purpose.
And make all gives me the association that ALL is build, not only
the core kernel. Therefore I object against the make all semantic
that you suggest.
Better reserve that to a full build.
Furthermore I would advocate for a new target [yes one more!].
"make help"
make help shall generate a short list of available targets, something like:
<<<<<<<<<<<<
>make help
Configuration related targets:
oldconfig - bla bla
menuconfig - bla bla
config - bla bla
configallyes - ....
configallno - ....
Other generic targets:
vmlinux - The generic binary kernel
* modules - Build all modules
# pdfdocs - documentation
all - Build all targets marked with * and #
Architecture specific targets for current architecture (I386)
* bzImage - Default compressed kernel (arch/i386/boot/bzImage)
zImage - Another target (arch/i386/boot/zImage)
Executing "make" or "make kernel" builds targets marked with '*'
<<<<<<<<<<
The architecture specific stuff should obviously be located in the
corresponding architecture specific makefiles and triggered by archhelp.
Comments?
I would be happy to do a patch if people support this.
Sam
next prev parent reply other threads:[~2002-06-18 20:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 17:10 Adam J. Richter
2002-06-18 19:16 ` Sam Ravnborg
2002-06-18 19:28 ` Kai Germaschewski
2002-06-18 20:09 ` Sam Ravnborg [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-19 3:07 Adam J. Richter
2002-06-19 2:55 Adam J. Richter
2002-06-19 2:50 Adam J. Richter
2002-06-19 2:56 ` Kai Germaschewski
2002-06-18 15:00 Adam J. Richter
2002-06-18 16:14 ` Kai Germaschewski
2002-06-18 21:23 ` Gerd Knorr
2002-06-19 8:02 ` Martin Dalecki
2002-06-18 12:18 Adam J. Richter
2002-06-18 14:24 ` Kai Germaschewski
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=20020618220910.A3001@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=adam@yggdrasil.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--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®