From: Jerry A! <jerry@thehutt.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] MOSIX and kernel 2.4.6
Date: Mon Jul 23 08:03:02 2001 [thread overview]
Message-ID: <20010723100257.A18556@gemini.thehutt.org> (raw)
In-Reply-To: <1DCB85BD45DED211B12D009027279E4F476804@murcury>; from SMitchell@phoenix-interactive.com on Mon, Jul 23, 2001 at 09:32:34AM -0400
On Mon, Jul 23, 2001 at 09:32:34AM -0400, Sean Mitchell wrote:
:
: Aha! Thanks Jerry... all the posts I saw on the subject (including one by
: Alan Cox) suggested starting with a clean tree which did work me (no deps at
: that point). I think your suggestion was in fact my problem. At any rate it
: was suggested that the makefiles in recent kernels are somehow broken. Not
: sure if this is actually the case, but....
The makefiles aren't broken, just the people that use them. 8) Most of
the people that I've seen have this issue aren't used to constantly
changing kernels. They're used to having 2.2.1x on their tree and never
needing to do a "make dep" after their initial configuration.
Alas, we're living in a world where we're getting a kernel rev per week,
so this stuff gonna happen more and more often.
--Jerry
name: Jerry Alexandratos || Open-Source software isn't a
phone: 703.599.6023 || matter of life or death...
email: jerry@thehutt.org || ...It's much more important
|| than that!
next prev parent reply other threads:[~2001-07-23 14:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-23 7:35 [gentoo-dev] MOSIX and kernel 2.4.6 Sean Mitchell
2001-07-23 8:03 ` Jerry A! [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-23 7:07 Sean Mitchell
2001-07-23 7:28 ` Jerry A!
2001-07-23 7:34 ` Hendrik Visage
2001-07-22 16:14 jb3insf
2001-07-22 18:01 ` Hendrik Visage
2001-07-22 23:01 ` Daniel Robbins
2001-07-23 1:02 ` Hendrik Visage
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=20010723100257.A18556@gemini.thehutt.org \
--to=jerry@thehutt.org \
--cc=gentoo-dev@cvs.gentoo.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