Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Valentine Barshak <gvaxon@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gqview: Fix build failure due to missing -lm
Date: Thu, 25 Oct 2012 01:35:34 +0400	[thread overview]
Message-ID: <50885F26.8000701@gmail.com> (raw)
In-Reply-To: <CAFbHwiSwLqa=JSw=yqsEmHO7sqvgRmPQEgR454g=rBCu0qLdOg@mail.gmail.com>

On 10/25/2012 12:51 AM, Will Newton wrote:
> On Wed, Oct 24, 2012 at 8:22 PM, Valentine Barshak <gvaxon@gmail.com> wrote:
>> On 10/07/2012 12:35 AM, Valentine Barshak wrote:
>>>
>>> Signed-off-by: Valentine Barshak <gvaxon@gmail.com>
>>> ---
>>>    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))
>>>
>>>
>>
>> Does this work for everyone else or is it just deprecated and nobody should
>> use it?
>>
>> I can't build without -lm neither in BR nor using my native host tools.
>
> Which version of binutils are you using? 2.22?
>

Yes, 2.22.

Thanks,
Val.

  reply	other threads:[~2012-10-24 21:35 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 [this message]
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
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=50885F26.8000701@gmail.com \
    --to=gvaxon@gmail.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