From: Ralf Baechle <ralfb@cthulhu.engr.sgi.com>
To: Charles Lepple <clepple@foo.tho.org>, linux@cthulhu.engr.sgi.com
Subject: Re: kernel compilation problem
Date: Wed, 14 Apr 1999 21:37:58 -0700 [thread overview]
Message-ID: <19990414213758.D1174@uni-koblenz.de> (raw)
In-Reply-To: <371568F3.FA1E916A@foo.tho.org>; from Charles Lepple on Thu, Apr 15, 1999 at 04:20:04AM +0000
On Thu, Apr 15, 1999 at 04:20:04AM +0000, Charles Lepple wrote:
> Then, while executing 'make dep', I see a bunch of messages about
> 'SOCK_DGRAM' being redefined.
>
> And when I try 'make zImage', it bombs compiling init/main.c -- there's
> a "parse error" in linux/sched.h, and lots of stuff breaks. I have the
> compile log if anyone can decipher it, but is this just a simple case of
> me overlooking a patch? Or where can I find a preconfigured kernel
> source tree?
Get the kernel from {ftp,www}.linux.sgi.com.
Ralf
next prev parent reply other threads:[~1999-04-15 4:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-15 4:20 kernel compilation problem Charles Lepple
1999-04-15 4:37 ` Ralf Baechle [this message]
1999-04-15 4:48 ` Matthias Kleinschmidt
-- strict thread matches above, loose matches on Subject: below --
2001-08-25 12:18 Kernel " Ben Hague
2001-08-25 10:37 ` Ralf Baechle
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=19990414213758.D1174@uni-koblenz.de \
--to=ralfb@cthulhu.engr.sgi.com \
--cc=clepple@foo.tho.org \
--cc=linux@cthulhu.engr.sgi.com \
/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