From: Joel Klecker <jk@espy.org>
To: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: LinuxPPC: couldn't donwload glibc sources.
Date: Mon, 19 Apr 1999 03:32:48 -0700 [thread overview]
Message-ID: <v04204e01b340b5cd8dfc@[206.163.71.146]> (raw)
In-Reply-To: <371A80F0.B04E9947@dgs.monash.edu.au>
At 01:03 +0000 1999-04-19, Brendan Simon wrote:
>I tried downloading the glibc sources as described on the cross-compiler
>page (http://members.home.com/mmporter/cross.html#LibC).
>
>Are following sites still valid ?
>
>ftp://alpha.gnu.org/gnu/glibc-2.0.106.tar.gz
>ftp://alpha.gnu.org/gnu/glibc-crypt-2.0.96.tar.gz
>ftp://alpha.gnu.org/gnu/glibc-linuxthreads-2.0.106.tar.gz
alpha.gnu.org is down, in any event those are old sources.
Try:
<ftp://sourceware.cygnus.com/pub/glibc/glibc-2.1.tar.gz>
<ftp://sourceware.cygnus.com/pub/glibc/glibc-linuxthreads-2.1.tar.gz>
<ftp://ftp.funet.fi/pub/gnu/funet/glibc-crypt-2.1.tar.gz>
--
Joel Klecker (aka Espy) Debian GNU/Linux Developer
<URL:mailto:jk@espy.org> <URL:mailto:espy@debian.org>
<URL:http://web.espy.org/> <URL:http://www.debian.org/>
[[ 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-04-19 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-19 1:03 LinuxPPC: couldn't donwload glibc sources Brendan Simon
1999-04-19 10:32 ` Joel Klecker [this message]
1999-04-19 16:46 ` Matt Porter
-- strict thread matches above, loose matches on Subject: below --
1999-04-19 12:22 Simone Piccardi
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='v04204e01b340b5cd8dfc@[206.163.71.146]' \
--to=jk@espy.org \
--cc=linuxppc-dev@lists.linuxppc.org \
/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.