linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Kukuk <kukuk@suse.de>
To: linuxppc-dev@lists.linuxppc.org
Subject: new RLIM_INFINITY and binary compatiblity
Date: Wed, 15 Dec 1999 13:37:22 +0100	[thread overview]
Message-ID: <19991215133722.A16123@allen.suse.de> (raw)



Hi,

In the current kernels, RLIM_INFINITY has changed from signed long
to unsigned long. In the moment this is not the big problem, because
glibc has it's own definition of RLIM_INFINITY.

Now Uli Drepper has made this changes to glibc, too. The problem:
binaries, which are compiled with the new, bigger RLIM_INFINITY
doesn't work correct on old kernels.
My question is: What is planed for the PowerPC port ?

There are 3 possible solutions:
1. The problem will be ignored, and the people have to use a new
   kernel if glibc 2.1.3/2.2 is available (This is the current
   solution for SPARC64)

2. The RLIM_INFINITY will be changed back to the old value
   (This is the solution for ALPHA)

3. linuxppc becomes also the ugetrlimit syscall like Intel has.

I don't know what is planned for the PPC linux kernel, all 3
solutions are possible and easy to solve for me with glibc.
I would prefer 3, because then we have the SUS compatible
RLIM_INFINITY.

Comments ? I would like to fix the current glibc snapshots, so they
build again on other Platforms then Intel (In the moment it could
only be build on Intel correct). So I need an answer.

  Thorsten

-- 
Thorsten Kukuk       http://www.suse.de/~kukuk/       kukuk@suse.de
SuSE GmbH            Schanzaeckerstr. 10            90443 Nuernberg
Linux is like a Vorlon.  It is incredibly powerful, gives terse,
cryptic answers and has a lot of things going on in the background.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

                 reply	other threads:[~1999-12-15 12:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=19991215133722.A16123@allen.suse.de \
    --to=kukuk@suse.de \
    --cc=linuxppc-dev@lists.linuxppc.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).