All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Alessandro Amici <alexamici@tiscali.it>
Cc: linux-kernel@vger.kernel.org, James.Bottomley@HansenPartnership.com
Subject: Re: 2.5.37+ i386 arch split broke external module builds
Date: Wed, 02 Oct 2002 22:13:19 +0100	[thread overview]
Message-ID: <20770.1033593199@passion.cambridge.redhat.com> (raw)
In-Reply-To: <20021002210609.575031EA74@alan.localdomain>


alexamici@tiscali.it said:
>  average users may have either a kernel-headers package that matches
> their  running kernel and/or a souce package without the configuration
> stuff. in  both cases 'the hacker way' doesn't work :)

Often nowadays they'll not have 'kernel-headers' but instead 
'glibc-kernheaders' which is littered with '#ifdef __KERNEL__ #error' to 
prevent people from doing that.

If you don't have the corresponding source and configuration, you cannot
build a module with any reasonable chance of success -- at least for my
definition of 'reasonable' in the context of shipping drivers to the Great
Unwashed.

> OTOH, for small device drivers you don't need the full blown kernel
> CFLAGS,  you know what you need anyway. 

Build for Alpha and tell me that again :)

--
dwmw2



  reply	other threads:[~2002-10-02 21:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-02 10:39 2.5.37+ i386 arch split broke external module builds Alessandro Amici
2002-10-02 11:28 ` David Woodhouse
2002-10-02 21:06   ` Alessandro Amici
2002-10-02 21:13     ` David Woodhouse [this message]
2002-10-02 22:09 ` James Bottomley
2002-10-02 23:49   ` Alessandro Amici

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=20770.1033593199@passion.cambridge.redhat.com \
    --to=dwmw2@infradead.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=alexamici@tiscali.it \
    --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 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.