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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <32637993-b73f-c2cb-6823-590c1638b5a6@infradead.org>
Date:   Sun, 10 May 2020 09:02:52 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Mahmood Naderan <mahmood.nt@...il.com>,
        linux-kernel@...r.kernel.org
Subject: Re: Using a custom LDFLAG for all objects and binaries

On 5/10/20 6:35 AM, Mahmood Naderan wrote:
> Hi
> I would like to modify the kernel makefile in a way to include
> --emit-relocs for every file that is linked during the process of
> kernel make.
> I see
> 
> KBUILD_HOSTLDFLAGS  := $(HOST_LFS_LDFLAGS) $(HOSTLDFLAGS)
> LDFLAGS_MODULE  =
> LDFLAGS_vmlinux =
> ...
> 
> But I don't know which one is the main. Should I put that option in
> front of every LD* variable? Or it is possible to apply one variable
> for every file that is linked?
> Appreciate your help.
> 
> 
> Regards,
> Mahmood

Hi,

Have you read Documentation/kbuild/makefiles.rst ?

    LDFLAGS
	Generic $(LD) options

	Flags used for all invocations of the linker.


You could always build with V=1 to see all of the
command lines that are used in the build.

HTH.
-- 
~Randy

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ