From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: g++ lib problem
Date: Fri, 13 Mar 2009 10:40:57 -0700 [thread overview]
Message-ID: <19c1b8a90903131040k5d7b1f40kfbfafbb787e45341@mail.gmail.com> (raw)
In-Reply-To: <ac9c93b10903130815t10265676ld8e464ab460689dd@mail.gmail.com>
On Fri, Mar 13, 2009 at 8:15 AM, Frans Meulenbroeks
<fransmeulenbroeks@gmail.com> wrote:
> 2009/3/12 Khem Raj <raj.khem@gmail.com>:
> [...]
>>
>> I see it gets it from libm but g++ specifiies -lm for you where as gcc
>> does not. I think the problem is that ARM have same precision for
>> double and long double so glibc defines __NO_LONG_DOUBLE_MATH for ARM
>> as a result the prototypes for the *l functions are not emitted into
>> math.h. Although in glibc they are aliases for the corresponding
> [...]
>
> Khem,
>
> Thanks for the explanation.
> Should we change the glibc package to resolve this?
>
hmmm IMO I think you should fix the application to not ask for long
double functions on platforms where long double is
not different than double and fixing glibc could be ok too. Care for a patch :)
> Frans
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
next prev parent reply other threads:[~2009-03-13 17:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 9:52 g++ lib problem Frans Meulenbroeks
2009-03-12 17:37 ` Khem Raj
2009-03-12 20:34 ` Frans Meulenbroeks
2009-03-12 21:58 ` Khem Raj
2009-03-13 15:15 ` Frans Meulenbroeks
2009-03-13 17:40 ` Khem Raj [this message]
2009-03-14 11:00 ` Frans Meulenbroeks
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=19c1b8a90903131040k5d7b1f40kfbfafbb787e45341@mail.gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/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.