On Fri, Nov 21, 2008 at 12:09:18AM +, Neil Jerram wrote:
> I'm afraid I don't understand. What do you want to happen when you
> type "e (exit)"?
I want Guile to exit, just as normally happens when you call (exit).
Also return codes should be supported in the debugger as in the REPL,
e.g. "e (
2008/11/20 Derek Peschel <[EMAIL PROTECTED]>:
> Hi a second time.
>
> I'm using Guile 1.8.4, a copy of (ice-9 debugging) from guile 1.8.5, and
> guile-debugging 0.15. It seems natural to type "e (exit)" at the debug>
> prompt. Unfortunately the quit exception isn't acted on. Is there any
> reaso
2008/11/20 Andy Wingo <[EMAIL PROTECTED]>:
> Hi Dave,
>
> On Thu 20 Nov 2008 00:01, Dave Nadler <[EMAIL PROTECTED]> writes:
>
>> /cygdrive/d/home/drn/guile-1.8.5/libguile/guile.c:72: undefined
>> reference to `_l
>> t__PROGRAM__LTX_preloaded_symbols'
>
> I think this is because we don't support lib
On Thu, Nov 20, 2008 at 10:54:45AM +0100, Andy Wingo wrote:
> I don't know how much the debugger gives you -- I haven't really gotten
> into using it yet. But what I would want would be that if you install a
An overview of the relevant modules might help you find your way around the
code and docum
2008/11/20 Ludovic Courtès <[EMAIL PROTECTED]>:
>
> In theory, yes. In practice, the notion of "unbuffered port" is
> ill-defined, I'm afraid. The `SCM_BUF0' flag probably can't be relied
> on, as it appears to be only really used on `fports.c'. Actually, for
> some reason (probably copy & paste
Hi Dave,
On Thu 20 Nov 2008 00:01, Dave Nadler <[EMAIL PROTECTED]> writes:
> /cygdrive/d/home/drn/guile-1.8.5/libguile/guile.c:72: undefined
> reference to `_l
> t__PROGRAM__LTX_preloaded_symbols'
I think this is because we don't support libltdl version 2.2 yet,
unfortunately. Someone with acces
Ooops - I have libtool 2.2.
I will try again with the older version if I must...
Thanks !
Best Regards, Dave
At 12:02 PM 11/20/2008, Ludovic Courtès wrote:
Hi,
Dave Nadler <[EMAIL PROTECTED]> writes:
> gcc -g -O2 -Wall -Wmissing-prototypes -Werror .libs/guile.exeS.o -o
> guile.exe guile-guile.
Hi,
Dave Nadler <[EMAIL PROTECTED]> writes:
> gcc -g -O2 -Wall -Wmissing-prototypes -Werror .libs/guile.exeS.o -o
> guile.exe guile-guile.o -Wl,--export-dynamic ./.libs/libguile.a -lgmp
> -lcrypt -lltdl
> guile-guile.o: In function `main':
> /cygdrive/d/home/drn/guile-1.8.5/libguile/guile.c:72:
Hi All - I'm trying to build guile under cygwin (GCC 3.4.4);
as I need it for autoconf (for some gcc work).
configure runs AOK at least I don't see anything wrong.
make runs for eons and then dies with the error below.
Many thanks in advance for any and all suggestions,
Best Regards, Dave
gcc -g
Hello Neil,
"Neil Jerram" <[EMAIL PROTECTED]> writes:
> 2008/11/15 Ludovic Courtès <[EMAIL PROTECTED]>:
>>
>> So where to go from here? I think this example shows that the
>> `swap_buffer' trick is too risky, unfortunately. Thus, we may need to
>> revert it, at least in 1.8. Second, I think th
Hi Derek,
On Thu 20 Nov 2008 01:03, Derek Peschel <[EMAIL PROTECTED]> writes:
> Presumably the upward-only implementation of throw and catch is the
> problem (or part of it). Is that true? Is there an easy rule for
> determining which stack frames become non-recoverable?
It's an interesting qu
2008/11/15 Ludovic Courtès <[EMAIL PROTECTED]>:
>
> So where to go from here? I think this example shows that the
> `swap_buffer' trick is too risky, unfortunately. Thus, we may need to
> revert it, at least in 1.8. Second, I think that a `read' method as a
> replacement for `fill_input', as I p
Andy Wingo <[EMAIL PROTECTED]> writes:
> On Thu 20 Nov 2008 00:36, "Neil Jerram" <[EMAIL PROTECTED]> writes:
>
>> 2008/11/18 Ludovic Courtès <[EMAIL PROTECTED]>:
>>>
>>> I submitted a bug: https://savannah.gnu.org/bugs/index.php?24867 . I'm
>>> not sure whether this can easily be fixed in 1.8, si
13 matches
Mail list logo
