[Bug 257367] lang/racket: update to 8.2

From: <bugzilla-noreply_at_freebsd.org>
Date: Fri, 23 Jul 2021 22:20:58 UTC

            Bug ID: 257367
           Summary: lang/racket: update to 8.2
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
               URL: https://blog.racket-lang.org/2021/07/racket-v8-2.html
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: olgeni@FreeBSD.org
          Reporter: bsd@philippost.de
             Flags: maintainer-feedback?(olgeni@FreeBSD.org)
          Assignee: olgeni@FreeBSD.org

Created attachment 226645
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=226645&action=edit
Update lang/racket to version 8.2 (xz archive)

This patch updates lang/racket to version 8.2. It supersedes the work in Bug

Changes are as follows:
- add USES+=gmake
- introduce a single choice option which backend to build: BC or CS, where BC
is the legacy byte code implementation and CS the newer one based on Chez
Scheme. The FUTURES and JIT options are only allowed with BC=on. The
--enable-libffi and --enable-places configure options where moved to the BC
options, as the CS backend configure script does not provide these options.
- add a CHEZ_MACHTYPE which is currently only set for amd64, arm, arm64, i386
and powerpc (first introduced in Bug 255529)
- carry over the changes to the post-patch and post-install targets from Bug
- add a patch to src/cs/c/configure to allow building on amd64

I also carried over the patch to src/bc/sconfig.h from Bug 255529 since I do
not have access to FreeBSD machines with architectures other than amd64 and

Although the patched port builds and (de)installs fine locally, it would be
nice if someone could take a look a the pkg-plist. I am not quite sure if
everything is in order.

Potential issue: stage-qa complains about possible REINPLACE_CMD issues:
are not modified.
I didn't yet look into the cause of this or how to fix this.

You are receiving this mail because:
You are the assignee for the bug.