From: Marc - A. Dahlhaus [ Administration | Westermann GmbH ] <mad@wol.de>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Autotools version requirements to high on cluster master branch?
Date: Wed, 12 Aug 2009 13:40:49 +0200 [thread overview]
Message-ID: <1250077249.21656.21.camel@marc> (raw)
In-Reply-To: <1250075464.23947.9.camel@cerberus.int.fabbione.net>
Am Mittwoch, den 12.08.2009, 13:11 +0200 schrieb Fabio M. Di Nitto:
> On Wed, 2009-08-12 at 12:31 +0200, Marc - A. Dahlhaus [ Administration |
> Westermann GmbH ] wrote:
> > Hello,
> >
> >
> > it asks for libtool 2.2.7 now which isn't released yet but builds just
> > fine with version 2.2.6a (just checked it)...
> >
> > thanks,
> >
> > Marc
>
> http://pogma.com/libtool/libtool-2.2.7a.tar.gz
>
> Keep in mind that master is far from being stable or supported. It will
> eat your machines.
>
> Fabio
thanks for the pointer.
Got a mail from another user about it and just tried to reproduce the
problem.
But i don't get the point in forcing users to upgrade there toolchain if
earlier versions of tools could build the configure script just fine in
the end...
I could make some tests to get the right requirements if you are
accepting patches against configure.ac which change the requirements to
versions which are more suitable for the macros used...
BTW i got stable3 up running just fine on our test environment...
Marc
next prev parent reply other threads:[~2009-08-12 11:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 10:31 [Cluster-devel] Autotools version requirements to high on cluster master branch? Marc
2009-08-12 11:11 ` Fabio M. Di Nitto
2009-08-12 11:40 ` Marc [this message]
2009-08-12 11:56 ` Fabio M. Di Nitto
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=1250077249.21656.21.camel@marc \
--to=unknown@example.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.