From: Simone Piccardi <Simone.Piccardi@fi.infn.it>
To: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: LinuxPPC: couldn't donwload glibc sources.
Date: Mon, 19 Apr 1999 14:22:47 +0200 [thread overview]
Message-ID: <371B2017.92A34955@fi.infn.it> (raw)
Last week I downlaod these:
glibc-2_0_112_tar.gz
glibc-crypt-2_0_96_tar.gz
glibc-linuxthreads-2_0_112_tar.gz
but I'm not still using these. I also download the source rpm for
glibc-2.1.
I would like to know what is better to use.
Bye
--
Simone Piccardi
Microsoft is NOT the answer. Microsoft is the Question.
The answer is: "NO!"
[[ 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 12:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-19 12:22 Simone Piccardi [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-04-19 1:03 LinuxPPC: couldn't donwload glibc sources Brendan Simon
1999-04-19 10:32 ` Joel Klecker
1999-04-19 16:46 ` Matt Porter
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=371B2017.92A34955@fi.infn.it \
--to=simone.piccardi@fi.infn.it \
--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 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).