From: Elgin Lee <ehl@funghi.com>
To: thomassr@erols.com
Cc: Elgin Lee <ehl@funghi.com>,
LinuxPPC Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: EGCS 1.1.1 FYI
Date: Tue, 08 Dec 1998 21:22:54 -0800 [thread overview]
Message-ID: <199812090522.VAA02554@porcini.funghi.com> (raw)
In-Reply-To: Message from Tom Vier <nester@nester.dyn.ml.org> of "Tue, 08 Dec 1998 22:05:27 EST." <Pine.LNX.3.96.981208202419.4464D-100000@zero>
>>>>> In <Pine.LNX.3.96.981208202419.4464D-100000@zero>
>>>>> Tom Vier <nester@nester.dyn.ml.org> wrote:
> anyone know if egcs-1.1.1-1a.ppc.rpm from pre-R5 is patched?
I don't know, but I doubt it. You can check the SRPM to see. IIRC,
LinuxPPC pre-R5 is based on an egcs-1.1.1-compiled glibc 2.1, which
1. works fine with an unpatched egcs
2. would not work with a patched egcs
The patches are only for compatibility with the currently deployed
shared libraries.
--Elgin
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next parent reply other threads:[~1998-12-09 5:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <nester@nester.dyn.ml.org>
[not found] ` <Pine.LNX.3.96.981208202419.4464D-100000@zero>
1998-12-09 5:22 ` Elgin Lee [this message]
[not found] <schinder@pobox.com>
1998-12-08 2:51 ` EGCS 1.1.1 FYI Paul J. Schinder
1998-12-07 15:10 ` David Edelsohn
1998-12-07 22:22 ` Ralf Weidemann
1998-12-08 1:05 ` Michael Meissner
1998-12-08 6:17 ` Elgin Lee
1998-12-08 11:38 ` Gary Thomas
1998-12-08 4:28 ` hagopiar
1998-12-08 10:42 ` David T. McWherter
1998-12-08 6:59 ` Daniel Jacobowitz
1998-12-06 8:06 jeramy
1998-12-07 16:12 ` Michael Meissner
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=199812090522.VAA02554@porcini.funghi.com \
--to=ehl@funghi.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=thomassr@erols.com \
/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).