Sam Steingold writes:
> > building on fedora x64 could be fixed.
> is this amd or intel?
> > ./configure CC='gcc -m64' --cbc build-plain
> > ...
> > (TYPE-OF (SETQ CALLBACKF (WITH-C-VAR (X 'IDFUN #'CALLBACK) X)))
> > trampoline: Out of virtual memory!
> > Exiting on signal 6
> this is with the failed ffcall build, right?
> (reported as https://savannah.gnu.org/bugs/?24282, btw, could you please check
> if this is the same as https://savannah.gnu.org/bugs/?22436 ?
Doesn't look the same to me - one gets a segfault, the other doesn't.
BTW I'm getting certificate errors on https urls above - using http
> your crash is in avcall and 22436 is in callback, but I wonder if they are
> still related).
> also, I wonder if the patch in https://savannah.gnu.org/bugs/index.php?22130
> would make any difference...
I guess you mean
That seems to change avcall-ia64.s, and I hope that wouldn't make any
difference to me.
Also, I'm not sure how to apply the patch - haven't done this sort of
$ [2008-09-26 09:50:01 root@... ~/clisp]
$ patch -i /tmp/clisp-2.39-ia64.dif
can't find file to patch at input line 3
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
|+++ ffcall/avcall/avcall-ia64.s 2006-07-21 16:24:20.000000000
File to patch: ^C
$ ls -l ffcall/avcall/avcall-ia64.s
-rw-r--r-- 1 root root 11079 2001-01-29 05:30
[2008-09-26 09:55:24 root@... ~/clisp]
If you want me to go ahead, I will, but tell me how.
> > $ ./configure CC='gcc -m64' --without-ffcall --cbc build-dir
> > ...
> > (READ-LINE *SOCKET-1*)
> > [SIMPLE-OS-ERROR]:
> > *** - handle_fault error2 ! address = 0x0 not in
> > [0x333fab000,0x3343f91e8) !
> > SIGSEGV cannot be cured. Fault address = 0x0.
> if you have cycles to burn, it would be nice to use the binary
> search to find out if this is a new bug.
Well, I don't have many spare cycles, but this machine does.
> i.e., does "cvs up -D 2005-01-01 && "/configure CC='gcc -m64' --without-ffcall
> --cbc build-2005-01-01" fail? if it does not, try "cvs up -D 2007-01-01" and
> proceed with the binary search to pinpoint the culprit.
> if older versions do not build either, we have to treat this as a "new
> platform" and follow the porting instructions in unix/PLATFORMS.
Wow, that's pretty far back.
All sorts of things might not work.
$ ./configure CC='gcc -m64' --without-ffcall --cbc build-2005-01-01
./configure: invalid argument --cbc
./configure: Try `./configure --help'
[2008-09-26 10:04:55 root@... ~/clisp/clisp]
$ ./configure CC='gcc -m64' --without-ffcall build-2005-01-01
./configure: line 324: test: too many arguments
chmod: invalid option -- 'm'
Try `chmod --help' for more information.
[2008-09-26 10:05:23 root@... ~/clisp/clisp]
will try 2007...