Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Martens <gmc@sonologic.nl>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] capnproto: new package
Date: Fri, 7 Jul 2017 19:39:11 +0200	[thread overview]
Message-ID: <20170707173911.GA26346@sunra> (raw)
In-Reply-To: <20170707094443.3de6a9e0@windsurf.lan>

Hi,

On Fri, Jul 07, 2017 at 09:44:43AM +0200, Thomas Petazzoni wrote:
> On Fri, 07 Jul 2017 08:58:08 +0200, Koen Martens wrote:
> > >Since upstream uses Git, we prefer to have a Git-formatted patch, i.e
> > >generated with "git format-patch -N". It should also have a proper
> > >commit title, i.e a single line at the beginning that summarizes the
> > >commit, separated from the rest of the commit log by one empty line.  
> > 
> > Sure, except the published tarball is from a subdirectory of the
> > upstream git repo. So creating a git patch with format-patch results
> > in a patch that needs 'patch -p2' to apply in buildroot. I understand
> > this is impossible. What do you prefer i do? Manually modify the
> > patch to remove the subdir that should be stripped?
> 
> Gah, OK. Then perhaps a quick comment in the patch description would be
> nice, like:
> 
> [Patch cannot be generated with git format-patch, as the upstream Git
> repository directory layout doesn't match the tarball directory layout]

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.

I have a one-line capnproto.conf i feed to test-pkg:

BR2_PACKAGE_CAPNPROTO=y

What am i doing wrong?

- 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/f686fde5/attachment.asc>

  reply	other threads:[~2017-07-07 17:39 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 [this message]
2017-07-07 18:16         ` Thomas Petazzoni
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=20170707173911.GA26346@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox