From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: R Shapiro <reshapiro@mediaone.net>, linuxppc-dev@lists.linuxppc.org
Subject: Re: current recommended versions of glibc/egcs/binutils for R5?
Date: Sun, 1 Aug 1999 15:58:53 +0200 [thread overview]
Message-ID: <99080116025601.00416@ns1102.munich.netsurf.de> (raw)
In-Reply-To: <14244.17697.552036.29509@ipa.ne.mediaone.net>
Am Son, 01 Aug 1999 schrieb R Shapiro:
>What are the currently recommended *stable* versions of glibc, egcs
>and binutils in R5? Should I stick with the installed versions:
>
> glibc 2.1.1-6c, egcs 1.1.2-12c, binutils 2.9.1.0.990418-1c
>
>or use the newer versions available on linuxppc.org:
>
> glibc 2.1.2-1a, egcs 1.1.2-12f, binutils-2.9.4.0.8-1a
I consider the newer versions stable and told the distribution maintainers
about it.
Franz.
[[ 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. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-08-01 13:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-01 13:01 current recommended versions of glibc/egcs/binutils for R5? R Shapiro
1999-08-01 13:58 ` Franz Sirl [this message]
1999-08-01 18:38 ` gdb broken under linuxppc r5 tools Kevin B. Hendricks
1999-08-01 19:03 ` Franz Sirl
1999-08-01 20:12 ` kbhend
1999-08-01 20:24 ` Kevin Buettner
1999-08-01 20:54 ` Franz Sirl
1999-08-02 11:20 ` Gary Thomas
1999-08-02 15:21 ` kbhend
1999-08-02 15:50 ` Daniel Jacobowitz
1999-08-02 16:01 ` kbhend
1999-08-22 15:09 ` bug in glibc 2.1.2 new semaphore functions in libpthread? Kevin Hendricks
1999-08-24 21:09 ` Franz Sirl
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=99080116025601.00416@ns1102.munich.netsurf.de \
--to=franz.sirl-kernel@lauterbach.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=reshapiro@mediaone.net \
/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.