From: Sam S. <sd...@gn...> - 2010-03-19 15:40:24
|
Raymond Toy wrote: > On 3/19/10 9:52 AM, Sam Steingold wrote: >> Raymond Toy wrote: >>>> I think it is "generally known" that "newer gcc cannot compile clisp >>>> on sparc (solaris & linux)". >>>> https://sourceforge.net/tracker/?func=detail&aid=1575811&group_id=1355&atid=101355 >>>> >>>> >>>> I think what needs to be done is filing a gcc bug report or a clisp >>>> workaround. >>>> One has to be at least somewhat proficient with assembly for either >>>> task. >>>> Volunteers? >>> I volunteered last time to fix clisp, but I need some help with figuring >>> out some things, otherwise, it becomes way more work than I really want >>> to spend. >> thanks. >> >>> The solution was proposed to use %o0 and %o1 as the return results >>> instead of %g<n> that is currently used. >> this seems to be assembly-related. >> alas, I get the segfault in hashtabl.d even with SAFETY=3 which >> disables all assembly. > That's not good. How do I set SAFETY=3 when building clisp? either 1. ./configure --with-debug 2. edit Makefile and add -DSAFETY=3 to CFLAGS 3. "make CFLAGS+=-DSAFETY=3" 4. edit lispbibl.d note that you can use -DNO_ASM to disable assembly (see lispbibl.d) note that you must do "make clean; make" if you modify Makefile for the change to take effect. |