On Wed, Jun 5, 2013 at 10:14 AM, Camm Maguire wrote:
> Greetings!
>
> 2.6.8 and below, fixnum == (signed-byte 32), so on 64bit machines,
> intptr_t will be (unsigned-byte 64), and a bignum.
OK, thanks. when writing FFI code, e.g. with defentry, what type
should I use for intptr_t? Just intptr_t
On Wed, Jun 5, 2013 at 9:26 AM, Jerry James wrote:
> OK, so ignore the email I just sent moments ago. It had the same
> effect as this patch, i.e., disabling sgbc so that maxima doesn't try
> to use it. I've got a gcl build with --enable-debug going now. Once
> it is done, I'll attempt the maxi
On Wed, Jun 5, 2013 at 8:59 AM, Camm Maguire wrote:
> Greetings, and thanks so much for your report! It would be great if you
> could configure with --enable-debug and provide the excellent gdb stack
> trace you do now. But from what I can gather, the relevant cvs change
> is:
OK, so ignore the
Greetings!
2.6.8 and below, fixnum == (signed-byte 32), so on 64bit machines,
intptr_t will be (unsigned-byte 64), and a bignum.
2.6.9 and higher, intptr_t will be fixnum, i.e. a machine long, on all
platforms.
Of the patches I mentioned earlier for 2.6.9, 64bit fixnums is the
simplest. If the
On Tue, Jun 4, 2013 at 4:34 PM, Jerry James wrote:
> I built the latest 2.6.8pre from CVS a few days ago for Fedora
> Rawhide. Now it is segfaulting while building maxima:
I looked through the diff from the 26 Jan 2013 snapshot to current CVS
head to see if I could spot something that might be r
Greetings, and thanks so much for your report! It would be great if you
could configure with --enable-debug and provide the excellent gdb stack
trace you do now. But from what I can gather, the relevant cvs change
is:
--- gclttto/o/sgbc.c2010-10-25 19:51:33.0 +
+++ gclttt/o/sgbc.
