public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Matthias Klose <doko@ubuntu.com>
To: GCJ-patches <java-patches@gcc.gnu.org>,
	       "gcc-patches@gnu.org" <gcc-patches@gnu.org>
Subject: [patch] [java] bump libgcj soname
Date: Tue, 21 Apr 2015 14:07:00 -0000	[thread overview]
Message-ID: <55365991.4030806@ubuntu.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 140 bytes --]

bump the libgcj soname on the trunk, as done for every release cycle, and update
the cygwin/mingw32 files.

ok for the trunk?

  Matthias



[-- Attachment #2: gcjversion.diff --]
[-- Type: text/x-patch, Size: 1591 bytes --]

gcc/

2015-04-21  Matthias Klose  <doko@ubuntu.com>

	* config/i386/cygwin.h (LIBGCJ_SONAME): Set libgcj version to -17.
	* config/i386/mingw32.h (LIBGCJ_SONAME): Set libgcj version to -17.

libjava/

2015-04-21  Matthias Klose  <doko@ubuntu.com>

	* libtool-version: Bump soversion.

Index: gcc/config/i386/cygwin.h
===================================================================
--- gcc/config/i386/cygwin.h	(revision 222268)
+++ gcc/config/i386/cygwin.h	(working copy)
@@ -154,5 +154,5 @@
 #define LIBGCC_SONAME "cyggcc_s" LIBGCC_EH_EXTN "-1.dll"
 
 /* We should find a way to not have to update this manually.  */
-#define LIBGCJ_SONAME "cyggcj" /*LIBGCC_EH_EXTN*/ "-16.dll"
+#define LIBGCJ_SONAME "cyggcj" /*LIBGCC_EH_EXTN*/ "-17.dll"
 
Index: gcc/config/i386/mingw32.h
===================================================================
--- gcc/config/i386/mingw32.h	(revision 222268)
+++ gcc/config/i386/mingw32.h	(working copy)
@@ -254,4 +254,4 @@
 #define LIBGCC_SONAME "libgcc_s" LIBGCC_EH_EXTN "-1.dll"
 
 /* We should find a way to not have to update this manually.  */
-#define LIBGCJ_SONAME "libgcj" /*LIBGCC_EH_EXTN*/ "-16.dll"
+#define LIBGCJ_SONAME "libgcj" /*LIBGCC_EH_EXTN*/ "-17.dll"
Index: libjava/libtool-version
===================================================================
--- libjava/libtool-version	(revision 222268)
+++ libjava/libtool-version	(working copy)
@@ -5,4 +5,4 @@
 # Note: When changing the version here, please do also update LIBGCJ_SONAME
 # in gcc/config/i386/cygwin.h and gcc/config/i386/mingw32.h.
 # CURRENT:REVISION:AGE
-16:0:0
+17:0:0

             reply	other threads:[~2015-04-21 14:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21 14:07 Matthias Klose [this message]
2015-04-21 14:11 ` Jakub Jelinek
2015-04-21 14:16   ` Matthias Klose
2015-04-21 14:19     ` Jakub Jelinek
2015-04-21 14:29       ` Matthias Klose
2015-04-21 14:37         ` Jakub Jelinek
2016-01-02 14:40           ` Matthias Klose
2016-01-02 15:40             ` Andrew Haley
2016-01-02 15:53               ` Matthias Klose
2016-01-02 16:11                 ` Andrew Haley
2016-01-03 11:38                   ` Matthias Klose
2016-01-03 14:17                     ` Andrew Haley
2016-01-03 15:52                       ` Matthias Klose
2016-01-03 16:23                         ` Andrew Haley
2016-01-03 17:34                           ` Matthias Klose
2016-01-03 19:04                             ` Mike Stump
2016-01-03 22:14                               ` Matthias Klose
2015-04-21 17:04   ` Andrew Hughes
2015-04-21 17:10     ` Jakub Jelinek
2015-04-21 17:17       ` Andrew Hughes

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=55365991.4030806@ubuntu.com \
    --to=doko@ubuntu.com \
    --cc=gcc-patches@gnu.org \
    --cc=java-patches@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: 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).