Re: [OMPI devel] Fwd: Open MPI 1.8: link problem when Fortran+C+Platform LSF

I know of two possibilities: 1) I cannot be certain but since the message concerns a PC-relative addressing mode, it is possible that something needs to be compiled with -fPIC to fix the issue. See if adding that option to any of the mpicc commands helps. 2) Try adding ONE of "-ll", "-lfl" or "-

Re: [OMPI devel] Fwd: Open MPI 1.8: link problem when Fortran+C+Platform LSF

I think the LSF part of this may be a red herring. Do you really need to add "-lbat -llsf" to the command line to make it work? The error message *sounds* like y.tab.o was compiled differently than others...? It's hard to know without seeing the output of mpicc --showme. On Oct 17, 2014, at

Re: [OMPI devel] Missing f08 binding for Win_allocate

Christoph - Thanks for sending this patch. I've been on travel this week, which always makes my inbox a disaster - sorry I didn't reply earlier. You did the right thing by filing a PR against master. It allows the use of the nice GitHub code review tools. I've already replied on that PR; jus

Re: [OMPI devel] OMPI BCOL hang with PMI1

Hey, Lena :). 2014-10-17 22:07 GMT+07:00 Elena Elkina : > Hi Artem, > > Actually some time ago there was a known issue with coll ml. I used to run > my command lines with -mca coll ^ml to avoid these problems, so I don't > know if it was fixed or not. It looks like you have the same problem. > b

Re: [OMPI devel] OMPI BCOL hang with PMI1

Hi Artem, Actually some time ago there was a known issue with coll ml. I used to run my command lines with -mca coll ^ml to avoid these problems, so I don't know if it was fixed or not. It looks like you have the same problem. Best regards, Elena On Fri, Oct 17, 2014 at 7:01 PM, Artem Polyakov

Re: [OMPI devel] OMPI BCOL hang with PMI1

Gilles, I checked your patch and it doesn't solve the problem I observe. I think the reason is somewhere else. 2014-10-17 19:13 GMT+07:00 Gilles Gouaillardet < gilles.gouaillar...@gmail.com>: > Artem, > > There is a known issue #235 with modex and i made PR #238 with a tentative > fix. > > Could

Re: [OMPI devel] [OMPI commits] Git: open-mpi/ompi branch master updated. dev-118-ge3be1fb

Oy! Thanks for removing that debug opal_output... :-) On Oct 17, 2014, at 7:39 AM, wrote: > This is an automated email from the git hooks/post-receive script. It was > generated because a ref change was pushed to the repository containing > the project "open-mpi/ompi". > > The branch, maste

Re: [OMPI devel] Why no release tags in open-mpi/ompi repository?

"Jeff Squyres (jsquyres)" writes: > Meaning: we deliberately chose not to change the development style of > the community to "develop on release branch" when we moved to git. Understood. It's your choice, but workflow is a big feature of Git. >> Seems to me that most people cloning open-mpi/om

[OMPI devel] Fwd: Open MPI 1.8: link problem when Fortran+C+Platform LSF

Forwarding this for Paul until his email address gets updated on the User list:Begin forwarded message:Date: October 17, 2014 at 6:35:31 AM PDTFrom: Paul Kapinos To: Open MPI Users Cc: "Kapinos, Paul" ,

Re: [OMPI devel] Why no release tags in open-mpi/ompi repository?

I hear what you are saying - we just beg to disagree :-) As Jeff said, a lot of it is history, but we’ve found this method works well for us and we’ve chosen to continue it. > On Oct 17, 2014, at 7:35 AM, Jed Brown wrote: > > Ralph Castain writes: >> We go the other direction - all code must

Re: [OMPI devel] Why no release tags in open-mpi/ompi repository?

Ralph Castain writes: > We go the other direction - all code must be committed to master so it > can “soak” prior to moving to a release branch. Maybe we're miscommunicating. Normal lifecycle for a bug fix is # start from oldest maintenance branch to which the fix is relevant git checkout

Re: [OMPI devel] ORTE headers in OPAL source

Josh, I had a look at the code (e.g., opal/mca/btl/sm/btl_sm.c) and there are two uses of orte code: if (orte_cr_continue_like_restart) and /* On restart we need the old file names to exist (not necessarily * contain content) so the CRS component does not fail when searching * for these o

Re: [OMPI devel] Why no release tags in open-mpi/ompi repository?

On Oct 17, 2014, at 6:41 AM, Jed Brown wrote: >> The ompi repo only contains the master branch. Releases are not made >> from master, and therefore it doesn't make sense to tag it with >> release tags. master is therefore not (directly) related to any given >> release. > > You can have tags in

Re: [OMPI devel] Why no release tags in open-mpi/ompi repository?

> On Oct 17, 2014, at 6:41 AM, Jed Brown wrote: > > "Jeff Squyres (jsquyres)" writes: > >> The ompi repo only contains the master branch. Releases are not made >> from master, and therefore it doesn't make sense to tag it with >> release tags. master is therefore not (directly) related to an

Re: [OMPI devel] Why no release tags in open-mpi/ompi repository?

"Jeff Squyres (jsquyres)" writes: > The ompi repo only contains the master branch. Releases are not made > from master, and therefore it doesn't make sense to tag it with > release tags. master is therefore not (directly) related to any given > release. You can have tags in the repository with

Re: [OMPI devel] Why no release tags in open-mpi/ompi repository?

On Oct 17, 2014, at 6:05 AM, Jed Brown wrote: > You can get them locally by fetching from open-mpi/ompi-release, but the > only tag in open-mpi/ompi is called "dev" and on a seemingly arbitrary > commit. Isn't that awkward already, and more so with each passing year? > Release tags in the develo

[OMPI devel] Why no release tags in open-mpi/ompi repository?

You can get them locally by fetching from open-mpi/ompi-release, but the only tag in open-mpi/ompi is called "dev" and on a seemingly arbitrary commit. Isn't that awkward already, and more so with each passing year? Release tags in the development repository are useful to determine which released

Re: [OMPI devel] OMPI BCOL hang with PMI1

Artem, There is a known issue #235 with modex and i made PR #238 with a tentative fix. Could you please give it a try and reports if it solves your problem ? Cheers Gilles Artem Polyakov wrote: >Hello, I have troubles with latest trunk if I use PMI1. > > >For example, if I use 2 nodes the app

[OMPI devel] OMPI BCOL hang with PMI1

Hello, I have troubles with latest trunk if I use PMI1. For example, if I use 2 nodes the application hangs. See backtraces from both nodes below. From them I can see that second (non launching) node hangs in bcol component selection. Here is the default setting of bcol_base_string parameter: bcol