date:20170330

Re: [OMPI devel] Segfault on MPI init

2017-03-30 Thread Cyril Bordage

Hello,

when I went back to this problem, the segfault did not happen again...
I do not know why, but I am glad with that.


Cyril.

Le 13/02/2017 à 10:15, Cyril Bordage a écrit :
> Unfortunately this does not complete this thread. The problem is not
> solved! It is not an installation problem. I have no previous
> installation since I use separate directories.
> I have nothing specific to MPI path in my env, I just use the complete
> path to mpicc and mpirun.
> 
> The error depends on which node I run on. For example I can run on node1
> and node2, or node1 and node3, or node2 and node3, but not on node1,
> node2 and node3. With the official version of the platform (1.8.1) it
> works like a charm.
> 
> George, maybe, you could see it by yourself by connecting to our
> platform (plafrim), since you have an account. It should be easier to
> understand and see our problem.
> 
> 
> Cyril.
> 
> Le 10/02/2017 à 18:15, George Bosilca a écrit :
>> To complete this thread, the problem is now solved. Some .so were lingering 
>> around from a previous installation causing startup pb.
>>
>>   George.
>>
>>
>>> On Feb 10, 2017, at 05:38 , Cyril Bordage  wrote:
>>>
>>> Thank you for your answer.
>>> I am running the git master version (last tested was cad4c03).
>>>
>>> FYI, Clément Foyer is talking with George Bosilca about this problem.
>>>
>>>
>>> Cyril.
>>>
>>> Le 08/02/2017 à 16:46, Jeff Squyres (jsquyres) a écrit :
 What version of Open MPI are you running?

 The error is indicating that Open MPI is trying to start a user-level 
 helper daemon on the remote node, and the daemon is seg faulting (which is 
 unusual).

 One thing to be aware of:

 https://www.open-mpi.org/faq/?category=building#install-overwrite



> On Feb 6, 2017, at 8:14 AM, Cyril Bordage  wrote:
>
> Hello,
>
> I cannot run the a program with MPI when I compile it myself.
> On some nodes I have the following error:
> 
> [mimi012:17730] *** Process received signal ***
> [mimi012:17730] Signal: Segmentation fault (11)
> [mimi012:17730] Signal code: Address not mapped (1)
> [mimi012:17730] Failing at address: 0xf8
> [mimi012:17730] [ 0] /lib64/libpthread.so.0(+0xf500)[0x766c0500]
> [mimi012:17730] [ 1]
> /home/bordage/modules/openmpi/openmpi-debug/lib/libopen-pal.so.0(opal_libevent2022_event_priority_set+0xa9)[0x7781fcb9]
> [mimi012:17730] [ 2]
> /home/bordage/modules/openmpi/openmpi-debug/lib/openmpi/mca_oob_tcp.so(+0xebcd)[0x7197fbcd]
> [mimi012:17730] [ 3]
> /home/bordage/modules/openmpi/openmpi-debug/lib/openmpi/mca_oob_tcp.so(mca_oob_tcp_peer_accept+0xa1)[0x71981e34]
> [mimi012:17730] [ 4]
> /home/bordage/modules/openmpi/openmpi-debug/lib/openmpi/mca_oob_tcp.so(+0xab1d)[0x7197bb1d]
> [mimi012:17730] [ 5]
> /home/bordage/modules/openmpi/openmpi-debug/lib/libopen-pal.so.0(opal_libevent2022_event_base_loop+0x53c)[0x7782323c]
> [mimi012:17730] [ 6]
> /home/bordage/modules/openmpi/openmpi-debug/lib/libopen-pal.so.0(+0x3d34c)[0x777c534c]
> [mimi012:17730] [ 7] /lib64/libpthread.so.0(+0x7851)[0x766b8851]
> [mimi012:17730] [ 8] /lib64/libc.so.6(clone+0x6d)[0x7640694d]
> [mimi012:17730] *** End of error message ***
> --
> ORTE has lost communication with its daemon located on node:
>
> hostname:  mimi012
>
> This is usually due to either a failure of the TCP network
> connection to the node, or possibly an internal failure of
> the daemon itself. We cannot recover from this failure, and
> therefore will terminate the job.
> --
> 
>
> The error does not appear with the official MPI installed in the
> platform. I asked the admins about their compilation options but there
> is nothing particular.
>
> Moreover it appears only for some node lists. Still, the nodes seem to
> be fine since it works with the official version of MPI of the platform.
>
> To be sure it is not a network problem I tried to use "-mca btl
> tcp,sm,self" or "-mca btl openib,sm,self" with no change.
>
> Do you have any idea where this error may come from?
>
> Thank you.
>
>
> Cyril Bordage.
> ___
> devel mailing list
> devel@lists.open-mpi.org
> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel


>>> ___
>>> devel mailing list
>>> devel@lists.open-mpi.org
>>> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
>>
>> __

[OMPI devel] Problem with bind-to

2017-03-30 Thread Cyril Bordage

Hello,

I am using the git version of MPI with "-bind-to core -report-bindings"
and I get that for all processes:
[miriel010:160662] MCW rank 0 not bound


When I use an old version I get:
[miriel010:44921] MCW rank 0 bound to socket 0[core 0[hwt 0]]:
[B/././././././././././.][./././././././././././.]

>From git bisect the culprit seems to be: 48fc339

This bug happends only when I launch my mpirun command from a login node
and not
from a compute node.


Cyril.
___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

[OMPI devel] Pull request: LANL-XXX tests failing

2017-03-30 Thread DERBEY, NADIA

Hi,

I just created a pull request and I have a failure in 4/8 checks, all related 
to LANL:

LANL-CI
LANL-OS-X
LANL-disable-dlopen
LANL-distcheck

When I ask for the failures details, I repectively get the following messages:
==

...
libtoolize: copying file `config/lt~obsolete.m4'
Build was aborted
ERROR: Step ?Set build status on GitHub commit [deprecated]? failed: no 
workspace for ompi_master_PR_CLE #1447
Setting status of b6de94e4490b91aaa6c5df70954fbabb8794528b to FAILURE with url 

 
https://jenkins.open-mpi.org/jenkins/job/ompi_master_PR_CLE/1447/
 and message: ' '
Using context: LANL-CI
Finished: ABORTED

==

...
config.status: creating opal/mca/mpool/hugepage/Makefile
Build was aborted
ERROR: Step ‘Set build status on GitHub commit [deprecated]’ failed: no 
workspace for ompi_pr_osx #557
config.status: 
creating opal/mca/mpool/memkind/Makefile
Setting status of b6de94e4490b91aaa6c5df70954fbabb8794528b to FAILURE with url 
https://jenkins.open-mpi.org/jenkins/job/ompi_pr_osx/557/ and message: ' '
Using context: LANL-OS-X
Finished: ABORTED

==

...
parallel-tests: installing 'config/test-driver'
Build was aborted
ERROR: Step ‘Set build status on GitHub commit [deprecated]’ failed: no 
workspace for ompi_master_pr_disable_dlopen #1464
Setting status of b6de94e4490b91aaa6c5df70954fbabb8794528b to FAILURE with url 

 
https://jenkins.open-mpi.org/jenkins/job/ompi_master_pr_disable_dlopen/1464/
 and message: ' '
Using context: LANL-disable-dlopen
Finished: ABORTED

==

...
parallel-tests: installing 'config/test-driver'
Build was aborted
ERROR: Step ‘Set build status on GitHub commit [deprecated]’ failed: no 
workspace for ompi_master_pr_distcheck #1457
Setting status of b6de94e4490b91aaa6c5df70954fbabb8794528b to FAILURE with url 

 
https://jenkins.open-mpi.org/jenkins/job/ompi_master_pr_distcheck/1457/
 and message: ' '
Using context: LANL-distcheck
Finished: ABORTED

==

Can somebody tell me what I did something wrong? (Compilation went fine on my 
side).

Regards,

--
Nadia Derbey - B1-387
HPC R&D - MPI
Tel: +33 4 76 29 77 62
nadia.der...@atos.net
1 Rue de Provence BP 208
38130 Echirolles Cedex, France
www.atos.com
___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

Re: [OMPI devel] Pull request: LANL-XXX tests failing

2017-03-30 Thread r...@open-mpi.org

You didn’t do anything wrong - the Jenkins test server at LANL is having a 
problem.

> On Mar 30, 2017, at 8:22 AM, DERBEY, NADIA  wrote:
> 
> Hi,
> 
> I just created a pull request and I have a failure in 4/8 checks, all related 
> to LANL:
> 
> LANL-CI
> LANL-OS-X
> LANL-disable-dlopen
> LANL-distcheck
> 
> When I ask for the failures details, I repectively get the following messages:
> ==
> ...
> libtoolize: copying file `config/lt~obsolete.m4'
> Build was aborted
> ERROR: Step ?Set build status on GitHub commit [deprecated]? failed: no 
> workspace for ompi_master_PR_CLE #1447
> Setting status of b6de94e4490b91aaa6c5df70954fbabb8794528b to FAILURE with 
> url  
> https
>  
> ://jenkins.open-mpi.org/jenkins/job/ompi_master_PR_CLE/1447/
>  and message: ' '
> Using context: LANL-CI
> Finished: ABORTED
> ==
> ...
> config.status: creating opal/mca/mpool/hugepage/Makefile
> Build was aborted
> ERROR: Step ‘Set build status on GitHub commit [deprecated]’ failed: no 
> workspace for ompi_pr_osx #557
> config.status : 
> creating opal/mca/mpool/memkind/Makefile
> Setting status of b6de94e4490b91aaa6c5df70954fbabb8794528b to FAILURE with 
> url https://jenkins.open-mpi.org/jenkins/job/ompi_pr_osx/557/ 
>  and message: ' '
> Using context: LANL-OS-X
> Finished: ABORTED
> ==
> ...
> parallel-tests: installing 'config/test-driver'
> Build was aborted
> ERROR: Step ‘Set build status on GitHub commit [deprecated]’ failed: no 
> workspace for ompi_master_pr_disable_dlopen #1464
> Setting status of b6de94e4490b91aaa6c5df70954fbabb8794528b to FAILURE with 
> url  
> https
>  
> ://jenkins.open-mpi.org/jenkins/job/ompi_master_pr_disable_dlopen/1464/
>  and message: ' '
> Using context: LANL-disable-dlopen
> Finished: ABORTED
> ==
>  ...
> parallel-tests: installing 'config/test-driver'
> Build was aborted
> ERROR: Step ‘Set build status on GitHub commit [deprecated]’ failed: no 
> workspace for ompi_master_pr_distcheck #1457
> Setting status of b6de94e4490b91aaa6c5df70954fbabb8794528b to FAILURE with 
> url  
> https
>  
> ://jenkins.open-mpi.org/jenkins/job/ompi_master_pr_distcheck/1457/
>  and message: ' '
> Using context: LANL-distcheck
> Finished: ABORTED
> ==
> 
> Can somebody tell me what I did something wrong? (Compilation went fine on my 
> side).
> 
> Regards,
> -- 
> Nadia Derbey - B1-387
> HPC R&D - MPI
> Tel: +33 4 76 29 77 62
> nadia.der...@atos.net 
> 1 Rue de Provence BP 208
> 38130 Echirolles Cedex, France
> www.atos.com 
> ___
> devel mailing list
> devel@lists.open-mpi.org
> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

Re: [OMPI devel] Pull request: LANL-XXX tests failing

2017-03-30 Thread Howard Pritchard

Actually it looks like we're running out of disk space at AWS.


2017-03-30 9:28 GMT-06:00 r...@open-mpi.org :

> You didn’t do anything wrong - the Jenkins test server at LANL is having a
> problem.
>
> On Mar 30, 2017, at 8:22 AM, DERBEY, NADIA  wrote:
>
> Hi,
>
> I just created a pull request and I have a failure in 4/8 checks, all
> related to LANL:
>
> LANL-CI
> LANL-OS-X
> LANL-disable-dlopen
> LANL-distcheck
>
> When I ask for the failures details, I repectively get the following
> messages:
> ==
>
> ...
> libtoolize: copying file `config/lt~obsolete.m4'
> Build was aborted
> ERROR: Step ?Set build status on GitHub commit [deprecated]? failed: no 
> workspace for ompi_master_PR_CLE #1447Setting status of 
> b6de94e4490b91aaa6c5df70954fbabb8794528b to FAILURE with url  
> https
>  
> ://jenkins.open-mpi.org/jenkins/job/ompi_master_PR_CLE/1447/
>  and message: ' '
> Using context: LANL-CI
> Finished: ABORTED
>
> ==
>
> ...
> config.status: creating opal/mca/mpool/hugepage/Makefile
> Build was aborted
> ERROR: Step ‘Set build status on GitHub commit [deprecated]’ failed: no 
> workspace for ompi_pr_osx #557config.status 
> : creating 
> opal/mca/mpool/memkind/Makefile
> Setting status of b6de94e4490b91aaa6c5df70954fbabb8794528b to FAILURE with 
> url https://jenkins.open-mpi.org/jenkins/job/ompi_pr_osx/557/ and message: ' '
> Using context: LANL-OS-X
> Finished: ABORTED
>
> ==
>
> ...
> parallel-tests: installing 'config/test-driver'
> Build was aborted
> ERROR: Step ‘Set build status on GitHub commit [deprecated]’ failed: no 
> workspace for ompi_master_pr_disable_dlopen #1464Setting status of 
> b6de94e4490b91aaa6c5df70954fbabb8794528b to FAILURE with url  
> https
>  
> ://jenkins.open-mpi.org/jenkins/job/ompi_master_pr_disable_dlopen/1464/
>  and message: ' '
> Using context: LANL-disable-dlopen
> Finished: ABORTED
>
> ==
>
> ...
> parallel-tests: installing 'config/test-driver'
> Build was aborted
> ERROR: Step ‘Set build status on GitHub commit [deprecated]’ failed: no 
> workspace for ompi_master_pr_distcheck #1457Setting status of 
> b6de94e4490b91aaa6c5df70954fbabb8794528b to FAILURE with url  
> https
>  
> ://jenkins.open-mpi.org/jenkins/job/ompi_master_pr_distcheck/1457/
>  and message: ' '
> Using context: LANL-distcheck
> Finished: ABORTED
>
> ==
>
> Can somebody tell me what I did something wrong? (Compilation went fine on
> my side).
>
> Regards,
>
> --
> Nadia Derbey - B1-387
> HPC R&D - MPI
> Tel: +33 4 76 29 77 62 <+33%204%2076%2029%2077%2062>nadia.der...@atos.net
> 1 Rue de Provence BP 208
> 38130 Echirolles Cedex, Francewww.atos.com
>
> ___
> devel mailing list
> devel@lists.open-mpi.org
> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
>
>
>
> ___
> devel mailing list
> devel@lists.open-mpi.org
> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
>
___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

Re: [OMPI devel] Pull request: LANL-XXX tests failing

2017-03-30 Thread Howard Pritchard

well not sure what's going on.  there was an upgrade of jenkins a bunch of
functionality seems to have gotten lost.


2017-03-30 9:37 GMT-06:00 Howard Pritchard :

> Actually it looks like we're running out of disk space at AWS.
>
>
> 2017-03-30 9:28 GMT-06:00 r...@open-mpi.org :
>
>> You didn’t do anything wrong - the Jenkins test server at LANL is having
>> a problem.
>>
>> On Mar 30, 2017, at 8:22 AM, DERBEY, NADIA  wrote:
>>
>> Hi,
>>
>> I just created a pull request and I have a failure in 4/8 checks, all
>> related to LANL:
>>
>> LANL-CI
>> LANL-OS-X
>> LANL-disable-dlopen
>> LANL-distcheck
>>
>> When I ask for the failures details, I repectively get the following
>> messages:
>> ==
>>
>> ...
>> libtoolize: copying file `config/lt~obsolete.m4'
>> Build was aborted
>> ERROR: Step ?Set build status on GitHub commit [deprecated]? failed: no 
>> workspace for ompi_master_PR_CLE #1447Setting status of 
>> b6de94e4490b91aaa6c5df70954fbabb8794528b to FAILURE with url  
>> https
>>  
>> ://jenkins.open-mpi.org/jenkins/job/ompi_master_PR_CLE/1447/
>>  and message: ' '
>> Using context: LANL-CI
>> Finished: ABORTED
>>
>> ==
>>
>> ...
>> config.status: creating opal/mca/mpool/hugepage/Makefile
>> Build was aborted
>> ERROR: Step ‘Set build status on GitHub commit [deprecated]’ failed: no 
>> workspace for ompi_pr_osx #557config.status 
>> : creating 
>> opal/mca/mpool/memkind/Makefile
>> Setting status of b6de94e4490b91aaa6c5df70954fbabb8794528b to FAILURE with 
>> url https://jenkins.open-mpi.org/jenkins/job/ompi_pr_osx/557/ and message: ' 
>> '
>> Using context: LANL-OS-X
>> Finished: ABORTED
>>
>> ==
>>
>> ...
>> parallel-tests: installing 'config/test-driver'
>> Build was aborted
>> ERROR: Step ‘Set build status on GitHub commit [deprecated]’ failed: no 
>> workspace for ompi_master_pr_disable_dlopen #1464Setting status of 
>> b6de94e4490b91aaa6c5df70954fbabb8794528b to FAILURE with url  
>> https
>>  
>> ://jenkins.open-mpi.org/jenkins/job/ompi_master_pr_disable_dlopen/1464/
>>  and message: ' '
>> Using context: LANL-disable-dlopen
>> Finished: ABORTED
>>
>> ==
>>
>> ...
>> parallel-tests: installing 'config/test-driver'
>> Build was aborted
>> ERROR: Step ‘Set build status on GitHub commit [deprecated]’ failed: no 
>> workspace for ompi_master_pr_distcheck #1457Setting status of 
>> b6de94e4490b91aaa6c5df70954fbabb8794528b to FAILURE with url  
>> https
>>  
>> ://jenkins.open-mpi.org/jenkins/job/ompi_master_pr_distcheck/1457/
>>  and message: ' '
>> Using context: LANL-distcheck
>> Finished: ABORTED
>>
>> ==
>>
>> Can somebody tell me what I did something wrong? (Compilation went fine
>> on my side).
>>
>> Regards,
>>
>> --
>> Nadia Derbey - B1-387
>> HPC R&D - MPI
>> Tel: +33 4 76 29 77 62 <+33%204%2076%2029%2077%2062>nadia.der...@atos.net
>> 1 Rue de Provence BP 208
>> 38130 Echirolles Cedex, Francewww.atos.com
>>
>> ___
>> devel mailing list
>> devel@lists.open-mpi.org
>> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
>>
>>
>>
>> ___
>> devel mailing list
>> devel@lists.open-mpi.org
>> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
>>
>
>
___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

Re: [OMPI devel] Pull request: LANL-XXX tests failing

2017-03-30 Thread Barrett, Brian via devel

Yeah, sorry about that; we had a configuration issue while trying to clean up 
some issues on the server which hosts the OMPI Jenkins install.  It should be 
back to normal now.

Brian

On Mar 30, 2017, at 11:46 AM, Howard Pritchard 
mailto:hpprit...@gmail.com>> wrote:

well not sure what's going on.  there was an upgrade of jenkins a bunch of 
functionality seems to have gotten lost.


2017-03-30 9:37 GMT-06:00 Howard Pritchard 
mailto:hpprit...@gmail.com>>:
Actually it looks like we're running out of disk space at AWS.


2017-03-30 9:28 GMT-06:00 r...@open-mpi.org 
mailto:r...@open-mpi.org>>:
You didn’t do anything wrong - the Jenkins test server at LANL is having a 
problem.

On Mar 30, 2017, at 8:22 AM, DERBEY, NADIA 
mailto:nadia.der...@atos.net>> wrote:

Hi,

I just created a pull request and I have a failure in 4/8 checks, all related 
to LANL:

LANL-CI
LANL-OS-X
LANL-disable-dlopen
LANL-distcheck

When I ask for the failures details, I repectively get the following messages:
==

...
libtoolize: copying file `config/lt~obsolete.m4'
Build was aborted
ERROR: Step ?Set build status on GitHub commit [deprecated]? failed: no 
workspace for ompi_master_PR_CLE #1447
Setting status of b6de94e4490b91aaa6c5df70954fbabb8794528b to FAILURE with url 

 
https://jenkins.open-mpi.org/jenkins/job/ompi_master_PR_CLE/1447/
 and message: ' '
Using context: LANL-CI
Finished: ABORTED

==

...
config.status: creating opal/mca/mpool/hugepage/Makefile
Build was aborted
ERROR: Step ‘Set build status on GitHub commit [deprecated]’ failed: no 
workspace for ompi_pr_osx #557
config.status: 
creating opal/mca/mpool/memkind/Makefile
Setting status of b6de94e4490b91aaa6c5df70954fbabb8794528b to FAILURE with url 
https://jenkins.open-mpi.org/jenkins/job/ompi_pr_osx/557/ and message: ' '
Using context: LANL-OS-X
Finished: ABORTED

==

...
parallel-tests: installing 'config/test-driver'
Build was aborted
ERROR: Step ‘Set build status on GitHub commit [deprecated]’ failed: no 
workspace for ompi_master_pr_disable_dlopen #1464
Setting status of b6de94e4490b91aaa6c5df70954fbabb8794528b to FAILURE with url 

 
https://jenkins.open-mpi.org/jenkins/job/ompi_master_pr_disable_dlopen/1464/
 and message: ' '
Using context: LANL-disable-dlopen
Finished: ABORTED

==

...
parallel-tests: installing 'config/test-driver'
Build was aborted
ERROR: Step ‘Set build status on GitHub commit [deprecated]’ failed: no 
workspace for ompi_master_pr_distcheck #1457
Setting status of b6de94e4490b91aaa6c5df70954fbabb8794528b to FAILURE with url 

 
https://jenkins.open-mpi.org/jenkins/job/ompi_master_pr_distcheck/1457/
 and message: ' '
Using context: LANL-distcheck
Finished: ABORTED

==

Can somebody tell me what I did something wrong? (Compilation went fine on my 
side).

Regards,

--
Nadia Derbey - B1-387
HPC R&D - MPI
Tel: +33 4 76 29 77 62
nadia.der...@atos.net
1 Rue de Provence BP 208
38130 Echirolles Cedex, France
www.atos.com

___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel


___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel


___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

Re: [OMPI devel] 2.0.2 SRPM in "install_in_opt" configuration creates file outside /opt

2017-03-30 Thread Kevin Buckley

On 29 March 2017 at 13:49, Jeff Squyres (jsquyres)  wrote:
> I have no objections to this.
>
> Unfortunately, I don't have the time to work on it, but we'd be glad to look 
> at pull requests to introduce this functionality.  :-)

Yes, yes, alright.

I am though slightly confused, following the move to GitHub.

If I go to the GiHub repo, the available release tarballs appear, for
example, as: ompi-2.0.2.tar.gz
and unpack as

drwxrwxr-x root/root 0 2017-01-31 05:54 ompi-2.0.2/
-rw-rw-r-- root/root 15724 2017-01-31 05:54 ompi-2.0.2/.gitignore
.-rw-rw-r-- root/root  4212 2017-01-31 05:54 ompi-2.0.2/.mailmap
-rw-rw-r-- root/root  3415 2017-01-31 05:54 ompi-2.0.2/.travis.yml
-rw-rw-r-- root/root  9867 2017-01-31 05:54 ompi-2.0.2/AUTHORS
..

that is, using the GitHub subproject/repo name.

However, the tarball refered to in the SRPM's SPEC-file has the
"does what it says on the tin" name:

Source: openmpi-%{version}.tar.bz2

which is also the version availble from the open-mpi.org website, and which
unpacks as

drwxrwxr-x mpiteam/mpiteam   0 2017-02-01 04:21 openmpi-2.0.2/
-rw-rw-r-- mpiteam/mpiteam 9867 2017-01-27 08:14 openmpi-2.0.2/AUTHORS
...

Are the GitHub tarballs and the "availble from the open-mpi.org
website" tarballs
the same ? (except for the git stuff)

Should they be the same, now that the development is managed at GitHub ?

What is your process behind taking the GitHub release tarball and
turning it into
the open-mpi.org one ? (or vice-versa ?)
___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

Re: [OMPI devel] 2.0.2 SRPM in "install_in_opt" configuration creates file outside /opt

2017-03-30 Thread Gilles Gouaillardet


Kevin,


you should only use the tarballs from www.open-mpi.org


they are generated with our scripts.
if i understand correctly, github.com has its own way of generating a 
tarball from a git tag.


Cheers,

Gilles

On 3/31/2017 1:24 PM, Kevin Buckley wrote:

On 29 March 2017 at 13:49, Jeff Squyres (jsquyres)  wrote:

I have no objections to this.

Unfortunately, I don't have the time to work on it, but we'd be glad to look at 
pull requests to introduce this functionality.  :-)

Yes, yes, alright.

I am though slightly confused, following the move to GitHub.

If I go to the GiHub repo, the available release tarballs appear, for
example, as: ompi-2.0.2.tar.gz
and unpack as

drwxrwxr-x root/root 0 2017-01-31 05:54 ompi-2.0.2/
-rw-rw-r-- root/root 15724 2017-01-31 05:54 ompi-2.0.2/.gitignore
.-rw-rw-r-- root/root  4212 2017-01-31 05:54 ompi-2.0.2/.mailmap
-rw-rw-r-- root/root  3415 2017-01-31 05:54 ompi-2.0.2/.travis.yml
-rw-rw-r-- root/root  9867 2017-01-31 05:54 ompi-2.0.2/AUTHORS
..

that is, using the GitHub subproject/repo name.


However, the tarball refered to in the SRPM's SPEC-file has the
"does what it says on the tin" name:

Source: openmpi-%{version}.tar.bz2

which is also the version availble from the open-mpi.org website, and which
unpacks as

drwxrwxr-x mpiteam/mpiteam   0 2017-02-01 04:21 openmpi-2.0.2/
-rw-rw-r-- mpiteam/mpiteam 9867 2017-01-27 08:14 openmpi-2.0.2/AUTHORS
...

Are the GitHub tarballs and the "availble from the open-mpi.org
website" tarballs
the same ? (except for the git stuff)

Should they be the same, now that the development is managed at GitHub ?

What is your process behind taking the GitHub release tarball and
turning it into
the open-mpi.org one ? (or vice-versa ?)
___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel



___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

Re: [OMPI devel] Segfault on MPI init

[OMPI devel] Problem with bind-to

[OMPI devel] Pull request: LANL-XXX tests failing

Re: [OMPI devel] Pull request: LANL-XXX tests failing

Re: [OMPI devel] Pull request: LANL-XXX tests failing

Re: [OMPI devel] Pull request: LANL-XXX tests failing

Re: [OMPI devel] Pull request: LANL-XXX tests failing

Re: [OMPI devel] 2.0.2 SRPM in "install_in_opt" configuration creates file outside /opt

Re: [OMPI devel] 2.0.2 SRPM in "install_in_opt" configuration creates file outside /opt

9 matches

Site Navigation

Mail list logo

Footer information