> Dear Camm Maguire,
> First, I downloaded gcl from cvs after release 2.6.7-97, and built it
> successfully on:
> Linux vesta.uio.no 2.6.32-220.el6.x86_64 #1 SMP Wed Nov 9 08:03:13 EST
> 2011 x86_64 GNU/Linux
> gcc version 4.4.6 20110731 (Red Hat 4.4.6-3) (GCC)
> Then I ran both configure and make of maxima-5.26.0 using the following:
>> echo "configure maxima" 2>&1 | tee -a ../../logfile.maxima
>> strace -f ./configure --prefix=$INSTALL
>> --with-gcl=$HOME/local/bin/gcl 2>&1 | tee -a ../../logfile.maxima
>> echo "make maxima" 2>&1 | tee -a ../../logfile.maxima
>> strace -f make 2>&1 | tee -a ../../logfile.maxima
> The logfile can be downloaded from here:
> http://folk.uio.no/karstent/logfile.maxima > Its size is 81576181 bytes!
> Best regards,
> On 01/18/2012 07:56 PM, Camm Maguire wrote:
>> Greetings! I cannot reproduce this on a Debian unstable (sid) amd64
>> machine, gcc 4.6.2.
>> The only way this can happen is for mprotect to fail. I can update the
>> error message to give more info, but you can also run the build under
>> strace -f and see the mprotect errno setting if this is repeatable.
>> From the manpage:
>> EACCES The memory cannot be given the specified access. This can happen, for example, if you mmap(2) a file to which you have read-only
>> access, then ask mprotect() to mark it PROT_WRITE.
>> EINVAL addr is not a valid pointer, or not a multiple of the system page size.
>> ENOMEM Internal kernel structures could not be allocated.
>> ENOMEM Addresses in the range [addr, addr+len] are invalid for the address space of the process, or specify one or more pages that are not
>> mapped. (Before kernel 2.4.19, the error EFAULT was incorrectly produced for these cases.)
>> My guess is ENOMEM.
>> Please keep me posted.
>> Take care,
>> Karsten Trulsen<karstent@math...> writes:
>>> Dear Camm Maguire,
>>> Attempt to compile maxima-5.26.0 with the latest gcl (downloaded from
>>> CVS after release 2.6.7-96) is not successful. The building of gcl
>>> apparently goes well, I reproduce some configuration details:
>>>> checking build system type... x86_64-unknown-linux-gnu
>>>> checking host system type... x86_64-unknown-linux-gnu
>>> However, during the building of maxima, there is an error when dealing with
>>>> ; - Compiling source file
>>>> ; "/work/karstent/testinstall/maxima/maxima-5.26.0/src/compar.lisp"
>>>> Compiling /work/karstent/testinstall/maxima/maxima-5.26.0/src/compar.lisp.
>>>> End of Pass 1.
>>>> ;; Note: Tail-recursive call of HAS-INT-SYMBOLS was replaced by iteration.
>>>> ;; Note: Tail-recursive call of LIST-MEQP was replaced by iteration.
>>>> ;; Note: Tail-recursive call of CONSTP was replaced by iteration.
>>>> ;; Note: Tail-recursive call of SIGN was replaced by iteration.
>>>> ;; Note: Tail-recursive call of NONINTEGERP was replaced by iteration.
>>>> ;; Note: Tail-recursive call of EVOD was replaced by iteration.
>>>> End of Pass 2.
>>>> OPTIMIZE levels: Safety=0 (No runtime error checking), Space=0, Speed=3
>>>> Finished compiling binary-gcl/compar.o.
>>>> ; - Loading binary file "binary-gcl/compar.o"
>>>> Loading binary-gcl/compar.o
>>>> Error in FUNCALL [or a callee]: The assertion !clear_protect_memory(memory) on line 574 of sfaslelf.c in function fasload failed
>>> I am sorry if this error report does not satisfy formal requirements,
>>> I am not even sure if the error should be sent to gcl or maxima.
>>> Best regards,
>>> Karsten Trulsen
Camm Maguire camm@magu... ==========================================================================
"The earth is but one country, and mankind its citizens." -- Baha'u'llah