From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] infozip: fix cross-compilation issues
Date: Sun, 02 Feb 2014 10:31:58 +0100 [thread overview]
Message-ID: <87txchrhbl.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1391120128-8375-1-git-send-email-romain.naour@openwide.fr> (Romain Naour's message of "Thu, 30 Jan 2014 23:15:28 +0100")
>>>>> "Romain" == Romain Naour <romain.naour@openwide.fr> writes:
> - Use CFLAGS from command line
> - Remove "Check C compiler type (optimization options)"
> This test force optimization to -O3
> while it is already set in CFLAGS
> - Don't use host CPP
> - Remove "Check for Large File Support"
> LFS support is already set in CFLAGS
> Note: configure script still use host nm
> Signed-off-by: Romain Naour <romain.naour@openwide.fr>
Committed, thanks.
Please don't forget to send the patch upstream.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-02-02 9:31 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 [this message]
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
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=87txchrhbl.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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