Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 1/1] package/gutenprint: Un-deprecate and bump version to 5.2.11
Date: Sun, 21 Feb 2016 00:19:59 +0100	[thread overview]
Message-ID: <20160221001959.3c65b74d@free-electrons.com> (raw)
In-Reply-To: <1453664973-21165-1-git-send-email-olivier.schonken@gmail.com>

Dear Olivier Schonken,

On Sun, 24 Jan 2016 21:49:33 +0200, Olivier Schonken wrote:
> Signed-off-by: Olivier Schonken <olivier.schonken@gmail.com>
> ---
> Changes V4 -> V5
> Updated Gutenprint with recently released 5.2.11
> Added patch to fix endianness detection. Will submit upstream
>  ...-print-olympus.c-fix-endianness-detection.patch | 33 ++++++++++++++++++++++
>  package/gutenprint/Config.in                       |  2 --
>  package/gutenprint/gutenprint.hash                 |  2 +-
>  package/gutenprint/gutenprint.mk                   |  2 +-
>  4 files changed, 35 insertions(+), 4 deletions(-)
>  create mode 100644 package/gutenprint/0003-print-olympus.c-fix-endianness-detection.patch

This package didn't build, because host-gutenprint was missing a
dependency on host-pkgconf. This dependency is needed because we
autoreconf host-gutenprint, and configure.ac uses PKG_CHECK_MODULES(),
whose definition is only available if host-pkgconf has been built.

I've added this dependency to host-gutenprint, and applied your patch
to the next branch. Thanks a lot!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2016-02-20 23:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-24 19:49 [Buildroot] [PATCH v5 1/1] package/gutenprint: Un-deprecate and bump version to 5.2.11 Olivier Schonken
2016-02-20 23:19 ` Thomas Petazzoni [this message]

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=20160221001959.3c65b74d@free-electrons.com \
    --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