From: Alex Suykov <alex.suykov@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2016-01-04
Date: Tue, 5 Jan 2016 14:51:22 +0200 [thread overview]
Message-ID: <20160105125122.GA24278@vostro> (raw)
In-Reply-To: <20160105073021.6CB4110127C@stock.ovh.net>
Tue, Jan 05, 2016 at 08:30:21AM +0100, Thomas Petazzoni wrote:
> arm | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/199fbe68e11df7fac890b79e774dd0369988c917/
> bfin | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/786b2d83f7036c41a7e461ce9ab334c2ba0a4820/
> sh4a | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/f19114c40a4ecd2642e41bba36e97987623b0149/
> bfin | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/0d9a3693b1f8f9f94640c5d5a7c3aabdee015818/
> powerpc | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/57a45d77cf8549f572579f39c9dba7e31f8f02fd/
> nios2 | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/e058f1d7915e580ffbe1586beac652057e4d8515/
> mips64el | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/e7ee5dedc4f62d9007875fd47ddc5c2c0d210968/
Looks like a host gcc issue, maybe. I can't reproduce it.
Apparently it comes down to whether this code is correct:
typedef struct rsa_st RSA; /* from openssl headers */
typedef struct rsa_st RSA; /* from vboot-utils */
and all compilers I can check agree that it is.
host-vboot-utils are built with CC=/usr/bin/gcc
Is there any way to tell which gcc version do the autobuilders use?
prev parent reply other threads:[~2016-01-05 12:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-01-04 Thomas Petazzoni
2016-01-05 12:51 ` Alex Suykov [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=20160105125122.GA24278@vostro \
--to=alex.suykov@gmail.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