> > 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 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? What happens when you run 'uname -X'? TIA k.mcma...@gre.ac.uk - http://staffweb.cms.gre.ac.uk/~k.mcmanus -------------------------------------------------------------- Dr Kevin McManus Queen Mary 413 School of Computing & Mathematical Sciences, University of Greenwich, Old Royal Naval College, Park Row, Greenwich, Tel +44 (0)208 331 8719 London, SE10 9LS Fax +44 (0)208 331 8665 -------------------------------------------------------------- University of Greenwich, a charity and company limited by guarantee, registered in England (reg no. 986729) Registered Office: Old Royal Naval College
