From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-02-23
Date: Sun, 24 Feb 2013 17:39:00 +0100 [thread overview]
Message-ID: <87bob9bra3.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <201302241638.19487.yann.morin.1998@free.fr> (Yann E. MORIN's message of "Sun, 24 Feb 2013 16:38:19 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
Hi,
Yann> I'm not sure how to solve that one:
Yann> CC build.linux/src/v4l.o
Yann> /home/test/test/output1/build/tvheadend-v3.3/src/v4l.c: In function
Yann> 'v4l_adapter_check':
Yann> /home/test/test/output1/build/tvheadend-v3.3/src/v4l.c:465:5: error: format
Yann> '%llx' expects argument of type 'long long unsigned int', but argument 6 has
Yann> type 'v4l2_std_id' [-Werror=format]
Yann> (twice the same error).
Yann> But:
Yann> - "long long unsigned int" is 64-bit wide, unsigned
Yann> - "v4l2_std_id" is a "__u64", so is 64-bit wide, unsigned
Yann> - it's only used for logging to stderr
Yann> I'm not very happy with disabling -Werror, so I was thinking
Yann> about casting the value to hush gcc.
Why not? Software should imho not use -Werror in release builds (it can
be very interesting during development though).
We already disable it for a number of other packages (cifs-utils,
classpath, ipsec-tools, libroxml, bellagio, synergy).
Yann> What's so special about mips64el that it does not like v4l2_std_id as an
Yann> unsigned 64-bit value (I've checked the headers, it is an __u64).
Sorry, don't know.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-02-24 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-24 7:34 [Buildroot] [autobuild.buildroot.net] Build results for 2013-02-23 Thomas Petazzoni
2013-02-24 15:38 ` Yann E. MORIN
2013-02-24 16:39 ` Peter Korsgaard [this message]
2013-02-24 21:53 ` Arnout Vandecappelle
2013-02-25 8:34 ` Thomas Petazzoni
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=87bob9bra3.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