From: Rahul Karnik <deathdruid@gmail.com>
To: Andrew Walrond <andrew@walrond.org>
Cc: Mariusz Mazur <mmazur@kernel.pl>, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] linux-libc-headers 2.6.10.0
Date: Thu, 13 Jan 2005 06:46:32 -0500 [thread overview]
Message-ID: <5b64f7f050113034640e28eb9@mail.gmail.com> (raw)
In-Reply-To: <200501131100.19500.andrew@walrond.org>
On Thu, 13 Jan 2005 11:00:19 +0000, Andrew Walrond <andrew@walrond.org> wrote:
> On Thursday 13 January 2005 09:42, Mariusz Mazur wrote:
> >
> > I'm a distribution vendor. If x11 really required having current kernel
> > config at compile time to function properly, I'd start sending threats to
> > its authors.
We are not talking about an application, but rather out of tree kernel
modules (or rather, different versions of modules already in the
tree).
> Well there is certainly stuff like
>
> ifdef ARCHX86
> ifndef CONFIG_X86_CMPXCHG
> $(error CONFIG_X86_CMPXCHG needs to be enabled in the kernel)
> endif
> endif
>
> and
>
> ifdef CONFIG_AGP
> ifneq (,$(findstring mga,$(DRM_MODULES)))
> CONFIG_DRM_MGA := m
> endif
> endif
Let's be clear here: these are not regular X11 files, but those meant
to compile kernel modules. Are you surprised that config.h is needed?
-Rahul
next prev parent reply other threads:[~2005-01-13 11:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-08 15:13 [ANNOUNCE] linux-libc-headers 2.6.10.0 Mariusz Mazur
2005-01-10 15:16 ` Randy.Dunlap
2005-01-12 10:49 ` Andrew Walrond
2005-01-12 11:11 ` Mariusz Mazur
2005-01-12 12:04 ` Andrew Walrond
2005-01-13 8:13 ` Andrew Walrond
2005-01-13 9:42 ` Mariusz Mazur
2005-01-13 11:00 ` Andrew Walrond
2005-01-13 11:46 ` Rahul Karnik [this message]
2005-01-13 11:51 ` Jakub Jelinek
2005-01-13 16:14 ` Rahul Karnik
2005-01-13 16:29 ` Mariusz Mazur
2005-01-13 12:18 ` Andrew Walrond
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=5b64f7f050113034640e28eb9@mail.gmail.com \
--to=deathdruid@gmail.com \
--cc=andrew@walrond.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmazur@kernel.pl \
/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.