-
Notifications
You must be signed in to change notification settings - Fork 126
Description
Attempting to install clasp
via Roswell fails because the build process still depends on the externals-clasp repository, which has been archived on GitHub and is no longer actively maintained. The make
step crashes with error code 139
(segmentation fault) during the build.
To reproduce
Steps to reproduce:
ros install clasp
Result:
- Roswell downloads/extracts
externals-clasp
(commit8ad13ba592230f13d11c13b0498844ca7083ef
) - During
make
, it segfaults with error code139
- The install fails, and no
clasp
binary is installed
Error Output
The installation process shows two cascading failures:
- externals-clasp+ segfault (error code 139):
Skip downloading https://github.com/gos-k/externals-clasp/archive/8ad13ba592230f13d11c13b2b0498844ca7083ef.tar.gz
Extracting archive:/home/arandre/.roswell/archives/externals-clasp-6.0.1.tar.gz
Subprocess with command "make" exited with error code 139
- clasp installation failure (depends on step 1):
Subprocess with command "/usr/sbin/ros install externals-clasp+/6.0.1" exited with error code 1
The process shows it's trying to install clasp/2019-09-29
but fails because the externals-clasp+/6.0.1
dependency build crashed.
Full error backtrace shows the segfault occurs during the make process in ROSWELL.INSTALL.EXTERNALS-CLASP+::EXTERNALS-CLASP-MAKE
.
Environment
- OS: (Host) Windows 11 Home: (WSL2) Arch Linux
- Roswell version: roswell 24.10.115
- GCC version: gcc (GCC) 14.2.1 20240910
- libcurl version: libcurl=8.11.0
make
version: GNU Make 4.4.1
Probable Cause
- The GitHub repo
externals-clasp
was archived on June 9, 2024, is read-only, and is no longer maintained - The archived code appears to have compatibility issues with current build environments (modern GCC, etc.)
- Because it's archived, no fixes can be pushed there, but the Roswell install script still depends on it
- This makes
ros install clasp
effectively unmaintainable without pointing to a different source
Verification
which clasp
# no clasp in PATH after failed install
# Re-downloading doesn't help (build issue, not download corruption):
ros install clasp download.force=t
# Still fails with same segfault
Proposed Solutions
Roswell should either:
- Update the clasp install script to pull from an active fork or official clasp distribution
- Provide updated build scripts that work with current environments
- Remove the clasp installer if it's no longer supported and mark it as unsupported
- Host a maintained mirror of externals-clasp so the install workflow continues to function
Offer
If clasp is essentially un-buildable with the current setup, I would rather be notified of this, and I can fork and maintain the build script(s) myself. I really would prefer to be able to ros install clasp
, so I would have no problem doing this if the official maintainers don't want to maintain the build scripts.
Additional Context
- This likely affects all users trying to install clasp via Roswell on modern Linux distributions
- The issue appears to be compatibility between the 2019-era archived code and current toolchains
- Alternative clasp installation methods may work, but Roswell integration is important