From: Thorsten Kukuk <kukuk@suse.de>
To: Ulrich Drepper <drepper@cygnus.com>
Cc: Andreas Schwab <schwab@suse.de>, libc-hacker@sourceware.cygnus.com
Subject: Re: rlimit changes
Date: Fri, 10 Dec 1999 13:20:00 -0000 [thread overview]
Message-ID: <19991210222007.A30638@Wotan.suse.de> (raw)
In-Reply-To: <m3k8mmisl2.fsf@localhost.localnet>
On Fri, Dec 10, Ulrich Drepper wrote:
> Thorsten Kukuk <kukuk@suse.de> writes:
>
> > You make a change which breaks the ABI for all platforms for over
> > 2 weeks. We fixed it for all platforms.
>
> Wrong. I told you three times already: it didn't even compile on
> Alpha.
Yes, and I told you that I have no problems. I have compiled yet
the glibc 2.1.3 CVS snapshot from yesterday with the missing patches
from Andreas Schwab (which are only in 2.2) on a SuSE Linux 6.3/Alpha.
It compiles, it works. So we should try to find out what exactly
the problem is and what the reason it that it fails for you.
> It is not possible to fix the Alpha problems without removing the
> generic stuff. Try it out before complaining. On Alpha you get
> double definitions of the functions because they are picked up in misc
> and in resource.
As I told you already, I have tried it out before complaining.
The resulting version works, and I get no warnings or errors.
Where you write your problem now, I have looked at the log file.
You are right, oldgetrlimit64.os and oldsetrlimit64.os are included
twice, from misc and from resource. But the linker is not complaining
that he has 2 identical object files, he only use it once. So it
works for me and I had no chance to see it until yet.
I think this really shouldn't be so hard to fix, but I'm not a
Makefile expert. And I think there is something other wrong if
rlimit functions are included in misc and in resource.
> If SuSE wants to make a release, go on, use the old code. It's simply
> not correct on all platforms.
SuSE will never use CVS snapshots for the release, we only adds important
bug fixes to a public relase, where we are sure that this patches will
not break anything else. Snapshots makes to much trouble, as you never
know if they will not break the ABI or something else. And as you could
read everywhere, we released our new version already. This is the reason
why Andreas S. and I have now the time to get the current CVS version
working before glibc 2.1.3 will be released public.
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.
next prev parent reply other threads:[~1999-12-10 13:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-09 11:32 Ulrich Drepper
1999-12-10 1:01 ` Andreas Schwab
1999-12-10 7:15 ` Ulrich Drepper
1999-12-10 7:26 ` Andreas Schwab
1999-12-10 7:28 ` Thorsten Kukuk
1999-12-10 7:40 ` Ulrich Drepper
1999-12-10 7:56 ` Andreas Schwab
1999-12-10 8:08 ` Ulrich Drepper
1999-12-10 8:17 ` Andreas Schwab
1999-12-10 8:28 ` Ulrich Drepper
1999-12-10 8:35 ` Andreas Schwab
1999-12-10 8:41 ` Ulrich Drepper
1999-12-10 8:49 ` Andreas Schwab
1999-12-10 9:01 ` Ulrich Drepper
1999-12-10 9:34 ` Thorsten Kukuk
1999-12-10 10:03 ` Ulrich Drepper
1999-12-10 13:20 ` Thorsten Kukuk [this message]
1999-12-13 1:25 ` Andreas Schwab
1999-12-13 1:38 ` Jakub Jelinek
1999-12-13 2:54 ` Andreas Schwab
1999-12-10 9:26 ` Thorsten Kukuk
1999-12-10 8:13 ` Jakub Jelinek
1999-12-13 11:35 ` Ralf Baechle
1999-12-13 11:40 ` Andreas Schwab
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=19991210222007.A30638@Wotan.suse.de \
--to=kukuk@suse.de \
--cc=drepper@cygnus.com \
--cc=libc-hacker@sourceware.cygnus.com \
--cc=schwab@suse.de \
/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).