Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [OMPI devel] Migrate the OpenMPI to VxWorks
From: Ralph Castain (rhc_at_[hidden])
Date: 2010-04-15 23:35:37

I have not personally tried, but I am pretty sure that you can install the autotools under VxWorks - have you tried to download the latest autotool tarballs and build them?

On Apr 15, 2010, at 9:30 PM, Õž§ wrote:

> Hello everyone ,
> For the purpose to migrate the OpenMPI to VxWorks ,I have set up a VxWorks development environment with WorkBench 3.0. It is really a good news that the WorkBench supports gnu building tools, bash and some frequently used command like sed ,awd and so on but not the Autotools (Autoconf/Automake) .Once I wonder the configure script file generated under the linux may work well under the workbench shell environment . But it is a frustrate to find when I launch the configure ,it just hang without any prompt .I look into the problem and found maybe the version of the bash in the VxWorks is too low to parse the configure file .
> Then I come across the cmake which is used to as building tools under windows for the openmpi. Because of the feature of ¡°cross-platform¡± ,I think it is possible to use cmake to migrate .Also I found boostcmake project which supports the vxworks gnu compile tools using cmake .
> But considering my poor knowledge about the building system (Autotools,cmake,etc),I need some guide and advice to review what I plan to do is a possible .
> Thank you in advance !
> Jing Zhang
> _______________________________________________
> devel mailing list
> devel_at_[hidden]