Wang Mingyu 6231fc0160 mpich: upgrade 4.0.2 -> 4.0.3
Changes in 4.0.3
=================
    Fix message queue dumping interface support
    Fix multinic usage in ch4:ofi
    Fix bug in MPI_WIN_CREATE in ch4:ucx when UCX >= 1.13.0
    Fix MPIR_pmi_barrier when PMI2 is used
    Fix ROMIO lazy mutex initialization
    Fix build with HIP support
    Fix potential dynamic process message mixups in ch3
    Add missing const to MPI_Pready_list array_of_partitions argument
    Add support for C++ datatypes even when the C++ binding is disabled
    Add support for Intel OneAPI compilers

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2022-11-14 11:55:59 -08:00
..
2022-08-24 08:26:55 -07:00
2022-10-27 08:55:20 -07:00

meta-oe
=======

This layer depends on:

URI: git://github.com/openembedded/openembedded-core.git
branch: master

luajit recipe requires host compiler to be able to generate 32bit code when target is 32bit
e.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed
packages to fullfit this might have different names on different host distributions
e.g. on archlinux based distributions install prerequisites like below

pacman -S lib32-gcc-libs lib32-glibc

Ubuntu
sudo apt-get install gcc-multilib linux-libc-dev:i386

Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'

When sending single patches, please use something like:
'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix="meta-oe][PATCH"'

You are encouraged to fork the mirror on GitHub https://github.com/openembedded/meta-openembedded
to share your patches, this is preferred for patch sets consisting of more than one patch.

Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well,
'git fetch <remote>' works the same on all of them. We recommend GitHub because it is free, easy
to use, has been proven to be reliable and has a really good web GUI.

layer maintainer: Khem Raj <raj.khem@gmail.com>