Wang Mingyu
855726266a
Changelog: =========== - Fix initialization in GPU-aware builds when no devices are present - Fix internal pmix.h header conflict when building with an external PMIx library. - Fix build issue with Slurm by removing dependency on libslurm and always using internal logic for parsing the Slurm hostfile. - Fix potential stale GPU IPC handle usage resulting in data corruption or crashes - Update XPMEM thresholds to avoid excessive buffer mapping overhead - Fix potential hang in ROMIO when setting info hints on certain files - Improved detection of incompatible PMI[x] client/server configuration - Fix use of PMIX_PREFIX attribute for certain versions of OpenPMIx - Fix Intel GPU output with MPIR_CVAR_DEBUG_SUMMARY - Fix F08 binding compilation with nvfortran - Fix line continuation Hydra's --configfile option - Fix valgrind uninitialized read warnings in ch3 - Fix missing mpixxx_opts.conf file with help text for mpicc and friends - Fixes for several compiler warnings Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
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.
Note, it is discouraged to send patches via GitHub pull request system. Such patches get less attention from developers and can be mishandled or not reviewed properly. Please use emails instead. For exemple, you can use 'git request-pull' to generate an email referencing your git repository.
Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well, 'git fetch ' 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