From: "T. P. Saravanan" <sara@procsys.com>
To: linux-mips@linux-mips.org
Subject: Re: libc, libc-devel in CVS
Date: Thu, 07 Oct 2004 09:49:51 +0530 [thread overview]
Message-ID: <4164C3E7.5070609@procsys.com> (raw)
In-Reply-To: <416242DE.5010806@procsys.com>
T. P. Saravanan wrote:
>
> Hi,
>
> In the CVS (http://www.linux-mips.org/cvsweb/) I find two directories
> - libc and
> libc-devel. Can somebody roughly describe - why are there two, and
> what is the
> difference?
>
> If I need a stable (and reasonably recent) libc which one should I use?
> (Or should I use the glibc kept in ftp.gnu.org?)
>
> -Saravanan
>
>
Please correct me if I am wrong.
(This is just for the record and for the benefit of the late comers.)
When people say glibc CVS they mean the one at
http://sources.redhat.com/glibc/
and http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/?cvsroot=glibc.
[Not the one at http://www.linux-mips.org/cvsweb/].
-Sa.
next prev parent reply other threads:[~2004-10-07 4:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 6:44 libc, libc-devel in CVS T. P. Saravanan
2004-10-07 4:19 ` T. P. Saravanan [this message]
2004-10-07 13:18 ` Maciej W. Rozycki
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=4164C3E7.5070609@procsys.com \
--to=sara@procsys.com \
--cc=linux-mips@linux-mips.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