Greetings, and thanks for your report!

Appears to be gentoo specific:

https://buildd.debian.org/status/package.php?p=gcl
https://buildd.debian.org/status/fetch.php?pkg=gcl&arch=x32&ver=2.6.14-12&stamp=1738620948&raw=0

If there is ssh access I'd be happy to take a look, otherwise I suggest
running the offending command in gdb and posting a backtrace.

Take care,

Waldek Hebisch <de...@fricas.org> writes:

> On Tue, Feb 04, 2025 at 10:34:46AM -0500, Camm Maguire wrote:
>> Greetings, and thanks so much for your feedback!
>> 
>> Thank you so much for pointing out that these test failures are new, I
>> did not know that.  I had been focusing on the 2.7 build, but will now
>> look at these so we have a clean build with both GCL versions.
>
> Is any of GCL versions supposed to run on X32.?  I tried Version_2_6_15pre
> in chroot with X32 gentoo (outside is kernel from Debian 12).  Configure
> reports 'x86_64-pc-linux-gnux32', build goes some time and later dies:
>
> Compiling 
> /home/hebisch/kompi/gcl-2.6.15pre/unixport/../pcl/gcl_pcl_defclass.lisp.
>
> Error: ERROR "Caught fatal error [memory may be damaged]"
> Fast links are on: do (si::use-fast-links nil) for debugging
> Signalled by COMPILE-FILE.
> ERROR "Caught fatal error [memory may be damaged]"
>
> Broken at COMPILE-FILE.  Type :H for Help.
>     1  Return to top level. 
> PCL>>make[1]: *** [makefile:35: gcl_pcl_boot.c] Error 255

-- 
Camm Maguire                                        c...@maguirefamily.org
==========================================================================
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah

Reply via email to