meta-openembedded/meta-oe
Khem Raj 7f9699e730
xmlrpc-c: Fix race condition triggered during symlink creation
This should fix race condition sometime seen in highly parallell builds

   | rm -f libxmlrpc_util.so.4
   | rm -f libxmlrpc_util.so.4
   | ln -s libxmlrpc_util.so.4.60 libxmlrpc_util.so.4
   | ln -s libxmlrpc_util.so.4.60 libxmlrpc_util.so.4
   | rm -f libxmlrpc_util.so
   | ln: failed to create symbolic link 'libxmlrpc_util.so.4': File exists
   | make[2]: *** [/home/kraj01/yoe/build/tmp/work/core2-64-yoe-linux/xmlrpc-c/1.60.03/git/stable/unix-common.mk:72: libxmlrpc_util.so.4] Error 1

Signed-off-by: Khem Raj <raj.khem@gmail.com>
Cc: Martin Jansa <Martin.Jansa@gmail.com>
2024-10-27 18:08:38 -07:00
..
classes fitimage: fix name of default configuration 2024-10-16 08:16:06 -07:00
conf ptest-packagelists-meta-oe.inc: Add tomlplusplus 2024-10-17 14:07:45 -07:00
dynamic-layers netplan: upgrade 1.1 -> 1.1.1 2024-10-21 20:54:47 -07:00
files
lib/oeqa/selftest/cases
licenses
recipes-benchmark fio: upgrade 3.37 -> 3.38 2024-10-10 12:53:49 -07:00
recipes-bsp fwupd: upgrade 1.9.24 -> 1.9.25 2024-09-30 07:34:22 -07:00
recipes-connectivity transmission: fix compliance checking 2024-10-15 20:39:55 -07:00
recipes-core dbus-broker: Add missing systemd user symlink 2024-10-21 20:54:48 -07:00
recipes-crypto cryptsetup: fix udev PACKAGECONFIG 2024-10-10 12:53:50 -07:00
recipes-dbs postgresql.inc: fix do_package_qa error 2024-10-24 05:52:20 -07:00
recipes-devtools xmlrpc-c: Fix race condition triggered during symlink creation 2024-10-27 18:08:38 -07:00
recipes-extended fluentbit: fix building with wasm support 2024-10-21 20:54:48 -07:00
recipes-gnome adw-gtk3: upgrade 5.4 -> 5.5 2024-10-14 09:52:24 -07:00
recipes-graphics graphviz: Disable perl support 2024-10-27 18:08:26 -07:00
recipes-kernel makedumpfile: Remove recipe 2024-10-15 08:15:36 -07:00
recipes-multimedia libplacebo: reorganize dependencies 2024-10-17 14:07:46 -07:00
recipes-navigation gpsd: condition the runtime dependence of pyserial on the pygps 2024-09-27 06:18:13 -07:00
recipes-networking/cyrus-sasl recipes: Start WORKDIR -> UNPACKDIR transition 2024-05-23 08:44:44 -07:00
recipes-printing cups-filters: include UPSTREAM_CHECK_URI to fix UNKNOWN_BROKEN status 2024-07-24 08:56:30 -07:00
recipes-security nmap: Fix off-by-one overflow in the IP protocol table. 2024-10-14 23:25:11 -07:00
recipes-shells zsh: update 5.8 -> 5.9 2024-08-23 22:35:10 -07:00
recipes-support libgpiod: update to v2.2 2024-10-24 07:06:31 -07:00
recipes-test catch2: upgrade 3.7.0 -> 3.7.1 2024-09-29 10:01:07 -07:00
COPYING.MIT
README.md README.md: Hint at "git request-pull" 2024-09-14 08:43:55 -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.

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