[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gcl-devel] RE: On statically linked Axiom (was: static lisp and rpms)
From: |
Page, Bill |
Subject: |
[Gcl-devel] RE: On statically linked Axiom (was: static lisp and rpms) |
Date: |
Mon, 27 Oct 2003 19:59:21 -0500 |
Camm,
When using the -enable-static option on configure under
RedHat Linux 8.0 and gcc 3.3.2 is it expected that the
gcl image be only about 180kbytes larger than without
the -enable-static option? Fram a 6 Mbyte image, this
seems like a surprizingly small change in size to me.
Cheers,
Bill Page.
> -----Original Message-----
> From: Camm Maguire [mailto:address@hidden
> Sent: Thursday, October 23, 2003 12:56 PM
> To: Bill Page
> Cc: address@hidden; address@hidden; address@hidden
> Subject: Re: On statically linked Axiom (was: static lisp and rpms)
>
>
> Greetings! OK, thanks for the report -- I've just committed a fix in
> cvs 2.6.1 and head. The patch is in two parts, one loads weak symbols
> as well as undefined symbols into the bfd symbol table, and the other
> maps the 't' and 'nil stream descriptors properly in optimized
> references to read-char. These will be in the next stable and
> unstable release on the temp site.
> ...
> >
> > On Monday, October 20, 2003 11:45 PM Tim wrote:
> >
> > >
> > > The statically linked GCL image has a problem:
> > >
> > > make file foo.lisp:
> > >
> > > (defun test (st) (read-char st))
> > >
> > > at lisp prompt:
> > >
> > > >(compile-file "foo.lisp")
> > > >(load "foo.o")
> > >
> >
> > I tried this under Windows with GCL 2.6.1 which is statically
> > linked without readline by default (I think?). It worked fine.
> >
> > So it seems that moving to 2.6.1, building with the new
> > .\configure --enable-static option and eliminating readline
> > might correct your static linking problem.
> >
> > Cheers,
> > Bill Page.
> >
- [Gcl-devel] RE: On statically linked Axiom (was: static lisp and rpms),
Page, Bill <=