I think the problem was with open mpi 1.8.3. I went back to my older installation 1.6.5 and was able to compile with blcr.
Thanks DI On Mon, Dec 1, 2014 at 11:40 AM, <users-requ...@open-mpi.org> wrote: > Send users mailing list submissions to > us...@open-mpi.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://www.open-mpi.org/mailman/listinfo.cgi/users > or, via email, send a message with subject or body 'help' to > users-requ...@open-mpi.org > > You can reach the person managing the list at > users-ow...@open-mpi.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of users digest..." > > > Today's Topics: > > 1. Re: "default-only MCA variable"? (Ralph Castain) > 2. Re: "default-only MCA variable"? (Jeff Squyres (jsquyres)) > 3. OpenMPI with blcr problem (Dewan Ibtesham (Shafi)) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 1 Dec 2014 09:47:32 -0800 > From: Ralph Castain <r...@open-mpi.org> > To: Open MPI Users <us...@open-mpi.org> > Subject: Re: [OMPI users] "default-only MCA variable"? > Message-ID: <87e1ba37-4d50-453e-8e78-8c6209b0d...@open-mpi.org> > Content-Type: text/plain; charset=utf-8 > > > > On Nov 28, 2014, at 10:08 AM, Dave Love <d.l...@liverpool.ac.uk> wrote: > > > > Gilles Gouaillardet <gilles.gouaillar...@gmail.com> writes: > > > >> It could be because configure did not find the knem headers and hence > knem is not supported and hence this mca parameter is read-only > > > > Yes, in that case (though knem was meant to be used and it's annoying > > that configure doesn't abort if it doesn't find something you've > > explicitly asked for, and I didn't immediately need it). > > FWIW: I dug into this and found why we weren?t aborting if knem was > specified and not found. This obviously isn?t the specified OMPI behavior, > so I fixed it in the trunk and will port it back to v1.8.4 > > > However, I got > > the same for at least mpi_abort_print_stack with that parameter set. > > I?m not entirely familiar with the thinking behind it, but it appears that > some MCA params are intended solely for reporting purposes and are > therefore not really ?settable?. The ?have_knem_support? is one such > example, and it sounds like you may have found some others. > > I?ll ask around and see why we did that as I can understand how it would > be confusing. > > > > > This didn't happen with OMPI 1.6 and there's no obvious way to turn it > > off. > > > > _______________________________________________ > > users mailing list > > us...@open-mpi.org > > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users > > Link to this post: > http://www.open-mpi.org/community/lists/users/2014/11/25887.php > > > > ------------------------------ > > Message: 2 > Date: Mon, 1 Dec 2014 17:57:34 +0000 > From: "Jeff Squyres (jsquyres)" <jsquy...@cisco.com> > To: "Open MPI User's List" <us...@open-mpi.org> > Subject: Re: [OMPI users] "default-only MCA variable"? > Message-ID: <94c5e448-65d9-40a2-838f-2e511359f...@cisco.com> > Content-Type: text/plain; charset="Windows-1252" > > On Dec 1, 2014, at 12:47 PM, Ralph Castain <r...@open-mpi.org> wrote: > > > I?m not entirely familiar with the thinking behind it, but it appears > that some MCA params are intended solely for reporting purposes and are > therefore not really ?settable?. The ?have_knem_support? is one such > example, and it sounds like you may have found some others. > > Correct. We call these "info" MCA params. They've been around for a > long, long time, but I think they may have gotten renamed (at least in the > output) in the MCA revamp in the 1.7/1.8 series. > > Perhaps we need less confusing output in this area. > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > > > ------------------------------ > > Message: 3 > Date: Mon, 1 Dec 2014 11:39:53 -0700 > From: "Dewan Ibtesham (Shafi)" <de...@cs.unm.edu> > To: us...@open-mpi.org > Subject: [OMPI users] OpenMPI with blcr problem > Message-ID: > < > cakfg0+o_hzu3-gi40vz7jztsa-0qd8j2n0hpgfyahmdqsc6...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > I am trying to build blcr with openmpi. I have done it before without any > problem with earlier versions of openMPI but having problem on > 1.8.3 > > When I tried to configure, I get the following warning > > "configure:298525: WARNING: unrecognized options: --with-ft, --with-blcr" > > ./configure --help also doesn't provide any blcr related inputs. > > I went ahead and built it anyway and the following libraries are generated > instead of blcr specific ones. > > mca_crs_none.la > mca_crs_none.so > > Attached is the config log. > > Thank you > > DI > -------------- next part -------------- > HTML attachment scrubbed and removed > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: config.log.tgz > Type: application/x-gzip > Size: 191361 bytes > Desc: not available > URL: < > http://www.open-mpi.org/MailArchives/users/attachments/20141201/482bd290/attachment.tgz > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users > > ------------------------------ > > End of users Digest, Vol 3057, Issue 2 > ************************************** >
