Hi Michael,
On Sun, 2015-01-04 20:20:40 +0100, Michael Haubenwallner
wrote:
> (CC'ing build machinery maintainers, maybe I should have done this initially)
Good point, that's my oversight and I'm quite undecided what to do.
> Am 2014-12-31 um 11:45 schrieb Janne Blomqvist:
> > On Fri, Dec 19,
ping
As trunk is in stage 4, is there some accepted custom to re-run all the third
party
generators, to avoid different versions of generated code across the final
release?
Thanks!
/haubi/
On 01/04/2015 08:20 PM, Michael Haubenwallner wrote:
> (CC'ing build machinery maintainers, maybe I shoul
(CC'ing build machinery maintainers, maybe I should have done this initially)
Am 2014-12-31 um 11:45 schrieb Janne Blomqvist:
> On Fri, Dec 19, 2014 at 2:56 PM, Michael Haubenwallner
> wrote:
>> On the way to prepare some (aix) libtool patch for toplevel libtool.m4
>> I've discovered that differe
On Fri, Dec 19, 2014 at 2:56 PM, Michael Haubenwallner
wrote:
> On the way to prepare some (aix) libtool patch for toplevel libtool.m4
> I've discovered that different versions of automake were used to generate
> files across various libs:
>
> most libs: automake-1.11.1
> libatomic r21
Hi Michael and Jan-Benedict,
On Fri, 19 Dec 2014 13:56:50, Michael Haubenwallner wrote:
> On the way to prepare some (aix) libtool patch for toplevel libtool.m4
> I've discovered that different versions of automake were used to generate
> files across various libs:
>
> most libs: automa
On the way to prepare some (aix) libtool patch for toplevel libtool.m4
I've discovered that different versions of automake were used to generate
files across various libs:
most libs: automake-1.11.1
libatomic r211747: automake-1.11.6
libgfortran r204654: automake-1.11.3
r21
