Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] package/libgeotiff: fix static linking with tiff
Date: Thu, 10 Oct 2019 23:14:56 +0200	[thread overview]
Message-ID: <20191010231456.7250309a@windsurf> (raw)
In-Reply-To: <20191009170325.24709-1-fontaine.fabrice@gmail.com>

On Wed,  9 Oct 2019 19:03:23 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> Put back patch that was wrongly removed when bumping libgeotiff to
> version 1.5.1 in commit	1edf0383a6a9d17a27d831bb02833870655d43d9
> 
> Fixes:
>  - http://autobuild.buildroot.org/results/3eb3d41d3288c08616b68d52fdc7525c57c8e023
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  ...Use-pkg-config-for-libtiff-detection.patch | 49 +++++++++++++++++++
>  package/libgeotiff/libgeotiff.mk              |  2 +
>  2 files changed, 51 insertions(+)
>  create mode 100644 package/libgeotiff/0001-Use-pkg-config-for-libtiff-detection.patch

Series applied, thanks. In PATCH 2/3, the solution to add -lstdc++ is
not great, as we really hardcode something that is quite internal to
the toolchain, but there's no other easy way to solve this.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      parent reply	other threads:[~2019-10-10 21:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-09 17:03 [Buildroot] [PATCH 1/3] package/libgeotiff: fix static linking with tiff Fabrice Fontaine
2019-10-09 17:03 ` [Buildroot] [PATCH 2/3] package/proj: add -lsdtc++ to Libs.Private Fabrice Fontaine
2019-10-09 17:03 ` [Buildroot] [PATCH 3/3] package/libgeotiff: fix static linking with proj Fabrice Fontaine
2019-10-10 21:14 ` 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=20191010231456.7250309a@windsurf \
    --to=thomas.petazzoni@bootlin.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