This patch for mainline corresponds to the one I committed earlier on
the 4.7 branch. This sets a different version for libgo.so on mainline
going forward. Bootstrapped and ran Go testsuite on
x86_64-unknown-linux-gnu. Committed to mainline.
I actually committed this yesterday but forgot to pre
On Tue, Oct 23, 2012 at 9:59 AM, Jakub Jelinek wrote:
> On Tue, Oct 23, 2012 at 09:57:21AM -0700, Ian Lance Taylor wrote:
>> The problem is that I forgot to do that when the 4.7 branch was
>> created. So the 4.7 branch and the 4.6 branch were using the same
>> SONAME although they had completely
On Tue, Oct 23, 2012 at 09:57:21AM -0700, Ian Lance Taylor wrote:
> The problem is that I forgot to do that when the 4.7 branch was
> created. So the 4.7 branch and the 4.6 branch were using the same
> SONAME although they had completely different ABIs.
>
> That is, there is no ABI change on the
On Tue, Oct 23, 2012 at 9:27 AM, Jakub Jelinek wrote:
> On Tue, Oct 23, 2012 at 06:16:25PM +0200, Matthias Klose wrote:
>> On 23.10.2012 06:55, Ian Lance Taylor wrote:
>> > PR 54918 points out that libgo is not using version numbers as it
>> > should. At present none of libgo in 4.6, 4.7 and main
On Tue, Oct 23, 2012 at 06:16:25PM +0200, Matthias Klose wrote:
> On 23.10.2012 06:55, Ian Lance Taylor wrote:
> > PR 54918 points out that libgo is not using version numbers as it
> > should. At present none of libgo in 4.6, 4.7 and mainline are
> > compatible with each other. This patch to the
On 23.10.2012 06:55, Ian Lance Taylor wrote:
> PR 54918 points out that libgo is not using version numbers as it
> should. At present none of libgo in 4.6, 4.7 and mainline are
> compatible with each other. This patch to the 4.7 branch sets the
> version number for libgo there. Bootstrapped and
On Tue, Oct 23, 2012 at 12:37 AM, Jan Kratochvil
wrote:
>
> On Tue, 23 Oct 2012 06:55:01 +0200, Ian Lance Taylor wrote:
>> PR 54918 points out that libgo is not using version numbers as it
>> should. At present none of libgo in 4.6, 4.7 and mainline are
>> compatible with each other. This patch
Hello Ian,
On Tue, 23 Oct 2012 06:55:01 +0200, Ian Lance Taylor wrote:
> PR 54918 points out that libgo is not using version numbers as it
> should. At present none of libgo in 4.6, 4.7 and mainline are
> compatible with each other. This patch to the 4.7 branch sets the
> version number for libg
PR 54918 points out that libgo is not using version numbers as it
should. At present none of libgo in 4.6, 4.7 and mainline are
compatible with each other. This patch to the 4.7 branch sets the
version number for libgo there. Bootstrapped and ran Go testsuite on
x86_64-unknown-linux-gnu. Commit
