From: Koen Martens <gmc@sonologic.nl>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] capnproto: new package
Date: Fri, 7 Jul 2017 20:29:55 +0200 [thread overview]
Message-ID: <20170707182955.GA14836@sunra> (raw)
In-Reply-To: <20170707201643.79454a0c@windsurf>
Hi,
On Fri, Jul 07, 2017 at 08:16:43PM +0200, Thomas Petazzoni wrote:
> On Fri, 7 Jul 2017 19:39:11 +0200, Koen Martens wrote:
> > 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.
*doh*, indeed I had some old stuff in ~/br-test-pkg, thanks!
- Koen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170707/24b768f5/attachment.asc>
next prev parent reply other threads:[~2017-07-07 18:29 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
2017-07-07 18:29 ` Koen Martens [this message]
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=20170707182955.GA14836@sunra \
--to=gmc@sonologic.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.