From: Alexander Lukichev <alexander.lukichev@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] infozip: fix cross-compilation issues
Date: Mon, 03 Feb 2014 11:26:20 +0200 [thread overview]
Message-ID: <52EF60BC.4040600@gmail.com> (raw)
In-Reply-To: <87ob2pp8xa.fsf@dell.be.48ers.dk>
Hi Peter, Romain, all,
On 02/02/2014 10:16 PM, Peter Korsgaard wrote:
>>>>>> "Alexander" == Alexander Lukichev <alexander.lukichev@gmail.com> writes:
> > +-CFLAGS = -O2 $(CFLAGS_NOOPT)
> > ++CFLAGS ?= -02 $(CFLAGS_NOOPT)
> > Excuse me, is it -02 that's meant here?
> Good catch. Actually in the context of Buildroot we don't want the
> package to hardcode the optimization level, so I will simply drop it.
Just out of curiosity, I have not seen an -0<N> gcc optimization
flag (as opposed to -O<N>, zero vs. a big O). Is it somewhere on
gcc manual?
--
Best regards,
Alexander Lukichev
next prev parent reply other threads:[~2014-02-03 9:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 22:15 [Buildroot] [PATCH 2/3] infozip: fix cross-compilation issues Romain Naour
2014-02-02 9:31 ` Peter Korsgaard
2014-02-02 18:40 ` Alexander Lukichev
2014-02-02 20:16 ` Peter Korsgaard
2014-02-02 22:14 ` Romain Naour
2014-02-03 9:26 ` Alexander Lukichev [this message]
2014-02-04 9:01 ` Peter Korsgaard
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=52EF60BC.4040600@gmail.com \
--to=alexander.lukichev@gmail.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