From: "Måns Rullgård" <mru@kth.se>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Symlinks for building external modules
Date: Thu, 03 Jun 2004 19:55:10 +0200 [thread overview]
Message-ID: <yw1x4qps4jcx.fsf@kth.se> (raw)
In-Reply-To: <20040603173656.GA2301@mars.ravnborg.org> (Sam Ravnborg's message of "Thu, 3 Jun 2004 19:36:56 +0200")
Sam Ravnborg <sam@ravnborg.org> writes:
> On Thu, Jun 03, 2004 at 07:09:42PM +0200, Måns Rullgård wrote:
>> Andreas Gruenbacher <agruen@suse.de> writes:
>>
>> > Hi Sam,
>> >
>> > modules not in the kernel source tree need to locate both the source
>> > tree and the object tree (O=). Currently, the /lib/modules/$(uname
>> > -r)/build symlink is the only reference we have; it historically
>> > points to the source tree from 2.4 times. The following patch
>> > changes this as follows (this is what we have in the current SUSE
>> > tree now):
>> >
>> > /lib/modules/$(uname -r)/source ==> source tree
>> > /lib/modules/$(uname -r)/build ==> object tree
>>
>> This will break the building of all external modules until they are
>> updated, and break updated modules building against older kernels
>> unless they check the kernel version in the makefiles.. I suggest
>> leaving the 'build' link as is, and using a difference name for the
>> build directory, perhaps 'object'. This might look confusing, so we
>> could have a 'source' link as well and remove the 'build' link when
>> most external modules have been updated.
>
> The existing external modules are anyway broken when using separate
> directories for source and output directories.
They work fine if you pass O=/some/path on the make command line.
> So noting lost here. In the case where the kernel is build in the
> traditional way the build and source tree will point to the same
> place.
True.
> So I do not see this patch breaking existing setups, but I see
> external modules not being prepared for separate build and source
> directories.
>
> Patch looks good to me, and I will forward to Andrew soon.
I'll just have to go fix my kernel modules then.
--
Måns Rullgård
mru@kth.se
next prev parent reply other threads:[~2004-06-03 17:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 16:58 Andreas Gruenbacher
2004-06-03 17:09 ` Måns Rullgård
2004-06-03 17:36 ` Sam Ravnborg
2004-06-03 17:55 ` Måns Rullgård [this message]
2004-06-04 17:15 ` Jari Ruusu
2004-06-04 19:23 ` Sam Ravnborg
2004-06-04 19:45 ` Måns Rullgård
2004-06-05 13:45 ` Andreas Gruenbacher
2004-06-05 13:20 ` Jari Ruusu
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=yw1x4qps4jcx.fsf@kth.se \
--to=mru@kth.se \
--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®