Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Ian Chilton <ian@ichilton.co.uk>,
	linux-mips@oss.sgi.com, lfs-discuss@linuxfromscratch.org
Subject: Re: User/Group Problem
Date: Mon, 13 Nov 2000 23:19:49 +0100	[thread overview]
Message-ID: <20001113231949.B16012@bacchus.dhis.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1001113195048.12211C-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Mon, Nov 13, 2000 at 08:02:48PM +0100

On Mon, Nov 13, 2000 at 08:02:48PM +0100, Maciej W. Rozycki wrote:

> >  - your chown / chgrp binaries are statically linked.  In that case nss
> >    won't work on MIPS until it's fixed ...
> 
>  That's actually not a MIPS-specific problem.  This happens due to a bogus
> error from mmap() (when called by ld.so) which cannot handle certain valid
> requests -- when there is a non-zero suggested VM address, but the area
> and all space above it is already occupied or unavailable for other
> reasons.  It can sometimes appear for other ports, as well (I have an i386
> test case, for example), but it bites MIPS specifically, because of a
> non-zero initial VMA set for our shared objects.
> 
>  Here is a patch I use since July successfully.  We need to wait until
> 2.4.1 or so (or maybe even 2.5) is released for it to be applied as
> 2.4.0-test* are currently code-frozen.  Maybe we could apply it to our CVS
> for now?  Ralf, what do you think? 

There is second interpretation of this problem - the address passed to
mmap is bogus, so this computation needs to be fixed.

  Ralf

  parent reply	other threads:[~2000-11-13 22:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-07 11:06 User/Group Problem Ian Chilton
2000-11-08  4:01 ` Ralf Baechle
2000-11-13 19:02   ` Maciej W. Rozycki
2000-11-13 20:02     ` Ian Chilton
2000-11-13 20:02       ` Ian Chilton
2000-11-13 22:19     ` Ralf Baechle [this message]
2000-11-14 14:19       ` Maciej W. Rozycki
2000-11-15  7:52         ` Ralf Baechle
2000-11-16 12:13           ` Maciej W. Rozycki

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=20001113231949.B16012@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=ian@ichilton.co.uk \
    --cc=lfs-discuss@linuxfromscratch.org \
    --cc=linux-mips@oss.sgi.com \
    --cc=macro@ds2.pg.gda.pl \
    /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