I was talking with Jeff Squyres about your issue and he thinks the
config.guess issue needs to be resolved first, even though your
specification of x86_64 seems to get you by.
So, do you still see the unexpected "(" if you try and run
config/config.guess directly? The original issue IIRC was:
etected VPATH build
checking build system type... ../config/config.guess: line 1102: syntax
error near unexpected token `('
../config/config.guess: line 1102: ` UNAME_REL=`(/bin/uname -X|grep
Release|sed -e 's/.*= //')`'
configure: error: cannot guess build type; you must specify one
Can you manually run UNAME_REL=`(/bin/uname -X|grep Release|sed -e
's/.*= //')` in your shell without error?
--td
Terry Dontje wrote:
Date: Mon, 30 Mar 2009 19:05:25 +0100
From: Kevin McManus <k.mcma...@gre.ac.uk>
Subject: Re: [OMPI users] Linux opteron infiniband sunstudio
configure
problem
To: Open MPI Users <us...@open-mpi.org>
Message-ID: <20090330180524.gt13...@gre.ac.uk>
Content-Type: text/plain; charset=us-ascii
> > I will try to reproduce the problem.
> > I am not able to reproduce this with openmpi-1.3.2a1r20880.tar.gz.
> > $ uname -a
> Linux ... 2.6.16.46-0.12-smp #1 SMP Thu May 17 14:00:09 UTC 2007
x86_64 x86_64 x86_64 GNU/Linux
> $ cc -V
> cc: Sun C 5.9 Linux_i386 Patch 124871-01 2007/07/31
interesting, this is a v.similar system
->uname -a
Linux ... 2.6.16.54-0.2.5-smp #1 SMP Mon Jan 21 13:29:51 UTC 2008
x86_64 x86_64 x86_64 GNU/Linux
->cc -V
cc: Sun C 5.9 Linux_i386 Patch 124871-01 2007/07/31
I think we are looking in the wrong place, these syntax errors worry me,
I have never seen a configure script throw one before.
->ls -l /bin/sh
lrwxrwxrwx 1 root root 4 2008-04-02 02:13 /bin/sh -> bash
I am using tcsh it may take me a while to set up bash for myself.
So it is running in bash, which is unlikely to cause problems. Looking
at the configure source it runs some near identical code for MCA basic
before retiring ungracefully immediately after deciding that it can
handle MCA bucket. Ungracefully hacking the offending parentheses
from configure causes some v.strange things to happen. I will continue
hacking but until this bears fruit... do you also need to include
'x86_64' as an argument for configure?
I don't, and pretty sure neither does Ethan.
What happens when you run 'uname -X'?
Interesting I get "uname: invalid option --X" but should this always
end up turning into "unknown"?
--td
TIA
