From: Sam Ravnborg <sam@ravnborg.org>
To: Henry Nestler <Henry.Ne@Arcor.de>
Cc: linux-kernel@vger.kernel.org, Roland McGrath <roland@redhat.com>
Subject: Re: kbuild: LDFLAGS_MODULE unusable for external module builds (2.6.23-rc2)
Date: Tue, 25 Sep 2007 21:22:50 +0200 [thread overview]
Message-ID: <20070925192250.GA14689@uranus.ravnborg.org> (raw)
In-Reply-To: <46F8D9B8.3090806@Arcor.de>
Hi Henry.
On Tue, Sep 25, 2007 at 11:49:44AM +0200, Henry Nestler wrote:
> In reference of git 114f51577724b782a30f4f5ceaee9880de93d776:
> > kbuild: use LDFLAGS_MODULE only for .ko links
> >
> > Sam Ravnborg pointed out that Documentation/kbuild/makefiles.txt
> > already
> > says this is what it's for. This patch makes the reality live up to
> > the
> > documentation. This fixes the problem of LDFLAGS_BUILD_ID getting
> > into too
> > many places.
>
> LDFLAGS_MODULE is not usable in module build out of kernel tree since
> 2.6.23-rc2. LDFLAGS_$@ should use, but does never work. - Not for
> external module builds with the option "M=..."
LDFLAGS_MODULE are reserved for architectures and modules be external
or not should never ude LDFLAGS_MODULE.
And LDFALGS_$@ have never been documented to work for modules - dunno
where you have that from.
IIRC we only use LDFALGS_$@ in the ld macro to be used by bootloaders.
>
> What macro should set for linker parameters of foo.o ? I'm not shure.
Have you read:
Documentation/kbuild/makfilefiles.txt?
Here it is documented how to use the relevant variables.
> Currently found, that only LDFLAGS is usable. But, found LDFLAGS in
> modpost calls, there also exist a --start-group/--end-group. Is it right
> to use it for external module?
LDFLAGS are a kernel wide variable. Modules shall not fiddle with it!
>From your description you want to add a specific set of options to
the linker in a specific Kbuild file.
This is what EXTRA_LDFLAGS are present to help you with.
As for the:
> # Deal with recursive depens of libraries
I am not sure what you mean (despite yout comprehensive description).
Please try if EXTRA_LDFLAGS := --start-group lib.a --end-group
will solve your need.
I'm afraid not due to the placement of the --start-group --end-group.
If this does not help you please give me specific examples of how
the ld command-line should be then I can see how we tweak kbuild
to help you.
Sam
next prev parent reply other threads:[~2007-09-25 19:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 9:49 kbuild: LDFLAGS_MODULE unusable for external module builds (2.6.23-rc2) Henry Nestler
2007-09-25 19:22 ` Sam Ravnborg [this message]
2007-09-26 9:56 ` Henry Nestler
2007-09-26 11:01 ` Sam Ravnborg
2007-09-26 11:31 ` Henry Nestler
2007-09-27 8:21 ` Henry Nestler
2007-09-27 8:26 ` Sam Ravnborg
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=20070925192250.GA14689@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=Henry.Ne@Arcor.de \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.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