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 linksLDFLAGS_MODULE is not usable in module build out of kernel tree since
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
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:
From your description you want to add a specific set of options tothe 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 librariesI 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.