From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/3] package/feh: Fix build issue with some older cross-compilers
Date: Wed, 15 Nov 2017 22:35:08 +0100 [thread overview]
Message-ID: <20171115223508.249b809c@windsurf.lan> (raw)
In-Reply-To: <20171115213303.i5uyauphzo6pplyv@x230>
Hello,
On Wed, 15 Nov 2017 22:33:04 +0100, Petr Vorel wrote:
> > std=gnu11 was only added in gcc 4.7, so using this would break the
> > build with gcc < 4.7. According to the error message, only C99 is
> > needed, so could you try instead -std=c99, which is available since at
> > least gcc 4.2 ?
>
> Would it be -std=gnu99 sufficient for buildroot? Or it's a problem for some compilers?
> If yes, I'll patch the sources as it depends on alphasort(), which is not available on c99.
gnu99 is available since gcc 4.2 as well, see
https://gcc.gnu.org/onlinedocs/gcc-4.2.0/gcc/Standards.html#Standards,
so gnu99 should be fine.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-11-15 21:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 13:27 [Buildroot] [PATCH v2 1/3] package/feh: Fix build issue with some older cross-compilers Petr Vorel
2017-11-15 13:27 ` [Buildroot] [PATCH v2 2/3] package/feh: Cleanup build configuration Petr Vorel
2017-11-15 13:27 ` [Buildroot] [PATCH v2 3/3] package/feh: Bump to version 2.22.2 Petr Vorel
2017-11-15 21:09 ` [Buildroot] [PATCH v2 1/3] package/feh: Fix build issue with some older cross-compilers Thomas Petazzoni
2017-11-15 21:33 ` Petr Vorel
2017-11-15 21:35 ` Thomas Petazzoni [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=20171115223508.249b809c@windsurf.lan \
--to=thomas.petazzoni@free-electrons.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