Don't give it a host argument - unless you are trying to cross-compile, it
should figure it out for itself
On Apr 23, 2011, at 1:25 PM, Fernando Dutra Fagundes Macedo wrote:
> Correcting:
>
> I tried 1.5.2 and 1.5.3.
>
>
> -Mensagem original-
> De: users-boun...@open-mpi.org em nome
Correcting:
I tried 1.5.2 and 1.5.3.
-Mensagem original-
De: users-boun...@open-mpi.org em nome de Fernando Dutra Fagundes Macedo
Enviada: sáb 23/4/2011 16:16
Para: us...@open-mpi.org
Assunto: [OMPI users] Error with ARM target
Hi,
I am trying to use Open MPI on a Friendly ARM board,
Hi,
I am trying to use Open MPI on a Friendly ARM board, but I can't compile it to
ARM target. I'm trying to configure the package this way:
./configure -host="arm"
What can I do to make it work?
More information:
Error: "configure: error: No atomic primitives available for arm-unknown-none"
On Apr 23, 2011, at 12:07 PM, Reuti wrote:
> Am 23.04.2011 um 19:58 schrieb Ralph Castain:
>
>>
>> On Apr 23, 2011, at 11:55 AM, Pablo Lopez Rios wrote:
>>
What about setsid and pushing it in a new
seesion instead of using& in the script?
>>>
>>> :-) That works. Thanks!
>>>
>>> NB
Am 23.04.2011 um 19:58 schrieb Ralph Castain:
>
> On Apr 23, 2011, at 11:55 AM, Pablo Lopez Rios wrote:
>
>>> What about setsid and pushing it in a new
>>> seesion instead of using& in the script?
>>
>> :-) That works. Thanks!
>>
>> NB, the working script looks like:
>>
>> setsid bash -c "mp
Not directly, as in fg + Ctrl+C, but 'killall mpirun' or 'killall
command' works as usual. I wanted a script with the same effect as
running 'runscript & tail -f out' from the command line, and this is
exactly it.
On 23/04/11 18:58, Ralph Castain wrote:
On Apr 23, 2011, at 11:55 AM, Pablo Lop
Probably you are right in that if the executable in question actively
requests to trap SIGINT there is nothing you can do (short of running in
a new session as suggested by Reuti). But try the script in my first
email, or look at the output I printed; it works for other commands.
On 23/04/11 1
On Apr 23, 2011, at 11:55 AM, Pablo Lopez Rios wrote:
>> What about setsid and pushing it in a new
>> seesion instead of using& in the script?
>
> :-) That works. Thanks!
>
> NB, the working script looks like:
>
> setsid bash -c "mpirun command>& out"&
> tail -f out
>
Yes - but now you can
What about setsid and pushing it in a new
seesion instead of using& in the script?
:-) That works. Thanks!
NB, the working script looks like:
setsid bash -c "mpirun command>& out"&
tail -f out
Thanks,
Pablo
On 23/04/11 18:39, Reuti wrote:
Am 23.04.2011 um 19:33 schrieb Ralph Castain:
Am 23.04.2011 um 19:33 schrieb Ralph Castain:
> On Apr 23, 2011, at 10:40 AM, Pablo Lopez Rios wrote:
>
>>> I'm not sure what you are actually trying to accomplish
>>
>> I simply want a script that runs the equivalent of:
>>
>> mpirun command>& out&
>> tail -f out
>>
>> such that hitting Ctrl
On Apr 23, 2011, at 10:40 AM, Pablo Lopez Rios wrote:
>> I'm not sure what you are actually trying to accomplish
>
> I simply want a script that runs the equivalent of:
>
> mpirun command>& out&
> tail -f out
>
> such that hitting Ctrl+C stops tail but leaves mpirun running. I can
> certainl
I'm not sure what you are actually trying to accomplish
I simply want a script that runs the equivalent of:
mpirun command>& out&
tail -f out
such that hitting Ctrl+C stops tail but leaves mpirun running. I can certainly
do this without mpirun, it's not unreasonable to expect to be able to
Am 23.04.2011 um 17:07 schrieb Pablo Lopez Rios:
>> what about:
>> ( trap "" sigint; exec mpiexec ...)&
>
> Yup, that's included in the workarounds I tried. Tried again with your
> specific suggestion; no luck.
>
>> Well, maybe mpiexec is adjusting it on its own
>> again. This can be checked in
On Apr 23, 2011, at 9:11 AM, Pablo Lopez Rios wrote:
>> > Pressing Ctrl+C should stop tail -f, and the MPI job
>> > should continue.
>
>> I don't think that is true at all. When you hit ctrl-C,
>> every process executing in the script receives it. Mpirun
>> traps the ctrl-c and immediately ter
On Apr 23, 2011, at 9:07 AM, Pablo Lopez Rios wrote:
>> what about:
>> ( trap "" sigint; exec mpiexec ...)&
>
> Yup, that's included in the workarounds I tried. Tried again with your
> specific suggestion; no luck.
>
>> Well, maybe mpiexec is adjusting it on its own
>> again. This can be check
> Pressing Ctrl+C should stop tail -f, and the MPI job
> should continue.
I don't think that is true at all. When you hit ctrl-C,
every process executing in the script receives it. Mpirun
traps the ctrl-c and immediately terminates all running
MPI procs.
By "Ctrl+C should stop tail -f
what about:
( trap "" sigint; exec mpiexec ...)&
Yup, that's included in the workarounds I tried. Tried again with your specific
suggestion; no luck.
Well, maybe mpiexec is adjusting it on its own
again. This can be checked in /proc//status
The signal masks in /proc/$!/status are:
nomp
On Apr 23, 2011, at 6:20 AM, Reuti wrote:
> Hi,
>
> Am 23.04.2011 um 04:31 schrieb Pablo Lopez Rios:
>
>> I'm having a bit of a problem with wrapping mpirun in a script. The script
>> needs to run an MPI job in the background and tail -f the output. Pressing
>> Ctrl+C should stop tail -f, and
Hi,
Am 23.04.2011 um 04:31 schrieb Pablo Lopez Rios:
> I'm having a bit of a problem with wrapping mpirun in a script. The script
> needs to run an MPI job in the background and tail -f the output. Pressing
> Ctrl+C should stop tail -f, and the MPI job should continue. However mpirun
> seems t
19 matches
Mail list logo
