Arch Linux User Repository

gcc -march=native -mtune=native -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -DZUO_LIB_PATH='"'".././zuo/lib"'"' -o bin/zuo ./zuo/zuo.c ./zuo/zuo.c: In function ‘zuo_init_signal_handler’: ./zuo/zuo.c:5585:17: error: assignment to ‘__sighandler_t’ {aka ‘void ()(int)’} from incompatible pointer type ‘void ()(void)’ [-Wincompatible-pointer-types] 5585 | sa.sa_handler = zuo_signal_received; | ^ ./zuo/zuo.c:5565:13: note: ‘zuo_signal_received’ declared here 5565 | static void zuo_signal_received() { | ^ In file included from /usr/include/sys/wait.h:36, from ./zuo/zuo.c:23: /usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here 72 | typedef void (*__sighandler_t) (int); | ^~~~ make: *** [Makefile:167: bin/zuo] Error 1 ==> ERROR: A failure occurred in build(). Aborting... error: failed to build 'chez-scheme-10.1.0-1'

can you please remove 'replaces chez-scheme-git' as per https://wiki.archlinux.org/title/AUR_submission_guidelines - 1.1

it has also been updated: https://aur.archlinux.org/packages/chez-scheme-git

@maoif Thanks for raising this. Should be updated now.

@ecraven That definitely sounds like it would be good to have. It seems like it should be on by default (https://github.com/cisco/ChezScheme/commit/be33b28cff859ec3580a0435f4622c0218d70a38) ? Unless I am missing something. If turns out it is no longer on by default, so long as nobody else has any objections — I'll wait ~2 weeks and see — I'll update the PKGBUILD and revision.

Could you be persuaded to add --kernelobj to the ./configure line? This would also build several additional files that won't hurt, but are necessary to use https://github.com/gwatt/chez-exe (which is great for creating stand-alone executables with chez).

@taekyung Ah sorry! Didn't mean to snipe your work

Afaict based on the GH repo, x11 is necessary for more than just the docs 1,2. But there is a --disable-x11 flag which we could add to the configure script 3 and then cut that dependency (or move it to an optdepends)? : )

re: glibc -- I think that should definitely be on there as it probably won't build or run without it. I don't actually know if you could have the build tools necessary without also having glibc installed, but since Chez requires it, it should be listed as a dependency imo

@CodingCellist I was working on this, but you got it first! Thank you anyway!

By the way, the upstream documentation explicitly says it requires x11, but namcap complains it is not necessary. After reading through the documentation more carefully, I suspect that x11 dependency is only for documentation build (make doc). I think this can be removed. Moreover, in the current dependency list, glibc seems missing (again, namcap figured that out). What's your opinion on this?

Hey @jonathon and @zenten, sorry for not getting back. Does the issue repro on the latest release (9.6.2-1)?

Is there any progress on this? It's still not working on my system, same error.

With the new makepkg defaults including LTO this will fail to compile. The PKGBUILD needs either:

@@ -12,6 +12,7 @@ license=('Apache')
 depends=('ncurses' 'libx11' 'libutil-linux')
 conflicts=('petite-chez-scheme' 'chez-scheme-git')
 replaces=('petite-chez-scheme' 'chez-scheme-git')
+options=(!lto)
 source=("https://github.com/cisco/ChezScheme/releases/download/v$pkgver/csv$pkgver.tar.gz")
 sha256sums=('9aaa208c63eda8edfad72566790db0f9cedc7c6bb860157c400c98e22583c6b4')
 _archivename=csv$pkgver

to disable LTO, or:

@@ -23,5 +23,5 @@ build() {

 package() {
   cd "${srcdir}/${_archivename}"
-  make install DESTDIR="$pkgdir"
+  make install CFLAGS+=" -ffat-lto-objects" DESTDIR="$pkgdir"
 }

to make sure compilation succeeds with LTO intact.