All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: alan@lxorguk.ukuu.org.uk (Alan Cox)
To: ralf@lappi.waldorf-gmbh.de
Cc: alan@lxorguk.ukuu.org.uk, linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr
Subject: Re: Libc in CVS
Date: Mon, 24 Nov 1997 14:09:12 +0000 (GMT)	[thread overview]
Message-ID: <m0xZzCL-0005FsC@lightning.swansea.linux.org.uk> (raw)
In-Reply-To: <19971124141804.17724@lappi.waldorf-gmbh.de> from "ralf@lappi.waldorf-gmbh.de" at Nov 24, 97 02:18:04 pm

> For rpm the trick is easy, just don't use a static linked binary.
> Unfortunately the Redhat guys seem to think static binaries are a good
> idea and install a static rpm by default.  Which it is not, not even
> without a buggy dynamic linker.

Static rpm 2.4.8 +fixes works
Dynamic 2.4.8 crashes on startup every time

> Ok.  I stopped communicating with the Redhat guys shortly before I left the
> US.  Essentially they received a part of the patches that I don't classify
> as ugly hacks or work in progress.

No problem

> Some more packages like the binutils, gcc or libc are based on different
> versions and we should try to base our work on the same versions as Redhat
> does.

Right now Ive got chunks of bastardised 4.8 (eg with -O not -O2 to avoid
gcc blowing up on zsh) but hopefully I can knock those out over time

  reply	other threads:[~1997-11-24 14:17 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
1997-11-24 13:18       ` ralf
1997-11-24 14:09         ` Alan Cox [this message]
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=m0xZzCL-0005FsC@lightning.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-mips@fnet.fr \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=ralf@lappi.waldorf-gmbh.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.