| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 26 Sep 2007 13:31:31 +0200 From: Henry Nestler <Henry.Ne@...or.de> To: Sam Ravnborg <sam@...nborg.org> CC: linux-kernel@...r.kernel.org, Roland McGrath <roland@...hat.com> Subject: Re: kbuild: LDFLAGS_MODULE unusable for external module builds (2.6.23-rc2) 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists