axiom-developer
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Axiom-developer] RE: NULL_OR_ON_C_STACK macro invalid (was: noweb)


From: Page, Bill
Subject: [Axiom-developer] RE: NULL_OR_ON_C_STACK macro invalid (was: noweb)
Date: Tue, 15 Aug 2006 23:15:13 -0400

Tim,

On Tuesday, August 15, 2006 10:55 PM you wrote:
> 
> patches applied. testing restarted. --t
> 

Do you recall that this patch also involves a new version of
gcl-2.6.8pre? I am not sure whether the patch is applicable to
the older version of gcl-2.6.8pre in the Axiom repositories.

Regards,
Bill Page.


> -----Original Message-----
> From: Camm Maguire [mailto:address@hidden 
> Sent: Friday, August 11, 2006 10:24 AM
> To: address@hidden
> Cc: address@hidden; address@hidden; 
> address@hidden; address@hidden; address@hidden
> Subject: Re: NULL_OR_ON_C_STACK macro invalid (was: noweb)
> 
> Greetings!
> 
> I had to make the following modifications to 20050901 to work with the
> latest 2.6.8pre:
> 
> /fix/t1/camm/debian/axiom/axiom-20050901/int/interp/hash.lisp:
>  remove static
> 
> (clines "int mem_value(x ,i)object x;int i; { return ((short 
> *)x)[i];}")
> #+AKCL
> (defentry memory-value-short(object int) (int "mem_value"))
> 
> 
> /fix/t1/camm/debian/axiom/axiom-20050901/int/interp/cfuns.lisp
> : match unsigned/signed
> 
> #+(AND KCL (NOT ELF))
> (Clines
> "int MYCOMBINE(i,j)"
> "int i,j;"
> "{"
> "return ( (((((unsigned int)j) & 16777215) << 6)+((unsigned 
> int)i)) % 1073741789);"
> "}"
> )
> 
> /fix/t1/camm/debian/axiom/axiom-20050901/int/interp/sockio.lis
> p: match float/double
> 
>   (clines "extern float sock_get_float();")
>   (defentry open_server (string) (int "open_server"))
>   (defentry sock_get_int (int) (int "sock_get_int"))
>   (defentry sock_send_int (int int) (int "sock_send_int"))
>   (defentry sock_get_string_buf (int string int) (int 
> "sock_get_string_buf"))
>   (defentry sock_send_string_len (int string int) (int 
> "sock_send_string_len"))
>   (defentry sock_get_float (int) (float "sock_get_float"))
> 
> 
> The defentry code has been enhanced to support xgcl natively.
> 
> I just did a successful build of axiom 20050901 and acl2 3.0.1 with
> the same maxpage -- hope this works for you, though you might still
> have a stack/heap collision problem on your machine.
> 
> Take care,
> 
> "Page, Bill" <address@hidden> writes:
> 
> > Camm, 
> > 
> > On Thursday, August 10, 2006 1:59 PM you wrote:
> > > 
> > > Greetings!  FYI, just committed the removal of the
> > > power of 2 constraint on maxpage in both cvs head and
> > > version 2.6.8pre.
> > > 
> > 
> > Thanks for looking into this.
> > 
> > I just grabbed 2.6.8pre from cvs into a temp directory and
> > created a replacement tarball for the Axiom build, thus:
> > 
> >   cd /home/page/temp-dir
> >   export CVSROOT=:pserver:address@hidden:/sources/gcl
> >   cvs -z9 -q co -d gcl-2.6.8pre -r Version_2_6_8pre gcl
> >   tar czvf gcl-2.6.8pre.tgz gcl-2.6.8pre
> >   cd /home/page/axiom.build-improvements/zips
> >   mv gcl-2.6.8pre.tgz old_gcl-2.6.8pre.tgz
> >   mv /home/page/temp-dir/gcl-2.6.8pre.tgz .
> >   cd /home/page/axiom.build-improvements
> > 
> > I edited the GCLOPTS in Makefile from
> >   --enable-maxpage=256*1024
> > to
> >   --enable-maxpage=196*1024
> > resulting in
> > 
> >   GCLOPTS=--enable-vssize=65536*2 --enable-statsysbfd \
> >           --enable-maxpage=196*1024
> > 
> > in the default build for Axiom Silver build-improvements branch:
> > 
> >   make clean
> >   ./configure | tee build.log
> >   make 2>&1 | tee -a build.log
> > 
> > The build proceeded much further than before - the GCL sub-build
> > finished without errors - yeah! But the build of Axiom failed
> > with the following error message quite far along into the
> > interpsys build phase :(
> > 
> >   error: conflicting types for 'MYCOMBINE'
> > 
> > This is not something I have seen before. This same source builds
> > fine with the older version of 2.6.8pre and 128*256.
> > 
> > Here is the tail end of the log. I can send you the rest if you
> > like.
> > 
> > Please let me know how I can help.
> > 
> > Regards,
> > Bill Page
> > 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]