LAM/MPI logo

LAM/MPI General User's Mailing List Archives

  |   Home   |   Download   |   Documentation   |   FAQ   |   all just in this list

From: Christopher Barton (c.barton_at_[hidden])
Date: 2004-01-07 15:55:52


Thanks alot Jeff.

Just worked that out about 10 min before your post arrived! Oh well,
it's good to see how all this stuff works.

Make is running now so fingers crossed!

Do you know if it's possible to mix Linux and Cygwin nodes as per my
other post?

ta,

Jeff Squyres wrote:

>On Wed, 7 Jan 2004, Christopher Barton wrote:
>
>
>
>>Still hard at it ...
>>
>>
>
>Just seeing your previous mails (sorry, many of us are traveling this
>week...).
>
>The "sed" that you are seeing is generated by Gnu Autoconf.
>
>You should *not* be running autogen.sh -- if you get a downloaded tarball
>(either 7.0.3 or one of the nightly snapshots), autogen.sh has already
>been run for you and you should only need to run configure. Have you
>tried doing that with a fresh nightly tarball? I'm wondering if your
>installed version of Autoconf/Automake/Libtool are too old, or has a bug
>in the sed output...?
>
>
>
>>It is the execution of the code snipets below which fail on
>>"lam-7.1a1cvs20040107.tar.gz".
>>The first one of these snipets in the generated "config.status" is
>>trying to operate on "Makefile.in" to produce Makefile and goes into
>>some sort recusive loop.
>>
>>
>
>It could well be significant, but this is something that we never see /
>edit -- config.status is fully generated by configure, which is generated
>by GNU autoconf. Hence, if there's a change, then it's potentially
>something that's different because we have upgraded versions of Autoconf
>when making distribution tarballs.
>
>Note that the CVS snapshots are created with AC 2.59, while 7.0.3's
>configure was created with AC 2.57.
>
>
>