> Date: Mon, 30 Mar 2009 19:05:25 +0100
> From: Kevin McManus <k.mcmanus_at_[hidden]>
> Subject: Re: [OMPI users] Linux opteron infiniband sunstudio configure
> To: Open MPI Users <users_at_[hidden]>
> Message-ID: <20090330180524.GT13818_at_[hidden]>
> 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 ... 126.96.36.199-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 ... 188.8.131.52-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"?