public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: Tulio Magno Quites Machado Filho <tuliom@linux.vnet.ibm.com>,
	j serralheiro <mrserra@yahoo.com>,
	libc-ports@sourceware.org
Subject: Re: Glibc 2.3.90 Where can I find source?
Date: Mon, 23 Jan 2017 18:51:00 -0000	[thread overview]
Message-ID: <9b5cddd7-5f6e-ce13-f482-abc6c87a1438@redhat.com> (raw)
In-Reply-To: <87d1fdj3z4.fsf@linux.vnet.ibm.com>

On 01/23/2017 08:33 AM, Tulio Magno Quites Machado Filho wrote:
> j serralheiro via libc-ports <libc-ports@sourceware.org> writes:
> 
>> The glibc library installed by distribution familiar is glib 2.3.90.
>> The kernel is 2.6.16
>>
>> Up until now I compiled a cross-compiler and compiled a @hello@ program. I linked this program statically with glib 2.10 that I also compiled.
>> In this case the kernel headers are from 2.6.21 that I downloaded from github or something, a merge of handhelds and hackndev.
>> I searched and I cannot find source for glibc2.3.90 source code.
> 
> As far as I know, glibc never had an official 2.3.90 release.  This version
> seems to come from a Linux distribution.
> 
> Fedora uses the same version scheme, e.g.:
> http://pkgs.fedoraproject.org/cgit/rpms/glibc.git/tag/?h=glibc-2_3_90-39

Right.

And even then Fedora just follows upstream glibc's version for Rawhide (rolling
release).

There is no such thing as a 2.3.90 release, the ".90" denotes that the sources
came from the development branch _after_ glibc 2.3 was released.

So a version of 2.3.90 means that the sources where somewhere between 2.3 and
2.4 (before release).

-- 
Cheers,
Carlos.

      reply	other threads:[~2017-01-23 18:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <441720578.1199074.1485079270423.ref@mail.yahoo.com>
2017-01-22 10:01 ` j serralheiro via libc-ports
2017-01-23 13:33   ` Tulio Magno Quites Machado Filho
2017-01-23 18:51     ` Carlos O'Donell [this message]

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=9b5cddd7-5f6e-ce13-f482-abc6c87a1438@redhat.com \
    --to=carlos@redhat.com \
    --cc=libc-ports@sourceware.org \
    --cc=mrserra@yahoo.com \
    --cc=tuliom@linux.vnet.ibm.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).