From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] latencytop: disable static build
Date: Mon, 7 Apr 2014 20:12:07 +0300 [thread overview]
Message-ID: <20140407171207.GJ4096@tarshish> (raw)
In-Reply-To: <20140407175300.4b6111f1@skate>
Hi Thomas,
On Mon, Apr 07, 2014 at 05:53:00PM +0200, Thomas Petazzoni wrote:
> On Mon, 7 Apr 2014 17:00:34 +0300, Baruch Siach wrote:
> > The Makefile of latencytop doesn't take static linking into account when
> > calling pkg-config for glib-2.0. Disable static build of latencytop.
>
> Well, there are *lots* of packages that don't take into account static
> linking with pkg-config. There is even a patch proposed to improve this
> situation: http://patchwork.ozlabs.org/patch/326741/.
Thanks for the tip. I'll test this patch and report.
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 -
prev parent reply other threads:[~2014-04-07 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 14:00 [Buildroot] [PATCH] latencytop: disable static build Baruch Siach
2014-04-07 15:53 ` Thomas Petazzoni
2014-04-07 17:12 ` Baruch Siach [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=20140407171207.GJ4096@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.