From: "Rupert Wood" <me@rupey.net>
To: "'Mark Williams \(MWP\)'" <mwp@internode.on.net>
Cc: <gcc-help@gcc.gnu.org>, "'Ian Lance Taylor'" <ian@airs.com>
Subject: RE: CVS checkout
Date: Thu, 21 Jul 2005 16:39:00 -0000 [thread overview]
Message-ID: <ORCAU6xfPTeip68V8zD00000974@softwire.co.uk> (raw)
In-Reply-To: <20050721150552.GA29161@linux.comp>
Mark Williams wrote:
> > That is the right CVS tag. That should have given you the 4.0
> > branch sources. I don't know why it didn't work. What do you
> > see in gcc/version.c?
>
> const char version_string[] = BASEVER DATESTAMP DEVPHASE VERSUFFIX;
>
> Where ive found BASEVER to be "4.1.0".
>
> There has to be somthing ive done wrong...
Hmm, your command works for me, sorry. In the top level directory, you could
try
contrib/gcc_update -rgcc-4_0-branch
and see what happens? Fingers crossed that'll update all your tree to the
4.0 branch.
Rup.
next prev parent reply other threads:[~2005-07-21 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 7:16 Mark Williams (MWP)
2005-07-21 7:33 ` Ian Lance Taylor
2005-07-21 15:07 ` Mark Williams (MWP)
2005-07-21 16:39 ` Rupert Wood [this message]
2005-07-21 19:05 ` 'Mark Williams (MWP)'
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=ORCAU6xfPTeip68V8zD00000974@softwire.co.uk \
--to=me@rupey.net \
--cc=gcc-help@gcc.gnu.org \
--cc=ian@airs.com \
--cc=mwp@internode.on.net \
/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).