public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-4624] libgo: bump major version Date: Mon, 12 Dec 2022 22:18:28 +0000 (GMT) [thread overview] Message-ID: <20221212221828.F04E038500AB@sourceware.org> (raw) https://gcc.gnu.org/g:11c72cd3c8b06f057ce16c95966331ded692fd4e commit r13-4624-g11c72cd3c8b06f057ce16c95966331ded692fd4e Author: Ian Lance Taylor <iant@golang.org> Date: Mon Dec 12 12:46:40 2022 -0800 libgo: bump major version PR go/108057 The current version is the same as for the previous GCC release, but there have been minor changes like new type descriptors that make it impossible to run Go programs built with the previous GCC release with the current libgo. Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/456976 Diff: --- gcc/go/gofrontend/MERGE | 2 +- libgo/configure | 2 +- libgo/configure.ac | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/gcc/go/gofrontend/MERGE b/gcc/go/gofrontend/MERGE index a26f779557d..d8c4e02d6e6 100644 --- a/gcc/go/gofrontend/MERGE +++ b/gcc/go/gofrontend/MERGE @@ -1,4 +1,4 @@ -1c5bfd57131b68b91d8400bb017f35d416f7aa7b +9906861dc86c1733bb304d3d45b1534adb32712c The first line of this file holds the git revision number of the last merge done from the gofrontend repository. diff --git a/libgo/configure b/libgo/configure index 61a49947eb9..460fdad70a8 100755 --- a/libgo/configure +++ b/libgo/configure @@ -2608,7 +2608,7 @@ ac_compiler_gnu=$ac_cv_c_compiler_gnu ac_config_headers="$ac_config_headers config.h" -libtool_VERSION=21:0:0 +libtool_VERSION=22:0:0 # Default to --enable-multilib diff --git a/libgo/configure.ac b/libgo/configure.ac index 274fcfc35c7..09554a37a23 100644 --- a/libgo/configure.ac +++ b/libgo/configure.ac @@ -10,7 +10,7 @@ AC_INIT(package-unused, version-unused,, libgo) AC_CONFIG_SRCDIR(Makefile.am) AC_CONFIG_HEADER(config.h) -libtool_VERSION=21:0:0 +libtool_VERSION=22:0:0 AC_SUBST(libtool_VERSION) AM_ENABLE_MULTILIB(, ..)
reply other threads:[~2022-12-12 22:18 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221212221828.F04E038500AB@sourceware.org \ --to=ian@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ /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: linkBe 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).