[PATCH 4 of 7] cc/gcc: Add support for getting a gcc snapshot

[Arnaud Lacombe]

Hi,

On Tue, Dec 7, 2010 at 1:29 PM, Bryan Hundven <bryanhundven@gmail.com> wrote:
> On Tue, Dec 7, 2010 at 7:19 AM, Arnaud Lacombe <lacombar@gmail.com> wrote:
>> Hi,
>>
>> I had the same in my tree! You may want to have a look, in particular
>> for the download section, which require some other change in the
>> downloader utility cruft.
>>
>>  - Arnaud
>
> Interesting. Thanks Arnaud!
>
> Not saying that I don't like your patch, it is just a different way of
> doing things.
> The way that I had incorporated snapshots has no changes to gcc.sh.
> The thing that your patch is missing (maybe it is in a separate patch)
> is the "real gcc version" (I called it CT_CC_REAL_VERSION), which is
> needed during the finalize step in scripts/build/internals.sh.
>
> Even better then snapshot support, would be the ability to
> checkout/export gcc from svn from a specific branch/revision, much
> like eglibc.
this can be trivially done with git. I still have patches, but I'm no
longer using ct-ng, so I don't really care about them now. This is a
reason why I do not want people to only contribute patches to ct-ng.

> Binutils is a bit more different. They make a versioned snapshot
> (binutils-2.21.51.tar.bz2), a daily snapshot (binutils.tar.gz), and a
> weekly snapshot (binutils.weekly.tar.bz2).
> But they all currently extract to 'binutils-2.21.51'. Because the name
> of the archive is different then where the archive is extracted, it is
> tempting for me to modify CT_Extract() to support these kind of
> snapshot archives by basically running:
>
binutils has a git tree too.

> So that all binutils snapshots live in ${CT_SRC_DIR}/binutils-snapshots
>
> It's good to know that we have some things in common ;)
>
well, that was fun hacking around it, but ct-ng has too many
limitation and architectural defect which cannot be easily
worked-around. Maybe I should put my git repo online a day or another.

 - Arnaud

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