From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?Stefan_Fr=F6berg?= Date: Thu, 21 Feb 2013 12:38:57 +0200 Subject: [Buildroot] Advice on buildroot implementation In-Reply-To: <51250A00.8020804@mind.be> References: <718DFA7882181D45B8BD18F31C46D55427A6A8E3@MBX204.domain.local>, <5124085A.1080903@mind.be> <718DFA7882181D45B8BD18F31C46D55427A6A997@MBX204.domain.local> <5124AEB0.5080808@petroprogram.com> <51250A00.8020804@mind.be> Message-ID: <5125F941.6070606@petroprogram.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 20.2.2013 19:38, Arnout Vandecappelle kirjoitti: > On 20/02/13 12:08, Stefan Fr?berg wrote: > [snip] >> CFLAGS = -flto -fwhole-program >> LDFLAGS= -flto -fuse-linker-plugin >> >> It could be also possible to compile whole system to make it smaller but >> it is very delicate and experimental process and some packages >> don't like some flags at all (For example zlib 1.2.7 does not like >> -fwhole-program). >> >> So Im asking everyone here: >> >> How can I filter out flags-per-package ? > > For most gcc -f and -W options, there's a no- variant. So > > ZLIB_CFLAGS = -fno-lto -fno-while-program > ZLIB_LDFLAGS = -fno-lto -fno-use-linker-plugin > >> And also enable flags-per-package? >> I would like to enable globally those LTO flags and filter some/all >> flags from problematic packages. > > You can only do that by changing the package .mk file. I don't think > we want to add infrastructure for per-package CFLAGS configuration... > > Regards, > Arnout Well, if there are no-variants for those lto flags then I will be perfectly happy to try full shrinking test of my system with lto. Regards Stefan