Hello Sebastian, Sebastian <[email protected]> wrote: |I'm trying to build s-nail from official repo |(https://projects.archlinux.org/svntogit/packages.git) but \ |whole build stops |on test behave:s/mime:sign/verify: ... it just spins for many hours and |nothing. Does anyone meet that kind of behaviour on ARMV7(hard float) |architecture?
Thanks for reporting the issue! I must admit that i do not have any ARM machine. Yes that is a shame, it is the cleaner architecture i think. |Logs from makepkg with problematic section | |Code: Select all | ==> Starting check()... | make[1]: Entering directory '/home/h3x0r/arch_rebuild_dir/s-nail/src/s- |nail-14.7.10' 14.7.10? Shouldn't that be v14.7.11 (in PKGBUILD since 2015-01-05)? I also must admit i've never fiddled with the Arch Linux package system myself, Gaetan (Gaetan Bisson, the Arch Linux maintainer) always reported any problems, and sometimes i even got them right.. | Building.. | . CC : /usr/lib/distcc/bin/gcc | . CFLAGS : -march=armv7ve -mfloat-abi=hard -mfpu=neon-vfpv4 \ | -mcpu=cortex- |a7 -mtune=cortex-a7 -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 - |D_FORTIFY_SOURCE=2 | . INCLUDES: | . LDFLAGS : -Wl,-O1,--sort-common,--as-needed,-z,relro | . LIBS : -lssl -lcrypto -lssl -lcrypto -lgssapi_krb5 \ | -lkrb5 -lk5crypto |-lcom_err -lidn | Running test, please wait | ./cc-test.sh: line 28: warning: setlocale: LC_ALL: cannot change locale |(en_US.UTF-8): No such file or directory | behave:001: ok | behave:if-normal: ok | behave:if-regex: ok | behave:s/mime: .. generating test key and certificate .. | behave:s/mime:sign/verify: <------------- IT STOPS HERE, \ | CPU AROUND 100% Ugly. I have never seen this on my own. |In top i can see that mail (process) is working when this \ |test is launched, it |occupied one core for around 100%. Well. Assumed that the OpenSSL tests pass on ARM i would presume a miscompilation. You could try compiling this with -O1 not -O2, or compile S-nail apart from the Arch Linux package system and check wether a plain default "make" and/or "make devel" followed by "make test" gets it right. If this still loops then it would be extremely cool if you could kill an endlessly looping S-nail that was produced via "make devel" (or at least compiled with WANT_DEBUG=1 set), collect the output in a file and send it over via mail! Also it would be nice to see possible compiler messages, if any, none such for all compilers that i have around. For now i assume a miscompilation that may well go away with the next compiler update, or has to be worked around by adjusting compiler flags. Unfortunately the S-nail build system doesn't allow adjusting flags on a per-file base, so that the flag adjustment would affect them all.. :( --steffen ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ S-nail-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/s-nail-users
