archive mirror
 help / color / mirror / Atom feed
From: Andrew Walrond <>
To: Mariusz Mazur <>
Subject: Re: [ANNOUNCE] linux-libc-headers
Date: Thu, 13 Jan 2005 08:13:42 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wednesday 12 January 2005 11:11, Mariusz Mazur wrote:
> Looks like you've linked your kernel's config.h to llh and that causes the
> problem. You shouldn't do that unless you have a specific reason to,
> otherwise you might end up with problems I'm unable to test for (I can't
> check every possible combination of kernel CONFIG_'s).

I know you are deliberately vague in the faq ;) But what about something like 
X11? It needs the real config.h in order to build the kernel DRM drivers. 
Should it be built against
 1) llh + blank config.h
 2) llh + real config.h
 3) kernel source

I guess this ambiguity would go away once the real kernel headers have been 
sanitized for userspace (ie we could always use the real config.h without 
fear of breakage) But as you have already stated, the issues are complex, and 
consensus is lacking. The longer the status quo continues, the more apps are 
going to break when we do get round to it.

And I think, in this instance, the "shut up and hack" response is 
inappropriate; Either these changes come from a senior linux hacker, or they 
will be ignored/derided (again).

Andrew Walrond

  parent reply	other threads:[~2005-01-13  8:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-08 15:13 [ANNOUNCE] linux-libc-headers 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 [this message]
2005-01-13  9:42       ` Mariusz Mazur
2005-01-13 11:00         ` Andrew Walrond
2005-01-13 11:46           ` Rahul Karnik
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).