From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 2/2] package/pango: needs libfribidi
Date: Thu, 12 Dec 2019 22:34:48 +0100 [thread overview]
Message-ID: <20191212223448.7e1dc8ba@windsurf.home> (raw)
In-Reply-To: <20191209205224.2762-2-ps.report@gmx.net>
On Mon, 9 Dec 2019 21:52:24 +0100
Peter Seiderer <ps.report@gmx.net> wrote:
> Fixes:
> http://autobuild.buildroot.net/results/f16fda910da23dfe5f8ac1cb51f9dbcec444b516
>
> subprocess.CalledProcessError: Command '['git', 'clone', 'https://github.com/fribidi/fribidi.git', 'fribidi']' returned non-zero exit status 128.
>
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
This commit title really was too short, especially we like to
understand since when this problem is occurring. So I've added the
following paragraph:
Since commit 5cce413eb11ac75f5c48ed351896c5d1c33961d5 ("package/pango:
bump to version 1.44.6"), pango needs libfribidi. Through the Meson
subprojects mechanism, it tries to download it by itself if not
available. But in Buildroot, we definitely want to use the separate
libfribidi package, so let's add it as a dependency of pango.
A side question is: is here a way to tell Meson to never ever download
subprojects by itself, and instead bail out loudly ?
I've applied with the improved commit log. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-12-12 21:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 20:52 [Buildroot] [PATCH v1 1/2] package/libfribidi: enable host build Peter Seiderer
2019-12-09 20:52 ` [Buildroot] [PATCH v1 2/2] package/pango: needs libfribidi Peter Seiderer
2019-12-12 21:34 ` Thomas Petazzoni [this message]
2019-12-12 21:39 ` Peter Seiderer
2019-12-23 15:30 ` Peter Seiderer
2019-12-23 8:04 ` Peter Korsgaard
2019-12-12 21:33 ` [Buildroot] [PATCH v1 1/2] package/libfribidi: enable host build Thomas Petazzoni
2019-12-23 8:03 ` 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=20191212223448.7e1dc8ba@windsurf.home \
--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