linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: walter harms <wharms-fPG8STNUNVg@public.gmane.org>
Cc: linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: RFC: Bug 60749 - Do not need to link against -lm for fabs*()
Date: Mon, 16 Sep 2013 16:57:12 +0200	[thread overview]
Message-ID: <52371C48.7040404@bfs.de> (raw)
In-Reply-To: <5234511C.7030500-fPG8STNUNVg@public.gmane.org>



Am 14.09.2013 14:05, schrieb walter harms:
> 
> 
> Am 13.09.2013 20:20, schrieb Michael Kerrisk (man-pages):
>> Walter,
>>
>> On Fri, Sep 13, 2013 at 6:46 PM, walter harms <wharms-fPG8STNUNVg@public.gmane.org> wrote:
>>> hi list,
>>> i was investigating this and the good news it that you still need a libm.
>>> On the other side the reporter is right he does not need to specify that.
>>> Obviously this depends on the linker script used.
>>>
>>> The math man pages say: "Link with -lm".
>>> Perhaps it is better to say 'You may need to Link with -lm".
>>>
>>> any comments on that ?
>>
>>
>> Thanks for looking at this bug. Could you elaborate a little more on
>> what it/sin't in the linker script that makes the difference?
>>
> 
> I have no clue what linker magic is needed.
> 
I know what it going on. the is no linker magic required.
The point is gcc build-ins. Some functions are replaced with
build-ins. That happens e.g. with fabs() what the original poster noted.
Disabling the build-ins with gcc -fno-builtin shows that the -lm is still
a requirement.

next problem, who will do the bugzilla-entry ?

re,
 wh


--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2013-09-16 14:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-13 16:46 RFC: Bug 60749 - Do not need to link against -lm for fabs*() walter harms
     [not found] ` <5233415A.90506-fPG8STNUNVg@public.gmane.org>
2013-09-13 18:20   ` Michael Kerrisk (man-pages)
     [not found]     ` <CAKgNAkiy54SbGEt6KQ2a87SQejoyuzcTvDbVK8aAQXd==yNNvg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-14 12:05       ` walter harms
     [not found]         ` <5234511C.7030500-fPG8STNUNVg@public.gmane.org>
2013-09-16 14:57           ` walter harms [this message]
     [not found]             ` <52371C48.7040404-fPG8STNUNVg@public.gmane.org>
2014-03-10 13:25               ` Michael Kerrisk (man-pages)

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=52371C48.7040404@bfs.de \
    --to=wharms-fpg8stnunvg@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).