On Wed, 7 Jan 2004, Sam Watson wrote:
> Hello. I've been trying to build LAM 7.0.3 on a Linux system running a
> 2.4.2-2smp kernel, and I've been having some difficulties. I've tried
> both the Intel (our preference, because we use it for most things) and
> the GCC compilers, and keep getting errors during make. Usually (but not
> always) these have to do with Autoconf and Automake. As far as I can
> tell from the documentation, I shouldn't need these tools at all (I
> discovered this after trying and failing to build them), since the
> configure script should be standalone.
Sorry for the delay in replying -- most of us are traveling right now.
Yes, you should not need these tools -- the configure script that is in
the 7.0.3 tarball should be 100% standalone.
> I've attached gzipped versions of config.log and config.status, as well
> as the screen outputs of config and make. These are from the GCC
> attempt. Any help will be appreciated.
Something seems quite odd here -- it should not be attempting to run
automake (or any of the other tools) during the make process.
One cause for this can be when you are building on a networked filesystem
and your local node does not have a tightly sychronized clock with the
network filesystem server (i.e., timestamps get all out of whack).
Can you verify that your timestamps are appearing properly on files?
Perhaps something like this:
-----
$ date; touch foo; ls -l foo; date
-----
Look at the times reported by "date" and then look at the timestamp on the
foo file. Do they match?
If not, this is potentially your problem, and you need to run ntp or some
other network-time-sychronizer to ensure that your file server and working
node(s) all share the same time.
Let me know if this helps.
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
