Cross build from RasPi5/Linux/Aarch64 to -m=rv64le FAILS [zlib]

Open
#918 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Domain
build-system

Research direction

Start with the attached rv64-make.out.txt and the rv64le/zlib configure step; the output says the compiler error reporting is too harsh and libz configure failed. Trace how Chez Scheme configures zlib for an rv64le cross build and identify the compiler error that stops configuration. Done means ./configure -m=rv64le followed by make completes successfully; the issue has no recent discussion, so check whether this is still reproducible.

Written by the indexing model from the issue text.

Description

Greetings,

It has been several years since I used Chez and am interested in a build for StarFive 2 [RV64G].

I am probably doing something incredibly stupid and would appreciate any help.

Thanks!
-KenD [Ken(dot)Dickey(at)Whidbey(dot)COM]

rv64-make.out.txt

=============
RasPiOS5:Arm64:~/Scheme/ChezScheme >>> ./configure -m=rv64le

Configuring for rv64le, and will create boot files via pb

RasPiOS5:Arm64:~/Scheme/ChezScheme >>> make

bin/zuo rv64le MAKE="make"
checking boot files for rv64le against pb
... ... ...
running pb/bin/pb/scheme to build xc-rv64le/boot/rv64le/heapcheck.inc
cd rv64le/zlib && ./configure
Compiler error reporting is too harsh for ./configure (perhaps remove -Werror).
** ./configure aborting.
libz configure failed
in build-one
in loop
in module->hash
make: *** [Makefile:8: build] Error 1

Dominant language
Scheme
Stars
7.4k
Forks
1k
Avg merge
1d 20h
Merged PRs (30d)
19

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cisco/ChezScheme

All issues in cisco/ChezScheme

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.