From: Charles Lepple <clepple@foo.tho.org>
To: linux@cthulhu.engr.sgi.com
Subject: kernel compilation problem
Date: Thu, 15 Apr 1999 04:20:04 +0000 [thread overview]
Message-ID: <371568F3.FA1E916A@foo.tho.org> (raw)
While configuring the kernel (2.2.5 from ftp.kernel.org), I get the
following message:
Sound card support (CONFIG_SOUND) [N/y/m/?]
>scripts/Configure: drivers/sgi/char/Config.in: No such file or
directory
*
* Kernel hacking
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?
Thanks in advance,
--
Charles Lepple
System Administrator, Virginia Tech EE Workstation Labs
clepple@ee.vt.edu || http://www.foo.tho.org/charles/
next reply other threads:[~1999-04-15 4:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-15 4:20 Charles Lepple [this message]
1999-04-15 4:37 ` kernel compilation problem Ralf Baechle
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
2003-12-23 10:46 kernel " joy
2003-12-23 13:46 Pacheco Jason NPRI
[not found] <3BEEE23D31CAD2118D920008C75D8946059FF59E@NPRI54EXC21.NPT.N UWC.NAVY.MIL>
2003-12-23 16:51 ` Ray Olszewski
2003-12-24 4:45 ` joy
2003-12-24 6:46 ` Beolach
2003-12-24 13:22 Pacheco Jason NPRI
2007-02-22 13:01 Kernel " Zgembo Adislic
2007-02-22 13:10 ` Woodruff, Richard
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=371568F3.FA1E916A@foo.tho.org \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.