Weak references and GC

2005-09-07 Thread Neil Jerram
I'm having trouble with lists (actually source code expressions) that are weakly stored in several places and never being GC'd. I wondered if anyone on the list might be able to spot a problem in the following description. This is to do with my work on breakpoints, so each list here is a read cod

Re: Guile

2005-09-07 Thread Jon Wilson
Ah, here we go. This might help you some. From the Linux Documentation Project, at www.tldp.org, we have the Software Building HOWTO. http://tldp.org/HOWTO/Software-Building-HOWTO.html Read. Be enlightened. Regards, Jon Jon Wilson wrote: Dang it, I always send replies to the poster rather

Re: Guile

2005-09-07 Thread Jon Wilson
Dang it, I always send replies to the poster rather than to the list. My bad. Original Message Hi Angelyn, You might get a more helpful response if more pertinent information were provided. For example, knowing the conditions under which you ran ./configure would be very very

libreadline not found on your system (was Re: Guile)

2005-09-07 Thread Stephen Compall
On Wed, 2005-09-07 at 16:28 +0800, Angelyn V. Dilim wrote: > I am installing Guile which is the prerequisite of Texmacs software > after running the command below; > > # ./configure > > i read a warning error saying configure WARNING:libreadline is not > found on your system As Guile is a prer

Re: Guile

2005-09-07 Thread Mike Gran
Angelyn- Hi. Installing programs from the source can be confusing if you don't have much experience with it. Before you try installing from source, you should check to see if your version of GNU/Linux (or whatever operating system you are using) has a ready-to-install version. If you are using

Guile

2005-09-07 Thread Angelyn V. Dilim
Hi,   I am installing Guile which is the prerequisite of Texmacs software after running the command below;   # ./configure   i read a warning error saying configure WARNING:libreadline is not found on your system so when i run the command below;   # make   i am getting an error error code

Re: Exposing common type wrapping/unwrapping methods

2005-09-07 Thread Ludovic Courtès
Hi Marius, Marius Vollmer <[EMAIL PROTECTED]> writes: > Hmm, I think your patch mixes the two ways we have to express a socket > address: one way is an argument convention used by connect, bind, and > sendto; the other way is a vector with the relevant data inside, as > returned by accept, getsoc