From: Nick Clifton <nickc@redhat.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: binutils@sourceware.org
Subject: Re: 2.40 branch now open for updates
Date: Tue, 17 Jan 2023 12:04:22 +0000 [thread overview]
Message-ID: <971ade5c-e496-5fd9-3652-afa36e6280b0@redhat.com> (raw)
In-Reply-To: <fda8cc98-675-eb89-c8b3-3b3f38db3a@codesourcery.com>
Hi Joseph,
> It looks like version numbers aren't consistently set on the branch at
> present; building from it I get errors of the form:
>
> In file included from /scratch/jmyers/glibc/many12/src/binutils/gprof/gprof.h:41,
> from /scratch/jmyers/glibc/many12/src/binutils/gprof/basic_blocks.c:24:
> ./gconfig.h:104: error: "VERSION" redefined [-Werror]
> 104 | #define VERSION "2.40.00"
> |
> In file included from /scratch/jmyers/glibc/many12/src/binutils/gprof/../bfd/sysdep.h:29,
> from /scratch/jmyers/glibc/many12/src/binutils/gprof/gprof.h:33,
> from /scratch/jmyers/glibc/many12/src/binutils/gprof/basic_blocks.c:24:
> ../bfd/config.h:327: note: this is the location of the previous definition
> 327 | #define VERSION "2.40"
>
*sigh* Yes you are right. I had a snafu when I was creating the release
tarballs and accidentally set the version number to 2.40.00 instead of 2.40.
I thought that I had fixed all of the files before making the release, but
obviously I missed a few. This should now be fixed.
Cheers
Nick
next prev parent reply other threads:[~2023-01-17 12:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 15:35 Nick Clifton
2023-01-16 19:11 ` Joseph Myers
2023-01-17 12:04 ` Nick Clifton [this message]
2023-01-24 20:47 ` Vladimir Mezentsev
2023-01-25 11:26 ` Nick Clifton
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=971ade5c-e496-5fd9-3652-afa36e6280b0@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=joseph@codesourcery.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).