From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] gutenprint: fix host build when libusb found
Date: Fri, 15 Apr 2016 07:49:09 +0300 [thread overview]
Message-ID: <20160415044908.GG2092@tarshish> (raw)
In-Reply-To: <20160402184733.GA8155@waldemar-brodkorb.de>
Hi Waldemar,
On Sat, Apr 02, 2016 at 08:47:33PM +0200, Waldemar Brodkorb wrote:
> Allow to disable USB support, otherwise host build breaks when
> libusb is found as installation tries to install to /usr.
> Fixes following autobuild error:
> http://autobuild.buildroot.net/results/081b3be918ac1eaa8cfbc5919e00bc1ea267c1df/
>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
Tested-by: Baruch Siach <baruch@tkos.co.il>
> ---
> .../0004-build-usb-backends-conditional.patch | 23 ++++++++++++++++++++++
> package/gutenprint/gutenprint.mk | 1 +
> 2 files changed, 24 insertions(+)
> create mode 100644 package/gutenprint/0004-build-usb-backends-conditional.patch
>
> diff --git a/package/gutenprint/0004-build-usb-backends-conditional.patch b/package/gutenprint/0004-build-usb-backends-conditional.patch
> new file mode 100644
> index 0000000..db44a12
> --- /dev/null
> +++ b/package/gutenprint/0004-build-usb-backends-conditional.patch
> @@ -0,0 +1,23 @@
> +Allow to disable USB backend
> +
> +Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
Have you tried to upstream this patch?
Since we would now be patching also configure.ac, please updated the
AUTORECONF comment in gutenprint.mk.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2016-04-15 4:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-02 18:47 [Buildroot] [PATCH] gutenprint: fix host build when libusb found Waldemar Brodkorb
2016-04-15 4:49 ` Baruch Siach [this message]
2016-04-15 9:31 ` Peter Korsgaard
2016-04-15 17:50 ` Waldemar Brodkorb
2016-04-15 22:07 ` Peter Korsgaard
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=20160415044908.GG2092@tarshish \
--to=baruch@tkos.co.il \
--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