From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-11-24
Date: Mon, 25 Nov 2013 23:49:13 +0100 [thread overview]
Message-ID: <5293D3E9.2090207@mind.be> (raw)
In-Reply-To: <OF0E9DA113.910F94AB-ON86257C2E.00328BF4-86257C2E.003369F4@rockwellcollins.com>
On 25/11/13 10:21, Ryan Barnett wrote:
> Thomas P, All,
>
> Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote on
> 11/25/2013 01:30:02 AM:
>
> > powerpc | host-protobuf-c-0.15 | NOK |
> http://autobuild.buildroot.net/results/10db94f960db6cc8b2fbcafa66aa487fc66f99c6/
>
> I looked into this last night and I was unable to reproduce the issue
> (from pulling the defconfig). From looking at the logs, it appears that
> the issue is that a file wasn't generated before trying to compile the
> code. In my experience, errors like below are due to the makefile not
> having their dependencies correct. I tired rebuilding this package around
> 5-7 times and I never ran into this error with the defconfig provided.
I have seen exactly the same error before and sent a fix to the list,
but I can't find it back... so I guess I must have imagined it.
Anyway, there are two solutions: either disable parallel build for
protobuf-c, or fix the dependencies. IIRC the problem is actually that
the static and shared library are built in parallel with the same object
files.
Regards,
Arnout
>
> cxx-generate-packed-data.cc:28: error: 'foo' is not a namespace-name
> cxx-generate-packed-data.cc:28: error: expected namespace-name before ';'
> token
> In file included from cxx-generate-packed-data.cc:35:
> common-test-arrays.h:44: error: 'TestEnumSmall' does not name a type
> common-test-arrays.h:45: error: 'TestEnumSmall' does not name a type
> common-test-arrays.h:47: error: 'TestEnumSmall' does not name a type
> In file included from cxx-generate-packed-data.cc:35:
> common-test-arrays.h:51: error: 'TestEnum' does not name a type
> common-test-arrays.h:52: error: 'TestEnum' does not name a type
> common-test-arrays.h:53: error: 'TestEnum' does not name a type
> cxx-generate-packed-data.cc:39: error: variable or field
> 'dump_message_bytes' declared void
> cxx-generate-packed-data.cc:39: error: 'google' has not been declared
> cxx-generate-packed-data.cc:39: error: 'message' was not declared in this
> scope
> cxx-generate-packed-data.cc:40: error: expected primary-expression before
> 'const'
>
> Thanks,
> -Ryan
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-11-25 22:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2013-11-24 Thomas Petazzoni
2013-11-25 9:21 ` Ryan Barnett
2013-11-25 15:55 ` Thomas De Schampheleire
2013-11-25 16:01 ` Ryan Barnett
2013-11-25 22:49 ` Arnout Vandecappelle [this message]
2013-11-25 22:58 ` Ryan Barnett
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=5293D3E9.2090207@mind.be \
--to=arnout@mind.be \
--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