On Thu, Sep 1, 2016 at 3:14 PM, Jeff Squyres (jsquyres)
wrote:
>
> FWIW, we usually store the tarballs themselves in VCSs if we want to
> preserve specific third-party tarballs. It's a little gross (i.e., storing
> a big binary tarball in a VCS), but it works. Depends on
On Sep 1, 2016, at 2:05 PM, Sean Ahern wrote:
>
> In actuality, I stored off the source in our "third party" repo before I
> built it.
>
> svn add openmpi-2.0.0
> svn commit
>
> When I grabbed that source back on the machine I wanted to build on, the
> relative timestamps
Okay, I think I figured it out. The short answer is that version control
systems can mess up
relative
file system timestamps.
While I was basically doing:
tar xzf openmpi-2.0.0.tar.gz
cd openmpi-2.0.0
./configure …
make
In actuality, I stored off the source in our "third party" repo before
Ok, weird. Try running the process again (untar, configure, make) but use
"make -d" and capture the entire output so that you can see what file(s)
is(are) triggering Automake to invoke aclocal during the build (it will be a
*LOT* of output).
> On Sep 1, 2016, at 1:20 PM, Sean Ahern
Yep, that's it.
-Sean
--
Sean Ahern
Computational Engineering International
919-363-0883
On Thu, Sep 1, 2016 at 1:04 PM, Jeff Squyres (jsquyres)
wrote:
> That's odd -- I've never seen this kind of problem happen on a
> locally-mounted filesystem.
>
> Just to make sure:
That's odd -- I've never seen this kind of problem happen on a locally-mounted
filesystem.
Just to make sure: you're *not* running autogen.pl, right? You're just
basically doing this:
-
$ tar xf openmpi-2.0.0.tar.bz2
$ cd openmpi-2.0.0
$ ./configure ...
$ make ...
-
Right?
> On Sep
Greetings, Jeff.
Sure, I could see that. But I'm trying to run on a locally mounted
filesystem in this case. I may need to run make in debug mode and see what
it thinks is out of date. See if you guys can help me track down the
dependency problem.
-Sean
--
Sean Ahern
Computational Engineering
Greetings Sean.
Yes, you are correct - when you build from the tarball, you should not need the
GNU autotools.
When tarball builds fail like this, it *usually* means that you are building in
a network filesystem, and the time is not well synchronized between the machine
on which you are