Re: [CT-NG] WIP - status

[Bryan Hundven <bryanhundven at gmail dot com>]

On Thu, Jan 20, 2011 at 10:25 AM, Yann E. MORIN
<yann.morin.1998@anciens.enib.fr> wrote:
> Bryan, All,
>
> On Thursday 20 January 2011 01:30:03 Bryan Hundven wrote:
>> Maybe try glibc 2.13, wrt IA-64?
>
> Fact is, the webpage for glibc still mentions 2.11.2 as the latest version
> officially released version. How on earth is one supposed to know that a
> new version gets released if the project's page is not updated? Or maybe
> this page is not the official one: http://www.gnu.org/software/libc/
> Drepper-land is a very strange place to wander in. Sigh...
>
>> Would it also be useful to be able to get glibc (and glibc-ports) from
>> git as well as from tarballs? I noticed that some versions of glibc
>> did not release tarballs for libc, and ports.
>
> Well... The purpose of released tarballs is just that: to put out
> _releases_. Of course we could use the git tree, but really this makes
> it more complicated than it should be... :-(

_releases_ make sense. In my opinion, crosstool-ng should not just be
for creating stable toolchains from releases, but it should also be
usable for toolchain component development/testing as well. Released
versions of the toolchain components should be the default behavior.
I think that being able to configure snapshots or directly from the
official vcs would be the use-cases for developers/testers of any of
the components that make up the toolchain.

When I get around to re-doing the gcc/binutils snapshots feature,
maybe I'll also add snapshots for glibc.
(granted, glibc also doesn't post snapshots of the repository...
*double sigh*, but I would consider a git tag/revision/date as a
snapshot.)

What might also make sense before re-doing the snapshot feature, is to
consolidate and/or fuctionalize checking-out/exporting source from a
version control system into '<vcs>_{checkout,export}' function (or
something similar) so that adding the snapshot feature will be cleaner
and simpler. Just a thought... I'm curious to know your thoughts on
this.

>> It's also easy to export git to a tarball:
>> git archive --format=tar --prefix=glibc-<version>/
>> {revision|branch+revision|HEAD} | bzip2 > glibc-<version>.tar.bz2
>
> The issue is not how to use a specific tag/branch/changeset from git,
> but rather how to properly integrate it in the downlad process...
>
> If we were to use the git tree as source, then there is no point in
> usign tarballs at all. What I envision is:
> Â- check if git tree is already downlaoded
> Â - if not, then clone it
> Â - move to local source dir
> Â- clone the local tree to the working dir
> Â- check out appropriate tag
>
> There is already some git-handling code in crosstool-NG, but I did not
> have the time/willingness to pursue this for now. I'll look into that
> after the next release...
>
>> I'll give both glibc and eglibc a shot tonight on
>> armeb-xscale-linux-gnueabi, powerpc-e500v2-linux-gnuspe, and
>> x86-nptl-linux-gnu tonight.
>
> Thank you! :-)
>
>> I noticed that with x86_64-nptl-linux-gnu, gdb-7.2 is not building...
>> I'll send an email about this later, when I test the above stuff.
>
> Good, thanks.
>
> Regards,
> Yann E. MORIN.
>
> --
> .-----------------.--------------------.------------------.--------------------.
> | ÂYann E. MORIN Â| Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
> | +33 662 376 056 | Software ÂDesigner | \ / CAMPAIGN Â Â | Â___ Â Â Â Â Â Â Â |
> | +33 223 225 172 `------------.-------: ÂX ÂAGAINST Â Â Â| Â\e/ ÂThere is no Â|
> | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL  Â|  v  conspiracy. Â|
> '------------------------------^-------^------------------^--------------------'
>

-Bryan

--
For unsubscribe information see http://sourceware.org/lists.html#faq