From: alan@lxorguk.ukuu.org.uk (Alan Cox)
To: ralf@uni-koblenz.de
Cc: alan@lxorguk.ukuu.org.uk, linux@cthulhu.engr.sgi.com
Subject: Re: Libc in CVS
Date: Mon, 24 Nov 1997 11:30:41 +0000 (GMT) [thread overview]
Message-ID: <m0xZwiw-0005FsC@lightning.swansea.linux.org.uk> (raw)
In-Reply-To: <19971124120549.01585@lappi.waldorf-gmbh.de> from "ralf@uni-koblenz.de" at Nov 24, 97 12:05:49 pm
> > With luck it'll also fix the rpm-2.4.8 core dump bug which seems to be
> > bad linking.
>
> My rpm has never dumped core but it was complaining about nonexisting
> users while creating the binary rpm file even though the user was
> existing thus failing to build. That rpm problem is fixed.
Yep thats the bug - I also got some crashes. It was caused by getpw* failing
in peculiar ways. My RPM binary has its own
> All the source RPM packages on linus are known to build and work for
> little endian targets. Some of them, for example ncompress, have special
> modifications to support big endian targets.
Im actually trying to build a full RedHat 5.0 by early December so Im picking
up your changes to stuff like bash indirectly via redhat on the whole. I can
then merge anything that escaped and together we can make sure they are in
RH5.1.
Obviously as of about Dec1 the amount of answers I can get from RedHat will
noise dive for a couple of months
Alan
next prev parent reply other threads:[~1997-11-24 11:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-24 4:41 Libc in CVS ralf
1997-11-24 9:46 ` Alan Cox
1997-11-24 11:05 ` ralf
1997-11-24 11:30 ` Alan Cox [this message]
1997-11-24 13:18 ` ralf
1997-11-24 14:09 ` Alan Cox
1997-11-24 15:55 ` Erik Troan
1997-11-24 17:16 ` ralf
1997-11-24 21:35 ` David S. Miller
1997-11-24 21:58 ` Erik Troan
1997-11-24 23:22 ` ralf
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=m0xZwiw-0005FsC@lightning.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux@cthulhu.engr.sgi.com \
--cc=ralf@uni-koblenz.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