From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] aircrack-ng: new package
Date: Sat, 09 Feb 2013 14:18:19 +0200 [thread overview]
Message-ID: <51163E8B.4070904@petroprogram.com> (raw)
In-Reply-To: <20130209130104.50bd9c14@skate>
Hi Thomas
9.2.2013 14:01, Thomas Petazzoni kirjoitti:
> Dear Stefan Fr?berg,
>
> On Sat, 09 Feb 2013 13:45:39 +0200, Stefan Fr?berg wrote:
>
>> Ah, but now I see it.
>> That -Werror thing.
>> I always define -Wno-error in my buildroot CFLAGS because
>> I hate it when people think that their code is perfect (it newer is,
>> and neither is my code) and
>> stop compiling because warnings.
>> That's why my compilationg with 4.5 succeeded.
> Indeed, if the reason the compilation fails is because of -Werror, then
> remove -Werror from the compilation flags, and use the stable 1.1
> release rather than the SVN version.
>
> Best regards,
>
> Thomas
I Agree.
It's always good to take the latest stable version (if there is any) as
starting point and included in buildroot.
And after that is kosher, then maybe go for the latest and greatest
bleeding edge version.
Regards
Stefan
prev parent reply other threads:[~2013-02-09 12:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 16:16 [Buildroot] [PATCH] aircrack-ng: new package Laurent Cans
2013-02-08 15:30 ` Gustavo Zacarias
2013-02-08 18:53 ` Laurent CANS
2013-02-08 15:32 ` Thomas Petazzoni
2013-02-08 15:37 ` Stephan Hoffmann
2013-02-08 20:26 ` Arnout Vandecappelle
2013-02-10 15:08 ` Laurent CANS
2013-02-12 17:01 ` Arnout Vandecappelle
2013-02-08 16:20 ` Stefan Fröberg
2013-02-08 22:38 ` Laurent CANS
2013-02-09 11:36 ` Stefan Fröberg
2013-02-09 11:45 ` Stefan Fröberg
2013-02-09 12:01 ` Thomas Petazzoni
2013-02-09 12:18 ` 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=51163E8B.4070904@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