From: David Relson <relson@osagesoftware.com>
To: "Calin A. Culianu" <calin@ajvar.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Cannot compile mandrake 8.2 Kernel
Date: Wed, 10 Apr 2002 16:06:08 -0400 [thread overview]
Message-ID: <4.3.2.7.2.20020410160354.00d77a00@mail.osagesoftware.com> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0204101505220.5649-100000@rtlab.med.cornel l.edu>
At 03:10 PM 4/10/02, Calin A. Culianu wrote:
>The stupid mandrake 8.2 kernel (2.4.18-mdk6) won't compile. I know,
>mandrake is kind of a newbie distro, but I needed to mess with that kernel
>for some reason (don't ask).
>
>Anyway it gets errors like the following then you do make modules. I
>notices someone else also had the exact same problem.. also below is
>preprocessor output from that compile... I think the problem is due to
>some of the exported kernel symbols containing parens...:
Calin,
I think the proper place for this query is the Mandrake Expert mailing
list, which can be subscribed to at expert@linux-mandrake.com.
Mandrake has been around for several years and I've used their distribution
(and often their kernels) since Mandrake 7.0. I think it's incorrect to
blame their "newness".
What gcc are you running? gcc-3.0.4 has worked fine for me in building
2.4.18 kernels on 8.2.
David
next parent reply other threads:[~2002-04-10 20:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33L2.0204101505220.5649-100000@rtlab.med.cornel l.edu>
2002-04-10 20:06 ` David Relson [this message]
2002-04-10 20:22 ` Calin A. Culianu
2002-04-10 19:10 Calin A. Culianu
2002-04-10 21:52 ` Steven Cole
2002-04-10 22:17 ` Calin A. Culianu
2002-04-15 13:52 ` Jesse Pollard
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=4.3.2.7.2.20020410160354.00d77a00@mail.osagesoftware.com \
--to=relson@osagesoftware.com \
--cc=calin@ajvar.org \
--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
all inboxes | Powered by JetHome®