From: Michael Elizabeth Chastain <mec@shout.net>
To: jjs@pobox.com, kaos@ocs.com.au
Cc: alan@lxorguk.ukuu.org.uk, dri-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [patch] 2.4.0-prerelease drm and modversions
Date: Mon, 1 Jan 2001 01:35:37 -0600 [thread overview]
Message-ID: <200101010735.BAA12841@duracef.shout.net> (raw)
Keith Owens writes:
kaos> drivers/char/drm/Makefile is breaking the Makefile rules. It builds
kaos> drmlib.a and expects to link that library into both the kernel and into
kaos> modules.
Ah, shit.
kaos> The kernel makefile system assumes that everything is either kernel or
kaos> module, not both. The components in drmlib.a get compiled for kernel
kaos> only, when used in a module they are missing the symbol versions.
I agree with Keith.
The kernel version is going to get compiled, and then the module version is
going to get compiled with different compilation flags: -DMODULE. The two
versions are always going to fight.
kaos> +$(patsubst %.o,%.c,$(lib-objs-mod)):
kaos> + @ln -sf $(subst -mod,,$@) $@
kaos> +
This looks good to me. It's missing a dependency though. If foo-mod.c
exists, and someone edits or patches foo.c, then foo-mod.c needs to be
re-created.
Keith, what do you think of this:
source-objs-mod := $(patsubst %-mod.o,%-mod.c,$(lib-objs-mod))
$(source-objs-mod): $(patsubst %-mod.c,%.c,$(source-objs-mod))
ln -sf $(patsubst %-mod.c,%.c,$@) $@
It suffers from the thundering herd problem (each *-mod.c depend on
all *.c files) but I think it's correct.
Michael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-01 8:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-01 7:35 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-01 7:38 [patch] 2.4.0-prerelease drm and modversions Michael Elizabeth Chastain
2000-12-31 22:38 2.4.0-prerelease J Sloan
2001-01-01 4:59 ` [patch] 2.4.0-prerelease drm and modversions Keith Owens
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=200101010735.BAA12841@duracef.shout.net \
--to=mec@shout.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dri-devel@lists.sourceforge.net \
--cc=jjs@pobox.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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