From: Sam Ravnborg <sam@ravnborg.org>
To: Pavel Roskin <proski@gnu.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Removing .tmp_versions considered harmful
Date: Fri, 21 Apr 2006 09:32:16 +0200 [thread overview]
Message-ID: <20060421073216.GA17492@mars.ravnborg.org> (raw)
In-Reply-To: <1145593342.2904.30.camel@dv>
On Fri, Apr 21, 2006 at 12:22:22AM -0400, Pavel Roskin wrote:
> Hello!
>
> A patch applied shortly after Linux 2.6.16
> (fb3cbd2e575f9ac0700bfa1e7cb9f4119fbd0abd in git) causes
> the .tmp_versions directory to be removed every time make is run to
> build external modules.
>
>
> 2) The projects where modules are build in more than one directory (such
> as MadWifi) are now compiled with spurious warnings about unresolved
> symbols. This happens because every module is compiled individually,
> and the *.mod files for one module are removed before the other is
> compiled.
Then fix madwifi so it builds modules as documented in
Documentation/kbuild/modules.txt
See: --- 5.3 External modules using several directories
As with many other external modules madwifi contains a lot of ugly
makefile hackery - and if done as documentated it gets so much simpler.
I'm aware that 2-4 support complicates things a little but if people
made it be slimm and nice for 2.6 and _then_ added 2.4 supporrrrrrrrrrit
woulllllld be much simpler.
It seems that people keep all the hackery for 2.4 and does a bad job
adapting to 2.6.
All the bad FAQ's out there does a good job confusing people.
Almost no-one mention SUBDIRS= as is preferred with 2.4 but seldom used
:-(
Sam
next prev parent reply other threads:[~2006-04-21 7:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 4:22 Pavel Roskin
2006-04-21 7:32 ` Sam Ravnborg [this message]
2006-04-21 11:55 ` Pavel Roskin
2006-04-24 19:55 ` Pavel Roskin
2006-04-24 19:58 ` Arjan van de Ven
2006-04-24 20:19 ` Pavel Roskin
2006-04-30 21:47 ` Sam Ravnborg
2006-05-01 0:59 ` Pavel Roskin
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=20060421073216.GA17492@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=proski@gnu.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
Powered by JetHome