public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: ndronen@io.frii.com (Nicholas Dronen)
To: help-gcc@gnu.org
Subject: Re: Can't link ddd under x86
Date: Fri, 31 Dec 1999 22:24:00 -0000	[thread overview]
Message-ID: <BaC54.214$G3.171246592@news.frii.net> (raw)
Message-ID: <19991231222400.KkSThjX5ZwNZUZh-C-Sa5I3znBCfXQAPMG2J2MgMFx0@z> (raw)
In-Reply-To: <836lhv$u3e$1@nnrp1.deja.com>

Stephen Rasku (stephen@tgivan.com) wrote:
: I am trying to compile ddd 3.1.6 on Solaris 7 (x86).  At link time, I
: get the following error:

: ld: fatal: file /dev/zero: cannot mmap file: Resource temporarily
: unavailable

: I am using gcc 2.8.1 and I had no problems compiling on Sparc using the
: same version of the compiler.  Any idea as how to fix this?

From /usr/include/sys/errno.h.

#define EAGAIN  11  /* Resource temporarily unavailable */

From the man page for mmap(2).

EAGAIN	The mapping could not be locked in memory.

	   	There was insufficient room to reserve swap  space
	    for the mapping.

	    The file to be  mapped  is  already  locked  using
	    advisory   or   mandatory   record   locking.  See
	    fcntl(2).

It looks like you're either running sorely short of 
memory (unless this documentation is out of date
with respect to Solaris's paging algorithms) or
someone else has locked the file.

Regards,

Nicholas

  reply	other threads:[~1999-12-31 22:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-14 16:11 Stephen Rasku
1999-12-14 17:32 ` Nicholas Dronen [this message]
1999-12-31 22:24   ` Nicholas Dronen
1999-12-15  2:53 ` achetroi
1999-12-17 11:53   ` Stephen Rasku
1999-12-31 22:24     ` Stephen Rasku
1999-12-31 22:24   ` achetroi
1999-12-31 22:24 ` Stephen Rasku

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='BaC54.214$G3.171246592@news.frii.net' \
    --to=ndronen@io.frii.com \
    --cc=help-gcc@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).