Jayanth Othayoth
77397ccbb9
Added version bump to fix the ipmitool build issue. Build failure details available as part of this commit. https://codeberg.org/IPMITool/ipmitool/commit/bf774149ae7f74c12164a5b021b23520c5ca4016 Additional commit included in this version bump are below. Alexander Amelkin (1): man: Remove duplicate description for -b and -B Alexander Filippov (3): Remove trailing spaces replace HAS_PRAGMA_PACK macros imb: refix structure packing Howitzer105mm (4): Establish a uniform structure packing syntax ipmievd: Eliminate a possible command line overrun (#27) open: Eliminate buffer overrun (#24) lan: Clean compile time warning from LAN authentication (#22) István Donkó (1): doc: fix a small typo in `print_user_usage` Johnathan Mantey (1): fru: Fix a typo causing compilation to fail (#37) Miao Wang (1): lan: fix lan print fails on unsupported parameters bbradley (1): chassis: Partial revert of 6e037d6bfbb (#19) Signed-off-by: Jayanth Othayoth <ojayanth@gmail.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