[Top][All Lists]

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

Re: [Gcl-devel] troubles bulding Maxima with latest GCL CVS

From: Camm Maguire
Subject: Re: [Gcl-devel] troubles bulding Maxima with latest GCL CVS
Date: 16 Aug 2002 18:43:07 -0400

If it wouldn't be too much trouble, could you post the diff first?  

My original concern was in running ansi images in gdb -- and the
answer there seems to be using the system ld for the final link, as
even with a working native reloc code, we don't import the .stabs
debugging section of the objects, so those pieces of code effectively
become black boxes to gdb.  We could change this in the future, or
provide an option to do so, but for now only developers should be
interested and the easiest thing is to provide a make target which
uses ld.  So the symbol table building here is not an issue.

Beyond this, regarding the compile time/runtime initialization -- this
again is apparently not a problem, and I think I now know why.  The
lisp compiler is very careful not to compile in named references to
any functions that aren't available in raw_gcl.  All other function
links are arbitrarily named and connected to the proper function at
load time.  So in short, the symbol table built when initializing
raw_gcl should suffice, and it apparently does or else all hell would
break loose when loading pcl objects as part of the ansi build.  

So in sum, I don't think we need to build the symbol table again -- in
fact, it would just be a gratuitous waste of memory space, adding in
symbols which the loader would never need.  But I could be wrong, and
would like to see your diff in any case.

Take care,

"Vadim V. Zhytnikov" <address@hidden> writes:

> Camm Maguire writes:
> > 
> >    One thing I notice at saved_maxima and at saved_trad_gcl creation
> >    is the "Building raw symbol table" notifier.  This does not appear
> >    when building the new images.  These symbols are generated via the
> >    lisp function build-symbol-table, which must be getting called
> >    somewhere before save-system, though I cannot find it right now.  I
> >    don't think we are invoking this in the new image saves.  In
> >    general, the reloc code counts on the symbol table being generated
> >    at compile time, and statically available at run time.  I think,
> >    though, that the old reloc code could also build the table in case
> >    it was not initialized at runtime.  the new code does not yet have
> >    this capability, so perhaps I'll try adding this.  But to be sure,
> >    I need to be able to run gdb, which I can't now.  Can you help
> >    here, Vadim?
> > 
> After all I understood how to properly add build-symbol-table when
> saving new saved_pcl_gcl and saved_ansi_gcl.  And it works to me.
> Shall I commit the fix?
> Best wishes,
> -- 
>       Vadim V. Zhytnikov
>        <address@hidden>
>       <address@hidden>
>       <address@hidden>
>      <address@hidden>
> _______________________________________________
> Gcl-devel mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/gcl-devel

Camm Maguire                                            address@hidden
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah

reply via email to

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