Arch Linux User Repository

It's an upstream issue with a simple fix that will be merged soon, see https://github.com/andmarti1424/sc-im/issues/872

@XXXJJJPPP I can replicate this on my machine, although I didn't try a clean chroot. You might give that a try.

I actually don't use this program any more, so I'm disowning.

If you can't solve the issue, then you could try posting upstream. Good luck!

In file included from formats/ods.c:51: /usr/include/zip.h:389:67: note: declared here 389 | ZIP_DEPRECATED("use 'zip_error_strerror' instead") ZIP_EXTERN int zip_error_to_str(char _Nonnull, zip_uint64_t, int, int); | ^~~~ formats/ods.c:97:28: error: implicit declaration of function ‘malloc’ [-Wimplicit-function-declaration] 97 | content = (char ) malloc(sb_content.size); | ^~ formats/ods.c:58:1: note: include ‘<stdlib.h>’ or provide a declaration of ‘malloc’ 57 | #include "../utils/string.h" +++ |+#include <stdlib.h> 58 | #endif formats/ods.c:97:28: warning: incompatible implicit declaration of built-in function ‘malloc’ [-Wbuiltin-declaration-mismatch] 97 | content = (char ) malloc(sb_content.size); | ^~ formats/ods.c:97:28: note: include ‘<stdlib.h>’ or provide a declaration of ‘malloc’ formats/ods.c:101:13: error: implicit declaration of function ‘free’ [-Wimplicit-function-declaration] 101 | free(content); | ^~ formats/ods.c:101:13: note: include ‘<stdlib.h>’ or provide a declaration of ‘free’ formats/ods.c:101:13: warning: incompatible implicit declaration of built-in function ‘free’ [-Wbuiltin-declaration-mismatch] formats/ods.c:101:13: note: include ‘<stdlib.h>’ or provide a declaration of ‘free’ formats/ods.c:120:30: warning: incompatible implicit declaration of built-in function ‘free’ [-Wbuiltin-declaration-mismatch] 120 | if (content != NULL) free(content); | ^~ formats/ods.c:120:30: note: include ‘<stdlib.h>’ or provide a declaration of ‘free’ formats/ods.c:168:24: warning: incompatible implicit declaration of built-in function ‘free’ [-Wbuiltin-declaration-mismatch] 168 | free(strf); | ^~~~ formats/ods.c:168:24: note: include ‘<stdlib.h>’ or provide a declaration of ‘free’ formats/ods.c:211:35: error: implicit declaration of function ‘atof’ [-Wimplicit-function-declaration] 211 | double l = atof((char ) value); | ^~ formats/ods.c:223:20: warning: incompatible implicit declaration of built-in function ‘free’ [-Wbuiltin-declaration-mismatch] 223 | free(st); | ^~ formats/ods.c:223:20: note: include ‘<stdlib.h>’ or provide a declaration of ‘free’ formats/ods.c:243:5: warning: incompatible implicit declaration of built-in function ‘free’ [-Wbuiltin-declaration-mismatch] 243 | free(content); | ^~~~ formats/ods.c:243:5: note: include ‘<stdlib.h>’ or provide a declaration of ‘free’ make: *** [<builtin>: formats/ods.o] Error 1 ==> ERROR: A failure occurred in build(). Aborting... -> error making: sc-im-exit status 4 -> Failed to install the following packages. Manual intervention is required: sc-im - exit status 4 I encounted this error installing sc-im using yay both on wsl2 and local machine
after using archinstall(My English is poor, hope you can understand my meaning : )

Thanks @AlcovesSap. I've edited the PKGBUILD with a change that hopefully fixes this.

In latest pacman upgrade,the /etc/makepkg.conf has

CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions \
        -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security \

as default.(Commit 71d2dd10 RFC 17: Increase _FORTIFY_SOURCE level to 3)

I believe the flag -D_FORTIFY_SOURCE=3 makes sc-im easy to crash. In my case with

***buffer overflow detected***:terminated
Aborted (core dumped)

Changing the flag back to -D_FORTIFY_SOURCE=2 and rebuild sc-im save my problem.

If anyone has the same issue.Hope this will help. :)

@nesk_aur base-devel, which includes bison and patch, is assumed to be installed when building packages. As per the wiki, this should not be in the makedepends array.

Thanks for the information on aarch64. I've added it to the PKGBUILD.

Additional build-time deps: bison, patch. This pkg builds fine on aarch64.

@Rhinoceros Thanks!

@Strider85 You probably need to look upstream. It's likely not a packaging error. I just searched and found this.

Hi. I was getting the faulty segmentation error for many random cases (for external functions, mainly), even with the "external_functions" option set. Worked fine after downgrade to 0.8.1.0.