From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] grpc: new package
Date: Mon, 26 Nov 2018 22:58:00 +0100 [thread overview]
Message-ID: <20181126225800.40584f11@windsurf.home> (raw)
In-Reply-To: <CALxq1w5ZqCiG3CMZ1VRO25=mf3mWhJJ2+_+oArteVk7GzUQADw@mail.gmail.com>
Hello Robert,
On Sat, 24 Nov 2018 15:57:07 -0800, robert rose wrote:
> I just ran with native cmake 3.12.1.
> Everything worked and yes I did build grpc.
> I am using Fedora 29 and everything is up to date.
> After the make fails, do make V=1 and send me the output. I will try and
> help you debug it.
So in fact, I was wrong: I told you the CMake version that my Fedora 29
system uses, but on this system, it builds fine. The build failure
occurred on an older Ubuntu system, which has:
$ cmake --version
cmake version 3.5.1
The full build log is at:
http://code.bulix.org/h552dy-513207
And the host-grpc build with make V=1 is at:
http://code.bulix.org/qy4r3g-513210
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-11-26 21:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-18 21:19 [Buildroot] [PATCH v2 1/2] c-ares: support host build Robert Rose
2018-11-18 21:19 ` [Buildroot] [PATCH v2 2/2] grpc: new package Robert Rose
2018-11-24 14:12 ` Thomas Petazzoni
[not found] ` <CALxq1w45Krr6E8Ri7rxrDN9USkbPdLbqmmK2x-XiH3AmHHeqpg@mail.gmail.com>
2018-11-24 20:45 ` Thomas Petazzoni
2018-11-24 22:00 ` robert rose
2018-11-24 23:57 ` robert rose
2018-11-26 21:58 ` Thomas Petazzoni [this message]
2018-11-27 17:17 ` Arnout Vandecappelle
2018-11-18 21:33 ` [Buildroot] [PATCH v2 1/2] c-ares: support host build Arnout Vandecappelle
2018-11-18 21:37 ` Arnout Vandecappelle
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=20181126225800.40584f11@windsurf.home \
--to=thomas.petazzoni@bootlin.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