public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: mike stump <mrs@windriver.com>
To: gcc@gcc.gnu.org, nospam@mega-nerd.com
Subject: Re: lrint / lrintf functions
Date: Sat, 20 Oct 2001 20:08:00 -0000	[thread overview]
Message-ID: <200110210307.UAA09913@kankakee.wrs.com> (raw)

> Date: Sun, 21 Oct 2001 12:29:31 +1000
> From: Erik de Castro Lopo <nospam@mega-nerd.com>
> To: gcc@gcc.gnu.org

> I am currently using the above two C99 functions. If I turn off optimisation
> ( -O0) I get an error stating that the functions can't be found.

> Is this the fault of gcc, the C library of something else?

If a symbol that should be defined in your C library, isn't, then
usually it is a library problem.

             reply	other threads:[~2001-10-20 20:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-20 20:08 mike stump [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-20 19:29 Erik de Castro Lopo

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=200110210307.UAA09913@kankakee.wrs.com \
    --to=mrs@windriver.com \
    --cc=gcc@gcc.gnu.org \
    --cc=nospam@mega-nerd.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).