From: Janos Holanyi <csani@lme.linux.hu>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Error while making 2.4.5 bzImage with CONFIG_MPENTIUMIII=y
Date: Thu, 28 Jun 2001 18:04:54 +0200 (CEST) [thread overview]
Message-ID: <993744294.3b3b55a63540c@mail.holanyi.hu> (raw)
In-Reply-To: <7570.993736352@ocs3.ocs-net>
In-Reply-To: <7570.993736352@ocs3.ocs-net>
Thank you and Alan Cox for replying and helping.
Would it be a bad idea to incorporate the relevant part(s) of that FAQ into
(under) the kernel Documentation tree?
Would it be possible to have 'make' catch the error(s) causing an exit during
kernel compilation and display a message pointing to that file?
Such a feature would have made me feel less st*pid now ;)
Regs,
Csan
Quoting Keith Owens <kaos@ocs.com.au>:
> >time make dep clean bzImage modules moduels_install 2>&1 | tee
> bzImage.log
>
> Please read the FAQ at http://www.tux.org/lkml/, in particular s8-8.
>
>
prev parent reply other threads:[~2001-06-28 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-28 13:39 csani
2001-06-28 13:52 ` Keith Owens
2001-06-28 16:04 ` Janos Holanyi [this message]
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=993744294.3b3b55a63540c@mail.holanyi.hu \
--to=csani@lme.linux.hu \
--cc=kaos@ocs.com.au \
--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®