From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] capnproto: new package
Date: Fri, 7 Jul 2017 20:16:43 +0200 [thread overview]
Message-ID: <20170707201643.79454a0c@windsurf> (raw)
In-Reply-To: <20170707173911.GA26346@sunra>
Hello,
On Fri, 7 Jul 2017 19:39:11 +0200, Koen Martens wrote:
> It's a temporary patch anyway, i have an open merge request with
> upstream.
>
> Anyway, i'm trying to utils/test-pkg capnproto with
> CAPNPROTO_AUTORECONF = YES, but get failures such as:
>
> /bin/bash:
> /home/gmc/br-test-pkg/armv5-ctng-linux-gnueabi/host/bin/autoreconf: No
> such file or directory
>
> Interestingly,
> /home/gmc/br-test-pkg/armv5-ctng-linux-gnueabi/host/usr/bin/autoreconf
> does exist, so with usr/bin instead of bin.
Are you doing completely clean builds here? If you have already done a
run of test-pkg before, make sure to clean up the build folders.
We have recently moved $(HOST_DIR)/usr to $(HOST_DIR), and it seems
like you have a mix of things before and after this change.
If that still doesn't work after a full rebuild, let us know, there
might be a real bug somewhere, though I would assume the autobuilders
would have caught such an obvious problem.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-07 18:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 15:40 [Buildroot] [PATCH 1/1] capnproto: new package Koen Martens
2017-07-06 19:16 ` Thomas Petazzoni
2017-07-07 6:58 ` Koen Martens
2017-07-07 7:44 ` Thomas Petazzoni
2017-07-07 17:39 ` Koen Martens
2017-07-07 18:16 ` Thomas Petazzoni [this message]
2017-07-07 18:29 ` Koen Martens
2017-07-06 22:44 ` 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=20170707201643.79454a0c@windsurf \
--to=thomas.petazzoni@free-electrons.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