Linux filesystem development
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Jan Hudec <bulb@ucw.cz>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: buffer cache
Date: Sun, 14 Sep 2003 11:37:22 +0100	[thread overview]
Message-ID: <1063535842.11431.44.camel@imladris.demon.co.uk> (raw)
In-Reply-To: <20030914100351.GG31719@vagabond>

Please don't drop me from the recipients when replying; it's very rude.

On Sun, 2003-09-14 at 12:03 +0200, Jan Hudec wrote:
> > Probably as a result of hacking up his own broken makefiles instead of 
> > 	make -C $KERNELDIR SUBDIRS=`pwd` modules
> 
> Well, I wrote a module to compile off-tree. The correct command to link
> a module is:
> ld -r -o <modname>.o <objects...>

No, that's not always correct. It's completely wrong for 2.6, of course
-- and even for 2.4, if building modules for a 64-bit kernel, you may
find your userspace is 32-bit by default and you need something like
-melf64_sparc on the linker command line. The kernel makefiles get this
right. Use them.

The kernel is also free to screw with its own internal ABI all it likes
-- with cflags affecting global register usage, etc. You must do as it
does in the kernel you happen to be building -- which basically means
you must use the kernel build system.

The correct way to build modules out of the kernel tree is to use the
kernel makefiles and override SUBDIRS to point at your own directory;
it's been that way since 2.0 if not earlier.

-- 
dwmw2



  reply	other threads:[~2003-09-14 10:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-13  8:51 buffer cache vadiraj c s
2003-09-13 10:27 ` Jan Hudec
2003-09-13 13:14   ` Matthew Wilcox
2003-09-13 17:25   ` Bryan Henderson
2003-09-13 17:28     ` Jan Hudec
2003-09-14  9:32       ` David Woodhouse
2003-09-14 10:03         ` Jan Hudec
2003-09-14 10:37           ` David Woodhouse [this message]
2003-09-14 11:19             ` Jan Hudec
2003-09-15 16:18             ` Bryan Henderson
2003-09-15 16:35               ` Greg KH
2003-09-15 22:41                 ` Bryan Henderson
2003-09-16  5:13                   ` David Woodhouse
2003-09-16 10:18                     ` Jamie Lokier
2003-09-16 12:16                       ` David Woodhouse

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=1063535842.11431.44.camel@imladris.demon.co.uk \
    --to=dwmw2@infradead.org \
    --cc=bulb@ucw.cz \
    --cc=linux-fsdevel@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