From: Henry Nestler <Henry.Ne@Arcor.de>
To: Sam Ravnborg <sam@ravnborg.org>
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: Wed, 26 Sep 2007 13:31:31 +0200 [thread overview]
Message-ID: <46FA4313.1060201@Arcor.de> (raw)
In-Reply-To: <20070926110130.GA20950@uranus.ravnborg.org>
Hello Sam,
Sam Ravnborg wrote:
>>>> What macro should set for linker parameters of foo.o ? I'm not shure.
>>> Have you read:
>>> Documentation/kbuild/makfilefiles.txt?
>> Yes. This was a *very* helpfull. And many examples spokes about
>> LDFLAGS_$@ there. Not directly described for modules.
>
> Took a deeper look.
> I saw one reference to LDFLAGS_$@ that is wrong:
> LDFLAGS Generic $(LD) options
>
> Flags used for all invocations of the linker.
> Often specifying the emulation is sufficient.
>
> Example:
> #arch/s390/Makefile
> LDFLAGS := -m elf_s390
> Note: EXTRA_LDFLAGS and LDFLAGS_$@ can be used to further customise
> the flags used. See chapter 7.
>
> The chapter reference is also bad...
> The other references to the LDFLAGS_$@ are in other situations - it is
> used in several places.
>
> If your example requires the LDFALGS_$@ I wil introduce it - for now
> it has not been required (except for vdso support where it was hacked).
I will check EXTRA_LDFLAGS compatibilities with older kernel versions.
Than I come back with results. Currently I no need LDFLAGS_$@.
--
Henry
next prev parent reply other threads:[~2007-09-26 11:31 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
2007-09-26 9:56 ` Henry Nestler
2007-09-26 11:01 ` Sam Ravnborg
2007-09-26 11:31 ` Henry Nestler [this message]
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=46FA4313.1060201@Arcor.de \
--to=henry.ne@arcor.de \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
--cc=sam@ravnborg.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