To be honest, I don't think we've ever tested on Tru64, so I'm not surprised 
that it doesn't work.  Indeed, I think that it is unlikely that we will ever 
support Tru64.  :-(

Sorry!


On Jun 7, 2012, at 12:43 PM, <bill.gless...@cwu.edu> <bill.gless...@cwu.edu> 
wrote:

> 
> Hello,
> 
> I am having trouble with the *** Assembler section of the GNU autoconf
> step in trying to build OpenMPI version 1.6 on an HP AlphaServer GS160
> running Tru64unix version 5.1B-6:
> 
> # uname -a
> OSF1 zozma.cts.cwu.edu V5.1 2650 alpha
> 
> The output is of the ./configure run
> zozma(bash)% ./configure --prefix=/usr/local/OpenMPI \
> --enable-shared --enable-static :
> 
> ...
> 
> *** Assembler
> checking dependency style of gcc... gcc3
> checking for BSD- or MS-compatible name lister (nm)... /usr/local/bin/nm -B
> checking the name lister (/usr/local/bin/nm -B) interface... BSD nm
> checking for fgrep... /usr/local/bin/grep -F
> checking if need to remove -g from CCASFLAGS... no
> checking whether to enable smp locks... yes
> checking if .proc/endp is needed... no
> checking directive for setting text section... .text
> checking directive for exporting symbols... .globl
> checking for objdump... objdump
> checking if .note.GNU-stack is needed... no
> checking suffix for labels... :
> checking prefix for global symbol labels... none
> configure: error: Could not determine global symbol label prefix
> 
> The ./config.log is appended.
> 
> Can anyone provide some information or suggestions on how to resolve this
> issue?
> 
> Thank you for your assistance,
> Bill Glessner   - System programmer , Cenral Washington University
> 
> ******


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/


Reply via email to