Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] Advice on buildroot implementation
Date: Thu, 21 Feb 2013 12:38:57 +0200	[thread overview]
Message-ID: <5125F941.6070606@petroprogram.com> (raw)
In-Reply-To: <51250A00.8020804@mind.be>

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

      reply	other threads:[~2013-02-21 10:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-19 23:03 [Buildroot] Advice on buildroot implementation Gregory Perry
2013-02-19 23:18 ` Arnout Vandecappelle
2013-02-20  1:24   ` Gregory Perry
2013-02-20 11:08     ` Stefan Fröberg
2013-02-20 17:38       ` Arnout Vandecappelle
2013-02-21 10:38         ` Stefan Fröberg [this message]

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=5125F941.6070606@petroprogram.com \
    --to=stefan.froberg@petroprogram.com \
    --cc=buildroot@busybox.net \
    /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