public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: "Aaron J. Grier" <aaron@frye.com>
To: Stephane Dalton <Stephane.Dalton@abl.ca>
Cc: crossgcc@sourceware.cygnus.com
Subject: Re: sbrk undefined symbol
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <20000221112508.A21117@aaron.fryebox.com> (raw)
In-Reply-To: <C5B7AD50B789D31191B400805F9F52CB17C501@exchange1.abl.ca>

On Mon, Feb 21, 2000 at 01:58:52PM -0500, Stephane Dalton wrote:

> Today I've added a #include <assert.h> inside on of the file and now
> at link time I got these error messages:

[undefined references to abort, _exit, sbrk, kill, and getpid]

> I've encountered this kind of error before (for different type of
> function) and the FAQ simply told to stub out these. Should I do the
> same here. I'm a bit worry to see sbrk here because as far as I know
> it is used for memory allocation???

assert() as defined in newlib depends on all these functions.  You can
find stubs in libgloss.  You'll need to link these in for assert to
work.

-- 
  Aaron J. Grier   |   Frye Electronics, Tigard, OR   |   aaron@frye.com
  "The simplistic anthropomorphism which asserts that source code has a
   life separate from its creator or maintainer is the product of one
   too many viewings of Tron."  -- paraphrasing of anonymous post on /.

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

      parent reply	other threads:[~2000-04-01  0:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-01  0:00 Stephane Dalton
2000-04-01  0:00 ` Doug Evans
2000-04-01  0:00 ` Aaron J. Grier [this message]

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=20000221112508.A21117@aaron.fryebox.com \
    --to=aaron@frye.com \
    --cc=Stephane.Dalton@abl.ca \
    --cc=crossgcc@sourceware.cygnus.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).