1b421ef711
These failures doesn't broken compiling, but not generate files under /usr/bin | userland@pumpkin3:/mnt/test/build_auh/tmp/work/core2-64-poky-linux/procmail/3.22/image/usr/bin$ ls | formail lockfile mailstat procmail part of error messages: | In file included from recommend.c:6: | includes.h:334:12: error: conflicting types for 'uname'; have 'int(void)' | 334 | extern int uname(); /* so we fix it :-) / | | ^~~~~ | In file included from sublib.c:13: | includes.h:334:12: error: conflicting types for 'uname'; have 'int(void)' | 334 | extern int uname(); / so we fix it :-) / | | ^~~~~ | In file included from procmail.h:3, | from procmail.c:20: | includes.h:334:12: error: conflicting types for 'uname'; have 'int(void)' | 334 | extern int uname(); / so we fix it :-) */ | | ^~~~~ | In file included from includes.h:67: | /datadrive/ubinux/workdir/build-dir/202506/build-ubinux-armv8/tmp/work/aarch64-ubinux-linux/procmail/3.22/recipe-sysroot/usr/include/sys/utsname.h:81:12: note: previous declaration of 'uname' with type 'int(struct utsname *)' | 81 | extern int uname (struct utsname *__name) _THROW; | | ^~~~~ | In file included from includes.h:67: | /datadrive/ubinux/workdir/build-dir/202506/build-ubinux-armv8/tmp/work/aarch64-ubinux-linux/procmail/3.22/recipe-sysroot/usr/include/sys/utsname.h:81:12: note: previous declaration of 'uname' with type 'int(struct utsname )' | 81 | extern int uname (struct utsname _name) THROW; | | ^~~~~ | In file included from includes.h:67: | /datadrive/ubinux/workdir/build-dir/202506/build-ubinux-armv8/tmp/work/aarch64-ubinux-linux/procmail/3.22/recipe-sysroot/usr/include/sys/utsname.h:81:12: note: previous declaration of 'uname' with type 'int(struct utsname )' | 81 | extern int uname (struct utsname __name) __THROW; | | ^~~~~ | In file included from includes.h:67: | /datadrive/ubinux/workdir/build-dir/202506/build-ubinux-armv8/tmp/work/aarch64-ubinux-linux/procmail/3.22/recipe-sysroot/usr/include/sys/utsname.h:81:12: note: previous declaration of 'uname' with type 'int(struct utsname )' | 81 | extern int uname (struct utsname __name) __THROW; | | ^~~~~ | recommend.c: In function 'main': | recommend.c:15:5: warning: old-style function definition [-Wold-style-definition] | 15 | int main(argc,argv)const int argc;const charconst argv[]; | | ^~~~ | procmail.c: In function 'savepass': | procmail.c:71:22: warning: old-style function definition [-Wold-style-definition] | 71 | static auth_identitysavepass(spass,uid)auth_identityconst spass; | | ^~~~~~~~ | procmail.c:76:12: error: too many arguments to function 'auth_finduid'; expected 0, have 2 | 76 | if(tpass=auth_finduid(uid,0)) / save by copying */ | | ^~~~~~~~~~~~ ~~~ | In file included from procmail.c:36: | authenticate.h:15:3: note: declared here | 15 | auth_finduid Q((const uid_t uid,const int sock)); | | ^~~~~~~~~~~~ | procmail.c: In function 'main': | procmail.c:97:5: warning: old-style function definition [-Wold-style-definition] | 97 | int main(argc,argv)int argc;const charconst argv[]; | | ^~~~ | procmail.c:212:9: error: too many arguments to function 'checkprivFrom'; expected 0, have 3 | 212 | checkprivFrom(euid,passinvk?auth_username(passinvk):0,override); | | ^~~~~~~~~~~~~~ ~~~~ | In file included from procmail.c:41: | from.h:9:2: note: declared here | 9 | checkprivFrom Q((uid_t euid,const charlogname,int override)); | | ^~~~~~~~~~~~~~ | procmail.c:213:9: error: too many arguments to function 'doumask'; expected 0, have 1 | 213 | doumask(INIT_UMASK); / allowed to set the From line? */ | | ^~~~~~~ Signed-off-by: Liu Yiding <liuyd.fnst@fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> |
||
|---|---|---|
| .. | ||
| classes | ||
| conf | ||
| dynamic-layers | ||
| files | ||
| lib/oeqa/selftest/cases | ||
| licenses | ||
| recipes-benchmark | ||
| recipes-bsp | ||
| recipes-connectivity | ||
| recipes-core | ||
| recipes-crypto | ||
| recipes-dbs | ||
| recipes-devtools | ||
| recipes-extended | ||
| recipes-gnome | ||
| recipes-graphics | ||
| recipes-kernel | ||
| recipes-multimedia | ||
| recipes-navigation | ||
| recipes-networking/cyrus-sasl | ||
| recipes-printing | ||
| recipes-security | ||
| recipes-shells | ||
| recipes-support | ||
| recipes-test | ||
| COPYING.MIT | ||
| README.md | ||
| SECURITY.md | ||
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