From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gqview: Fix build failure due to missing -lm
Date: Fri, 26 Oct 2012 09:38:00 +0200 [thread overview]
Message-ID: <508A3DD8.8060009@mind.be> (raw)
In-Reply-To: <1349555736-10008-1-git-send-email-gvaxon@gmail.com>
On 06/10/12 22:35, Valentine Barshak wrote:
> Signed-off-by: Valentine Barshak<gvaxon@gmail.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Tested-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Problem can be reproduced on e.g. x86_64 with external toolchain.
And since upstream is dead, the simple addition of -lm to LIBS is an
adequate solution.
Regards,
Arnout
> ---
> package/gqview/gqview.mk | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/package/gqview/gqview.mk b/package/gqview/gqview.mk
> index 2f64cd0..7d09fda 100644
> --- a/package/gqview/gqview.mk
> +++ b/package/gqview/gqview.mk
> @@ -7,6 +7,7 @@ GQVIEW_VERSION = 2.1.5
> GQVIEW_SOURCE = gqview-$(GQVIEW_VERSION).tar.gz
> GQVIEW_SITE = http://prdownloads.sourceforge.net/gqview
> GQVIEW_DEPENDENCIES = host-pkg-config libgtk2
> +GQVIEW_CONF_ENV = LIBS="-lm"
>
> $(eval $(autotools-package))
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-10-26 7:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-06 20:35 [Buildroot] [PATCH] gqview: Fix build failure due to missing -lm Valentine Barshak
2012-10-24 19:22 ` Valentine Barshak
2012-10-24 20:51 ` Will Newton
2012-10-24 21:35 ` Valentine Barshak
2012-10-25 9:02 ` Will Newton
2012-10-25 17:25 ` Valentine Barshak
2012-10-25 18:23 ` Will Newton
2012-10-25 19:02 ` Valentine Barshak
2012-10-26 7:38 ` Arnout Vandecappelle [this message]
2012-10-30 11:25 ` Markos Chandras
2012-11-07 19:06 ` 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=508A3DD8.8060009@mind.be \
--to=arnout@mind.be \
--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.