From: Brendan Simon <brendan@dgs.monash.edu.au>
To: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>,
linuxppc-user <linuxppc-user@lists.linuxppc.org>
Subject: LinuxPPC: couldn't donwload glibc sources.
Date: Mon, 19 Apr 1999 01:03:45 +0000 [thread overview]
Message-ID: <371A80F0.B04E9947@dgs.monash.edu.au> (raw)
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
Brendan Simon.
[[ 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 reply other threads:[~1999-04-19 1:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-19 1:03 Brendan Simon [this message]
1999-04-19 10:32 ` LinuxPPC: couldn't donwload glibc sources Joel Klecker
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=371A80F0.B04E9947@dgs.monash.edu.au \
--to=brendan@dgs.monash.edu.au \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-user@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 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).