From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: elenstev@mesatop.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
alan@lxorguk.ukuu.org.uk
Subject: Re: Linux 2.4.0-ac10 build errors
Date: Fri, 19 Jan 2001 21:27:44 -0500 [thread overview]
Message-ID: <3A68F7A0.9D31E5B5@mandrakesoft.com> (raw)
In-Reply-To: <01011919204300.04079@localhost.localdomain>
Steven Cole wrote:
>
> I got the following errors building 2.4.0-ac10:
> The first three digits are the line number in the build log.
Always run 'make mrproper' before building.
Alan's patch accidentally includes some files that are generated by the
build system.
Jeff
--
Jeff Garzik | "You see, in this world there's two kinds of
Building 1024 | people, my friend: Those with loaded guns
MandrakeSoft | and those who dig. You dig." --Blondie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-20 2:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-20 2:20 Linux 2.4.0-ac10 build errors Steven Cole
2001-01-20 2:27 ` Jeff Garzik [this message]
2001-01-20 2:33 ` Steven Cole
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=3A68F7A0.9D31E5B5@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=elenstev@mesatop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox