From: "Chris Nanakos" <nanakos@wired-net.gr>
To: Francis Lau <fkwlau@utcc.utoronto.ca>,
linux-c-programming@vger.kernel.org
Subject: Re: quotactl
Date: Wed, 2 Jul 2003 20:37:17 +0300 [thread overview]
Message-ID: <002e01c340c0$95fc8a40$db1e05d5@carlos> (raw)
In-Reply-To: Pine.LNX.4.44.0307021245010.20193-100000@gpu.utcc
make a clean compilation of the kernel from the beggining.(use make clean &&
make mrproper).Be sure that no object files exist when you start building
your new kernel.Try this....and e-mail again:)
Best regards,
Chris.
next prev parent reply other threads:[~2003-07-02 17:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S265125AbTGBQaA/20030702163000Z+15659@vger.kernel.org>
2003-07-02 16:48 ` quotactl Francis Lau
2003-07-02 17:37 ` Chris Nanakos [this message]
2003-07-02 18:04 ` quotactl Francis Lau
2003-07-02 18:20 ` quotactl Darío Mariani
2003-07-02 18:58 ` quotactl Francis Lau
2003-07-02 23:45 ` mid file deletion John T. Williams
2003-07-02 22:15 ` Glynn Clements
2003-07-02 21:45 ` quotactl Glynn Clements
2003-07-03 16:24 ` quotactl Francis Lau
2003-07-03 18:48 ` quotactl Glynn Clements
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='002e01c340c0$95fc8a40$db1e05d5@carlos' \
--to=nanakos@wired-net.gr \
--cc=fkwlau@utcc.utoronto.ca \
--cc=linux-c-programming@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;
as well as URLs for NNTP newsgroup(s).