Arch Linux User Repository

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.

One of the maintainers here.

I used to work at Apple and couldn't do any FOSS work, but I should be able to help out starting next week now that I've left the company.

@CodingCellist Thanks. You are now a maintainer.

@dgeibi If you need people, I am also happy to help maintain this package. I co-maintain the idris2 package, which depends on the chez-scheme package.

@GunpowderGuy Sorry for delaying updates, I'll take care of that in a couple of days.

@dgeibi I think I can keep maintaining it.

Sorry, I haven't used arch linux for a long time. @GunpowderGuy, You are a maintiner of the package now.

@dgeibi @taekyung @jaseemabid the package is still bugged, the checksum got wrong: https://github.com/cisco/ChezScheme/issues/605

Several people are reporting that the validity check fails when installing this package @dgeibi Edit: this is the problem https://github.com/cisco/ChezScheme/issues/605

I changed the binary name from scheme to chez.

Thanks @defty.

This is a patch to update to 9.5.6, canonicalize the license name, and install to chez and chez-script:

diff --git a/PKGBUILD b/PKGBUILD
index 0fb6596..8a7012b 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -2,26 +2,26 @@
 # Maintainer: Taekyung Kim <Taekyung.Kim.Maths@gmail.com>

 pkgname=chez-scheme
-pkgver=9.5.4
-pkgrel=2
+pkgver=9.5.6
+pkgrel=1
 pkgdesc="Chez Scheme is a compiler and run-time system for the language of the Revised^6 Report on Scheme (R6RS), with numerous extensions."
 arch=(i686 x86_64)
 url="https://github.com/cisco/ChezScheme"
 depends=()
-license=('APL')
+license=('Apache')
 depends=('ncurses' 'libx11' 'libutil-linux')
 conflicts=('petite-chez-scheme' 'chez-scheme-git')
 replaces=('petite-chez-scheme' 'chez-scheme-git')
 source=("https://github.com/cisco/ChezScheme/releases/download/v$pkgver/csv$pkgver.tar.gz")
-sha1sums=('867c82cc3879e37dcb0188ef1c08915afaac42a9')
+sha256sums=('6b3d1d111c6c47a4e51b500b30f4c29efd339e414f6ace743cff6d08a0dacaae')
 _archivename=csv$pkgver

 build() {
   cd "$srcdir/${_archivename}"
-  ./configure --installprefix=/usr --temproot=$pkgdir --threads
+  ./configure --installprefix=/usr --temproot=$pkgdir --installschemename=chez --installscriptname=chez-script --threads
 }

 package() {
   cd "${srcdir}/${_archivename}"
-  make install DESTDIR="$pkgdir" InstallSchemeName=scheme
+  make install DESTDIR="$pkgdir"
 }

Related update: https://aur.archlinux.org/packages/idris2/#comment-826542

Chez is not "standard" scheme, and there will never be one. Users should specify the scheme based on their choice.

@joshu, apologies, it seems the change you proposed in your original comment is "more correct" from looking into other Scheme implementations (ypsilon-scheme is invoked as ypsilon, scm-scheme as scm, chibi-scheme as chibi, etc.). So invoking chez-scheme as chez or chez-scheme would seemingly be more consistent with other implementations. Unfortunately, Idris2 seems to rely on chez-scheme being called scheme beyond what is configurable in the PKGBUILD, which complicates things a bit.

@taekyung, yes there doesn't seem to be an ideal solution. Both have their ups and down, but having a clash in the binary names is definitely not desirable. Based on the pattern above, maybe your change to chez-scheme was "correct". If you don't want to constantly be changing things around, however, that's fair enough. Sorry for confusing things. I realise maintaining a package can be a lot of work, especially when other packages rely on it.

@joshu, @CodingCellist, thank you for your input, and sorry for making inconveniences and confusion about this package as a maintainer. Apparently, changing PKGBUILD file in idris2 package doesn't fix the problem. So I think it is better to revert the binary name to scheme in order for making no more confusion at the moment.

However would agree on @joshu's comment that having the same binary name for MIT and chez schemes is not desirable at all, given that scheme programmers tend to install many implementations on their computer for testing, etc.

@CodingCellist, it's an interesting point. One could argue that it's a bigger issue to have both MIT and chez installing a binary with a common name (are other implementations also doing the same? I only have gambit installed and its binary is gambitc). It looks like it's straightforward to patch idris2's PKGBUILD to use a different binary name, and loko would require a change to its makefile.

Anyway, I have no preference personally for how this package is installed, so for anyone else reading:

• if this package gets reverted it's simple to patch the PKGBUILD to get around the problem of conflicting MIT/chez scheme installs. See my previous comment https://aur.archlinux.org/packages/chez-scheme/#comment-746465

@taekyung, the renaming in the latest release breaks the packages listed under "Required by". They expect, both at compile-time and run-time, to be able to invoke scheme as the executable for Chez Scheme.

Although I appreciate the conflicts with MIT/GNU Scheme, if packages which list this as a requirement still break when it is installed, I would argue that is a more serious concern than the conflict between two packages providing alternative Scheme implementations. If nothing else, the GitHub issue that @joshu links to does mention that Chez Scheme has been referred to as scheme since before its release in 1985 (and as such precedes MIT/GNU Scheme chronologically). The discussion in the GitHub issue seems to suggest anyone requiring a different executable name to install from source, specifying InstallSchemeName, which I would prefer rather than the package deciding this.

Chez Scheme 9.5.4 was released earlier this week. Here is a patch:

diff --git a/PKGBUILD b/PKGBUILD
index 19bba36..d7577d9 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -2,8 +2,8 @@
 # Maintainer: Taekyung Kim <Taekyung.Kim.Maths@gmail.com>

 pkgname=chez-scheme
-pkgver=9.5.2
-pkgrel=3
+pkgver=9.5.4
+pkgrel=1
 pkgdesc="Chez Scheme is a compiler and run-time system for the language of the Revised^6 Report on Scheme (R6RS), with numerous extensions."
 arch=(i686 x86_64)
 url="https://github.com/cisco/ChezScheme"
@@ -13,7 +13,7 @@ depends=('ncurses' 'libx11' 'libutil-linux')
 conflicts=('petite-chez-scheme' 'chez-scheme-git')
 replaces=('petite-chez-scheme' 'chez-scheme-git')
 source=("https://github.com/cisco/ChezScheme/releases/download/v$pkgver/csv$pkgver.tar.gz")
-sha1sums=('2d07be6aa99e66365864d96f538e12d3c5098957')
+sha256sums=('e5baa3702670542c734a32ad5e91ddbc3477a5b2079278ffb86fd58fd6c5079f')
 _archivename=csv$pkgver

 build() {

I got a conflict with mit-scheme, whose executable is at /usr/bin/scheme.

Fixed by adding InstallSchemeName=chez-scheme to the make install call in package().

as noted by Dybvig here

@owari and @ryn1x, thank you for your comments. Actually, x(org)proto is already in the dependency of libx11 and the upstream building guide do not say anything about x(org)proto but libx11, it is okay to remove it from make-dependency completely. Also, as parts of the base-devel package, binutils and make are not recommended to be in makedepends. So I also remove them. Thanks.

Please update xproto to xorgproto in PKGBUILD

makedepends=('binutils' 'make' 'ncurses' 'libx11' 'xorgproto')

It seems that makepkg could not detect xorgproto as a make dependency. I changed the make dependency xproto to xorgproto, then the error is gone and the compliation is done.

Thanks @xuanruiqi, I've updated the PKGBUILD file

I recommend adding --threads after ./configure, which will compile in threading support that is useful to some people.

Glad to see this package updated. I can help maintain this package too.

I can successfully install version 9.5.2 using the following PKGBUILD file. Maintainers, please update the package?

pkgname='chez-scheme'
pkgver=9.5.2
pkgrel=1
pkgdesc="Chez Scheme is a compiler and run-time system for the language of the Revised^6 Report on Scheme (R6RS), with numerous extensions."
arch=(i686 x86_64)
url="https://github.com/cisco/ChezScheme"
depends=()
license=('APL')
makedepends=('binutils' 'make' 'ncurses' 'libx11' 'xproto')
conflicts=('petite-chez-scheme' 'chez-scheme-git')
replaces=('petite-chez-scheme' 'chez-scheme-git')
source=("https://github.com/cisco/ChezScheme/releases/download/v$pkgver/csv$pkgver.tar.gz")
sha256sums=('7189f839f63e7f0e58277138f5873f91c23eae0706a5bfd7081dab5289268f10')
_archivename=csv$pkgver


build() {
  cd "${srcdir}/${_archivename}"

  ./configure --installprefix=/usr --temproot=$pkgdir
}

package() {
  cd "${srcdir}/${_archivename}"
  make install DESTDIR="$pkgdir"
}

@jumper149 I wouldn't say this package isn't properly maintained. These issues seem to be prevalent with recent changes to GCC. To my thinking, we're attempting to compile software on a new GCC, software that was written without the new GCC warnings into account. We can't fault the maintainer of the AUR package.

But the software authors are fixing the issues, it seems. The new GCC warnings have been getting plenty of attention, it seems, as I searched for similar errors.

Thanks for pointing out the -git package. It compiles and runs smoothly.

Im having the same compilation error as @bwmcn. Is this package maintained properly or is it better to just go with the '-git' version? @bwmcn there is also the 'chez-scheme-git' which is compiling fine (needs to download 1 GB of repositories tho)

Getting a compilation failure. Searching for similar errors suggests that this is related to the new `warnings' produced by GCC. Any insights appreciated.

prim5.c: In function ‘s_showalloc’:
prim5.c:329:85: error: ‘td of ’ directive output may be truncated writing 6 bytes into a region of size between 0 and 18 [-Werror=format-truncation=]
    snprintf(fmtbuf, FMTBUFSIZE, "%%#0%dtx %%#0%dtx (+ %%#0%dtx bytes @ %%#0%dtx) %%%dtd of %%%dtd\n", 
                                                                                      ^~~~~~  
In file included from /usr/include/stdio.h:862,  
                 from system.h:24,  
                 from prim5.c:17:  
/usr/include/bits/stdio2.h:64:10: note: ‘__builtin___snprintf_chk’ output between 54 and 112 bytes into a destination of size 60  
return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,  
      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~  
    __bos (__s), __fmt, __va_arg_pack ());  
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~