From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2017-02-13
Date: Wed, 15 Feb 2017 08:38:07 +0100 [thread overview]
Message-ID: <8760kbj44g.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170214232912.42d8a2df@free-electrons.com> (Thomas Petazzoni's message of "Tue, 14 Feb 2017 23:29:12 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
>> > sh4a | libraw-0.17.1 | NOK |
>> > http://autobuild.buildroot.net/results/908aef6c82d56060933713df217b6b2ba21a01b0
>>
>> error: 'SIZE_MAX' was not declared in this scope
>>
>> Missing header include I believe.
> This one is annoying.
> So libraw optionally depends on jasper, and it's when both are enabled
> that the problem occurs.
> The issue is that the jas_math.h header uses SIZE_MAX and other
> definitions of <stdint.h>, but those definitions are not visible to C++
> code, unless you define __STDC_LIMIT_MACROS.
> So one would think "just define __STDC_LIMIT_MACROS before including
> <stdint.h> in jas_math.h". Expect that libraw, before including jasper
> headers, includes other headers that already include <stdint.h>. So by
> the time jas_math.h includes <stdint.h>, it has already been included,
> and therefore, the definition of __STDC_LIMIT_MACROS in jas_math.h has
> no effect.
> I'm not sure how to fix this. Adding __STDC_LIMIT_MACROS to the build
> of libraw would fix it, but it's rather weird to have this
> implementation "detail" of jasper creep in all the way to users of the
> library.
I didn't look at libraw yet, but couldn't the jasper include just be
moved to the top of the file?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2017-02-15 7:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 7:28 [Buildroot] [autobuild.buildroot.net] Build results for 2017-02-13 Thomas Petazzoni
2017-02-14 13:27 ` [Buildroot] Analysis of build " Thomas Petazzoni
2017-02-14 14:51 ` Peter Korsgaard
2017-02-14 15:10 ` Thomas Petazzoni
2017-02-14 19:21 ` Peter Korsgaard
2017-02-14 20:03 ` Thomas Petazzoni
2017-02-14 20:21 ` Peter Korsgaard
2017-02-14 15:44 ` Philippe Proulx
2017-02-14 16:39 ` Yann E. MORIN
2017-02-14 20:02 ` Thomas Petazzoni
2017-02-14 20:05 ` Yann E. MORIN
2017-02-14 18:02 ` Baruch Siach
2017-02-14 19:37 ` Peter Korsgaard
2017-02-14 22:29 ` Thomas Petazzoni
2017-02-15 7:38 ` Peter Korsgaard [this message]
2017-02-15 8:33 ` Thomas Petazzoni
2017-02-15 23:14 ` Arnout Vandecappelle
2017-02-16 8:36 ` Thomas Petazzoni
2017-02-15 2:45 ` Sam Bobroff
2017-02-15 8:37 ` Thomas Petazzoni
2017-02-15 13:22 ` Gustavo Zacarias
2017-02-16 20:34 ` Bernd Kuhls
2017-02-22 11:26 ` [Buildroot] [arc-buildroot] " Vlad Zakharov
2017-02-22 12:48 ` Thomas Petazzoni
2017-02-22 13:01 ` Vlad Zakharov
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=8760kbj44g.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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