linux-kernel - Re: [PATCH 0/4] Compile kernel with -fwhole-program --combine

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]

Date:	Fri, 25 Aug 2006 11:51:28 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	David Woodhouse <dwmw2@...radead.org>
cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4] Compile kernel with -fwhole-program --combine


>> That's what I meant. Assume I explicitly built read.o foo.o and bar.o.
>> If I then run the regular make, it will rerun gcc for read.c foo.c and 
>> bar.c rather than using the already-created .o files for linking. 
>
>You built something manually that wasn't needed, and then it wasn't
>used. Is there a problem here?

Although I cannot give you any logical reasons, there are possibly reasons 
why building some things manually might help. Oh well, I think in that case 
I just pass a make option CONFIG_NOCOMBINE, as you said.


Jan Engelhardt
-- 
-
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/