Yeah, the ldd output for Arch Linux is as follows:

        linux-vdso.so.1 (0x0000007fab461000)
        libopen-rte.so.40 => /usr/lib/openmpi/libopen-rte.so.40
(0x0000007fab374000)
        libopen-pal.so.40 => /usr/lib/openmpi/libopen-pal.so.40
(0x0000007fab296000)
        libc.so.6 => /usr/lib/libc.so.6 (0x0000007fab111000)
        /lib/ld-linux-aarch64.so.1 => /usr/lib/ld-linux-aarch64.so.1
(0x0000003000000000)
        libdl.so.2 => /usr/lib/libdl.so.2 (0x0000007fab0fd000)
        librt.so.1 => /usr/lib/librt.so.1 (0x0000007fab0e5000)
        libm.so.6 => /usr/lib/libm.so.6 (0x0000007fab039000)
        libutil.so.1 => /usr/lib/libutil.so.1 (0x0000007fab023000)
        libz.so.1 => /usr/lib/libz.so.1 (0x0000007faaffc000)
        libhwloc.so.15 => /usr/lib/libhwloc.so.15 (0x0000007faaf92000)
        libpthread.so.0 => /usr/lib/libpthread.so.0 (0x0000007faaf62000)
        libudev.so.1 => /usr/lib/libudev.so.1 (0x0000007faaf16000)


ldd output on Termux:

libandroid-shmem.so
libopen-rte.so
libopen-pal.so
libm.so
libdl.so
libc.so

On Thu, 25 Feb 2021, 13:46 John Hearns via users, <users@lists.open-mpi.org>
wrote:

> Perhaps an idiot question from me..   In both environments run   ldd <your
> executable>
> Are there any libraries missing?
>
> On Thu, 25 Feb 2021 at 05:36, Gilles Gouaillardet via users <
> users@lists.open-mpi.org> wrote:
>
>> Can you run
>>
>>
>> ifconfig
>>
>> or
>>
>> ip addr
>>
>>
>> in both Termux and ArchLinux for Termux?
>>
>>
>>
>> On 2/25/2021 2:00 PM, LINUS FERNANDES via users wrote:
>> >
>> > Why do I see the following error messages when executing |mpirun| on
>> > ArchLinux for Termux?
>> >
>> > The same program executes on Termux without any glitches.
>> >
>> > |@localhost:/data/data/com.termux/files/home[root@localhost home]
>> > mpirun --allow-run-as-root [localhost:06773] opal_ifinit:
>> > ioctl(SIOCGIFHWADDR) failed with errno=13 [localhost:06773]
>> > pmix_ifinit: ioctl(SIOCGIFHWADDR) failed with errno=13
>> > [localhost:06773] oob_tcp: problems getting address for index 83376
>> > (kernel index -1)
>> >
>> --------------------------------------------------------------------------
>> > No network interfaces were found for out-of-band communications. We
>> > require at least one available network for out-of-band messaging.|
>>
>

Reply via email to