Re: hash-fold

Mikael Djurfeldt <[EMAIL PROTECTED]> writes: > Keisuke Nishida <[EMAIL PROTECTED]> writes: > > > The following code makes an error. Is this a feature or a bug? > > > > guile> (hash-fold acons () (make-vector 5)) > > It's a bug in the above expression. (make-vector 5) makes a vector > with #

Re: Crash in scm_boot_guile if stdin isn't open.

Jon K Hellan <[EMAIL PROTECTED]> writes: > Build it, and run it with stdin closed: > % ./prog <&-1 > Segmentation fault (core dumped) > > (gdb) bt How did scm_init_fluids sneek into your backtrace? Mine looks like: % gdb guile GNU gdb 4.17.m68k.objc.threads.hwwp.fpu.gnat Copyright 1998 Free S

Re: Crash in scm_boot_guile if stdin isn't open.

Jon K Hellan <[EMAIL PROTECTED]> writes: > Anyway, it's better that guile works around it than that all apps > which embed it each have to make a workaround. I have now committed a workaround. Please test it. 2000-03-12 Marius Vollmer <[EMAIL PROTECTED

Re: Crash in scm_boot_guile if stdin isn't open.

Gary Houston <[EMAIL PROTECTED]> writes: > It's quite interesting, it seems like a bug in gcc. > > Please compile this with -O2 and -O2 -fno-gcse and check my sanity: You are sane: % gcc -o bug bug.c % ./bug Aborted (core dumped) % gcc -o bug -O2 bug.c % ./bug Segment

Re: Crash in scm_boot_guile if stdin isn't open.

Gary Houston <[EMAIL PROTECTED]> writes: > I think I'll add something to configure to use the -fno-gcse flag if it's > supported. With proper benchmarking the effect, of course. ;-)

Re: autogen.sh broken for guile-readline

thi <[EMAIL PROTECTED]> writes: > a while ago, i submitted a small patch to address the situation > where aclocal and libtool are installed w/ different PREFIX. > perhaps this is the problem (still)? (insert standard grumble about > dropped patches here.) I'm not opposed to this change, but I g

Re: autogen.sh broken for guile-readline

thi <[EMAIL PROTECTED]> writes: > i don't believe installation of tools using different prefixes is really > considered a misinstallation. Agreed. "misinstallation" was probably the wrong word. In any case and my view, the problem lies entirely with automake and libtool and not with how Guile

Re: assoc-ref broken?

thi <[EMAIL PROTECTED]> writes: > something is weird w/ assoc-ref this is w/ latest cvs guile. > > guile> (assoc 3 '((1 . 2) (3 . 4) (5 . 6))) > (3 . 4) > guile> (assoc-ref 3 '((1 . 2) (3 . 4) (5 . 6))) > #f Use guile> (assoc-ref '((1 . 2) (3 . 4) (5 . 6)) 3) 4 instead. Arguments

sig11 puts Guile in a loop

Hi, after this function SCM_PROC(s_segfault, "segfault", 0, 0, 0, sim_segfault); SCM sim_segfault () { *(int *)0 = 0; return SCM_UNSPECIFIED; } has been added to libguile, I get this behaviour guile> (segfault) Guile is in a loop, calling take_signal,

Re: sig11 puts Guile in a loop

Gary Houston <[EMAIL PROTECTED]> writes: > This behaviour can be got back by explicitly calling SCM_ASYNC_TICK from > the handler, but I'm not sure if this was what you wanted to avoid with > the posix threads change: Intuitively, I would like to call SCM_ASYNC_TICK from take_signal, but I don't

Re: libguile/scmsigs.c (orig_handlers): function returns array

ns: > > static SIGRETTYPE (*orig_handlers[NSIG])(int); Thanks! However, I can't test this change because I HAVE_SIGACTION. 2000-05-03 Marius Vollmer <[EMAIL PROTECTED]> * scmsigs.c (orig_handlers) [HAVE_SIGACTION]: Fix declaration to be an array of function pointers ins

Re: guile-core (cvs version) -qt in INSTALL

Bill Schottstaedt <[EMAIL PROTECTED]> writes: > line 73 of the cvs guile-core INSTALL file says "-qt" > but I think it means "-lqt". Thanks! INSTALL seems to be somewhat outdated in general. I will look over it.

Re: sig11 puts Guile in a loop

Mikael Djurfeldt <[EMAIL PROTECTED]> writes: > What you could, and probably should, do is to call SCM_TICK in longer > loops in your simulator code. Yes, that's a good suggestion. However, the problem is that once a segv occured, and the handler for SIGSEGV simply returns, the program just reex

Re: sig11 puts Guile in a loop

Mikael Djurfeldt <[EMAIL PROTECTED]> writes: > But, as you previously suggested, it is not sensible to try to > continue executing code after a segv. That *kind* of signals should > cause immediate abort, I think. Ok, I'll implement something to that effect. I'm not sure if I canb get it compl

format: the difference between ~A and ~S.

Look at the following Guile behaviour: guile> (format #t "~A\n" '("x")) (x) guile> (format #t "~S\n" '("x")) ("x") guile> (use-modules (ice-9 format)) guile> (format #t "~A\n" '("x")) ("x") #t guile> (format #t "~S\n" '("x")) ("x") #t guile> I thi

Re: sig11 puts Guile in a loop

Ole Myren Rohne <[EMAIL PROTECTED]> writes: > I think which signals belong to "That *kind* of signals" should be > application specific: > > I use guile to interactively control a pci-to-vme bridge that gives > SIGBUS in a lot of non-fatal situations: vme-crate is not switched > on, no data avai

Re: Typo in reference manual

Eric Hanchrow <[EMAIL PROTECTED]> writes: > All instances of `disble', above, should of course be changed to > `disable'. This has already been fixed in CVS. Anyway: thanks!

Re: cvs guile on linuxppc 2000 and old sgi (irix 5.3)

Mikael Djurfeldt <[EMAIL PROTECTED]> writes: > Bill Schottstaedt <[EMAIL PROTECTED]> writes: > > > on sgi irix 5.3, the new makefiles use a construct something > > like DEPS_MAGIC... (line 551 of libguile/Makefile for example); > > all of these cause a syntax error in this version of make. > > I

Re: Guile-1.3.5pre2 Dynamic linking looking for .la.la, .la.so files?

"Greg J. Badros" <[EMAIL PROTECTED]> writes: > open("./cassowary/libconstraints.la.la", O_RDONLY) = -1 ENOENT (No such file or >directory) > open("./cassowary/libconstraints.la.so", O_RDONLY) = -1 ENOENT (No such file or >directory) > > Any ideas what is going on in the last couple lines? Thi

Re: rl_pre_input_hook checked as code when it is data

Marko Kohtala <[EMAIL PROTECTED]> writes: > guile-readline/configure in guile-1.4 checks for rl_pre_input_hook in > libreadline. However, it checks it as a function while it actually is a > function pointer variable. This does not go through all linkers. I > noticed this on HP-UX 10.20. Can you

Re: Bug in scm_call_catching_errors

Dirk Herrmann <[EMAIL PROTECTED]> writes: > 1) Is this function used at all? If not, we should deprecate it. Make it deprecated, I say.

Re: segfault from backtrace of do () with unbound variable

Bill Schottstaedt <[EMAIL PROTECTED]> writes: > Backtrace: > 0* [hi 2] > 1 Segmentation fault (core dumped) Fixed. Thanks! 2000-07-17 Marius Vollmer <[EMAIL PROTECTED]> * eval.c (unmemocopy): Don't rely on V being a list of at least on

Re: Bug in assq/v/oc-remove! primitives (with patch)

Neil Jerram <[EMAIL PROTECTED]> writes: > I think I've found a bug in assq-remove! and friends. My > understanding is that > > (assq/v/oc-remove! alist key1) > > should remove all entries from the alist whose *key* is > eq?/eqv?/equal? to key1. > > In fact, with the current CVS implementation

Re: Bug in assq/v/oc-remove! primitives (with patch)

Neil Jerram <[EMAIL PROTECTED]> writes: > I agree. Would you like a further patch for this, or will you just > change the 3 "while"s back to "if"s? Yep, I'll do the changes myself. The final patch then looks like a bug fix, where scm_delv_x and scm_delete_x is merely replaced by scm_delq_x, ri

Re: Bug in assq/v/oc-remove! primitives (with patch)

Mikael Djurfeldt <[EMAIL PROTECTED]> writes: > I'm not up-to-date on what you're talking about, but since you mention > removing *one* item, it seems like you should use scm_delq1_x instead > of scm_delq_x. Yep, right. I though scm_delq_x would only remove one item. Wasn't that the case some t

Re: Named let

Keisuke Nishida <[EMAIL PROTECTED]> writes: > Hello, > > Is this a bug? > > % guile > guile> (let loop ((foo loop)) foo) > # > > R5RS says is bound within . You did expect it to be bound _only_ in , not in the initialization expressions of the , right? According to the formal semantic

Re: Missing headers in iselect.c

for the report! The header files and are taken care of in the file "iselect.h" already. should be included, tho. 2000-08-05 Marius Vollmer <[EMAIL PROTECTED]> * iselect.c: Include . Thanks to Bertrand Petit!

Re: Named let

Marius Vollmer <[EMAIL PROTECTED]> writes: > Keisuke Nishida <[EMAIL PROTECTED]> writes: > > > Hello, > > > > Is this a bug? > > > > % guile > > guile> (let loop ((foo loop)) foo) > > # > > > > R5RS says is

Re: bug in modules?

[ Please post bug reports to <[EMAIL PROTECTED]>. ] Ivan Toshkov <[EMAIL PROTECTED]> writes: > Here is the test module, with missing closing paren: > > --- > (define-module (test)) > > (define (some-buggy-proc a) > a > > --- > > $ guile > guile> (version) > "1.4" >

Re: set-procedure-property! doesn't do proper type check on first arg

Mikael Djurfeldt <[EMAIL PROTECTED]> writes: > set-procedure-property! doesn't do proper type check on first arg Incidentally, I'm in favour of unifying object and procedure properties. That is, there would be only object properties, and the `object-property' functions can be used to access the

Re: Problem with current validate macros

Mikael Djurfeldt <[EMAIL PROTECTED]> writes: > If we could, somehow, store the signature with the primitives, and > look it up at errors, that would be even better. Isn't that information contained in the online docs?

Re: allow-other-keys typo in optargs.scm

Bill Schottstaedt <[EMAIL PROTECTED]> writes: > I think the line (209 in optargs.scm) > > ((allow-other-keys) #:allow-other-keys-value) > > should be > > ((allow-other-keys) #:allow-other-keys) Thanks! I fixed this. > Also, as I'm sure you guys know already (I'm not on this > mailing li

Re: allow-other-keys typo in optargs.scm

Bill Schottstaedt <[EMAIL PROTECTED]> writes: > > > Also, as I'm sure you guys know already (I'm not on this > > > mailing list), (use-modules (ice-9 syncase)) dies in the > > > current guile with a segfault. > > > > Hmm, it works for me. Can you try the latest CVS version and give > > detailed

[Bug-guile] Re: Numerical (parser?) bug

"Ivan Toshkov" <[EMAIL PROTECTED]> writes: > $ uname -psmr > Linux 2.2.14-5.0 i686 unknown > $ guile > guile> (version) > "1.4.1" > guile> 5e-308 > 5.0e-308 > guile> 5e-309 > ERROR: In expression 5e-309: > ERROR: Unbound variable: 5e-309 > ABORT: (unbound-variable) > > Type "(backtrace)" to get

Re: [Bug-guile] Generated files in cvs

"Dale P. Smith" <[EMAIL PROTECTED]> writes: > Not a big thing, but if guile-core was cleaned up, other modules > should be cleaned up too. Yep, right. I'll look into this. ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/list

Re: eq? and friends accept more than two parameters

Dirk Herrmann <[EMAIL PROTECTED]> writes: > If I understand R5RS correctly, then eq?, eqv? and equal? should > accept exactly two parameters. The current CVS guile, however, > accepts more parameters as well. On the one hand, this seems to be > a sensible extension, but it should somehow be pos

Re: C++ reserved words in header files

Martin Baulig <[EMAIL PROTECTED]> writes: > please don't use C++ reserved words such as `destructor' in > installed header files; I'm using GNU C 2.95.2 on Debian woody > and I got a syntax error in line 200 in coop-defs.h because of > this. Can you prepare a patch that covers all instances of t

Re: C++ reserved words in header files

unning grep over all header files also didn't give me any other > place. Ok, fixed. Thanks! 2000-10-02 Marius Vollmer <[EMAIL PROTECTED]> * coop-defs.h (coop_key_create): Don't use the C++ keyword `destructor' in prototype. Thanks to Martin Baulig! __

Re: [Patch] Install guile-procedures.txt in version-specific directory

Matthias Koeppe <[EMAIL PROTECTED]> writes: > 2000-10-28 Matthias Koeppe <[EMAIL PROTECTED]> > > * Makefile.am: Install guile-procedures.txt in version-specific > directory to enable multiple installed guile versions. > Suggested by Karl M. Hegbloom <[EMAIL PROTECTED]>. Appl

Re: Doc patches

Martin Grabmueller <[EMAIL PROTECTED]> writes: > I have looked through the top-level doc files of guile-core, mainly to > correct references to CVS repository locations, mailing lists etc., > and corrected everything I found. Thanks! I have applied your patch. Mikael, since you know the most a

Re: display-error segmentation fault

Neil Jerram <[EMAIL PROTECTED]> writes: > This is with a current CVS Guile (on a GNU/Linux system). > > [neil@ossau neil]$ guile > guile> (display-error #f #f #f #f #f #f) > Segmentation fault (core dumped) > [neil@ossau neil]$ > > The problem arises because scm_display_error does not check th

Guile webpages [still] unreadable

I think we already have discovered this, right? But it looks like we didn't fix it. What's the procedure for getting the Web pages changed? Subject: [[EMAIL PROTECTED]: Guile webpages unreadable] bcc: [EMAIL PROTECTED] Reply-to: [EMAIL PROTECTED] --text follows this line-- Please DTRT.

Re: Guile webpages [still] unreadable

thi <[EMAIL PROTECTED]> writes: > ... ok, fixed. (find-grep-dired for "FFF" (seven Fs) is clean.) Thanks! ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile

Re: cvs smob doc update

"Dale P. Smith" <[EMAIL PROTECTED]> writes: > Here is a patch that uses SCM_SMOB_DATA instead of SCM_CDR. Also things > like SCM_SMOB_PREDICATE and SCM_NEWSMOB. Thanks, applied! ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman

Re: make-vector/vector-length disagree for large vectors.

Dirk Herrmann <[EMAIL PROTECTED]> writes: > The bug with the missing boundary checking is easy to fix. Whether > vectors should be changed to allow for more than 2^24 elements is up to > the maintainers. Allowing only 2^24 elements is OK, but the boundary check should be correct, of course. __

Re: Properly handling smobs in macros.c

Martin Grabmueller <[EMAIL PROTECTED]> writes: > Hi all, > > this is not really a bug, but I think the attached change should be > made for the sake of consistency. > > 2001-02-08 Martin Grabmueller <[EMAIL PROTECTED]> > > * macros.c (scm_macro_name, scm_macro_transformer): Use >

Re: guile compile error

"Rigel" <[EMAIL PROTECTED]> writes: > Running RH7 on i586. got a compile error from standard make: > net_db.c:85: conflicting types for `inet_aton' > /usr/include/arpa/inet.h:69: previous declaration of `inet_aton' > make[1]: *** [net_db.lo] Error 1 > make[1]: Leaving directory `/usr/local/src/g

Re: Trying to get guile-oops to compile on rh7

[EMAIL PROTECTED] writes: > I can not get either cvs guile-oops or guile-oops-0.1.8.tar.gz > to compile on this machine. Guile-oops has been integrated into guile-core, so I don't think you need to compile guile-oops with cvs guile-core. ___ Bug-guile

Re: cond

s for the bug report! This should be fixed in CVS now. 2001-02-21 Marius Vollmer <[EMAIL PROTECTED]> * eval.c (scm_ceval, scm_deval): Check for wrong number of args before applying arrow procedure in `cond' and before applying receiver proce

Re: Guile 1.4 compilation bugs (and patches) under Cray UnicosMk

"Steven G. Johnson" <[EMAIL PROTECTED]> writes: > ! SCM_BIGDIG zdigs [SCM_DIGSPERLONG]; Fixed, thanks! > ! #include This has already been fixed in CVS previously. ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listin

Re: coredump in Guile 1.4 on Cray T3E

"Steven G. Johnson" <[EMAIL PROTECTED]> writes: > Compiling it with -g and running it under Cray's TotalView debugger > (ugh), I get the stack trace attached below. The Guile code at this > point is a little hairy, and I'm not entirely sure what is going on. > Can someone suggest something to lo

Re: Guile 1.4 compilation bugs (and patches) under Cray UnicosMk

"Steven G. Johnson" <[EMAIL PROTECTED]> writes: > Thanks; it looks like you only applied half of the patch, though. Oops. sorry. I should make it a habit to use "emerge" even for small patches... ___ Bug-guile mailing list [EMAIL PROTECTED] http://ma

Re: Guile problem

<[EMAIL PROTECTED]> writes: > Is there any solution for this problem? I really needed to compile > those programs and start working with them (otherwise I will have to > go back to Windows - blaargh) I think you will be better off to asking the authors of the other packages (snd, lilypond, etc)

Re: duplicate bindings in let*

Martin Grabmueller <[EMAIL PROTECTED]> writes: > > perhaps caused by the two "flags" in build-link? > > Correct, but the bug is not in let*, but in guile-config. Recently, > let* was changed to detect this error. No, no, no. `let*' can tolreate duplicate bindings. I just wasn't thinking clea

Re: Problem with __USE_XOPEN

Keisuke Nishida <[EMAIL PROTECTED]> writes: > What would be the best solution? We should add #define _GNU_SOURCE at the top of "posix.c". __USE_XOPEN is the wrong macro to use, it should be one of the _FOO_SOURCE macros. _GNU_SOURCE is the catch all and might be too broad, but _POSIX_SOU

Re: Missing declaration of `scm_debug_check_freelist'

Martin Grabmueller <[EMAIL PROTECTED]> writes: > I suppose it's just a > > static int scm_debug_check_freelist = 0; > > missing, but maybe someone else kows more about it. I don't. Please do what you think is the Right Thing. ___ Bug-guile maili

Re: ./check-guile: test: argument expected

Alexander Klimov <[EMAIL PROTECTED]> writes: > Hi. > > According to `man test' on Solaris 2.6 there is no `-e' primitive for sh, > but only for ksh. It also exists in bash. > > There is an error in check-guile:36 > > if [ ! -e guile-procedures.txt ]; then > ^^^ > which produces the error

Re: ./check-guile: test: argument expected

Alexander Klimov <[EMAIL PROTECTED]> writes: > Actully, documentation said that all commands follow simbolic links, so > `-f' means that after it resolve symbolic links it found `regular file'. Ahh, I see. Sorry for not checking more thoroughly. "-f" is the way to go, then. __

Strange error message for (apply car '())

Hi, this looks wrong: guile> (apply car '()) ERROR: In procedure cdr: ERROR: Wrong type argument in position 1: # (I think I'm going to fix this myself.) ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bu

Re: guile-oops 1.0.2 won't configure on DU 4.0

Alexandre Oliva <[EMAIL PROTECTED]> writes: > The configure script contains a test command using the `==' operator. > `==' is not portable. Please change that to `='. Thanks, Please be more specific. I can't find a test command using "==" in configure.in. The only occurences of "==" that I c

Re: guile-oops 1.0.2 won't configure on DU 4.0

Alexandre Oliva <[EMAIL PROTECTED]> writes: > On Mar 30, 2001, Marius Vollmer <[EMAIL PROTECTED]> wrote: > > > Alexandre Oliva <[EMAIL PROTECTED]> writes: > >> The configure script contains a test command using the `==' operator. > >> `==&

Re: Vectors should not evaluate to themselves

Martin Grabmueller <[EMAIL PROTECTED]> writes: > But that's just a theory, which is by me and is completely mine... :-) Presenter: You have a new theory about the vector? Martin: Can I just say here Chris that I have a new theory about the vector. P: Exactly. (He gestures but Martin does n

Re: numeric tests

Bill Schottstaedt <[EMAIL PROTECTED]> writes: > In case there's interest (some of the tests are a bit nutty), > the file is at ccrma-ftp.stanford.edu/pub/Lisp/number-tests.scm. Thanks! I'll look into this. ___ Bug-guile mailing list [EMAIL PROTECTED]

Re: Segfault connected with taking class-of memoized code?

Neil Jerram <[EMAIL PROTECTED]> writes: > > "Neil" == Neil Jerram <[EMAIL PROTECTED]> writes: > > Neil> [...] > Neil> debug> evaluate (class-of exp) > Neil> Segmentation fault > > A much simpler example is this: > > neil@laruns:~$ guile -q > guile> (class-of class-of) > Segment

Re: values.h missing in libguile.h

Martin Grabmueller <[EMAIL PROTECTED]> writes: > I assume it is just a small mistake that values.h is not included in > libguile.h, but I ask anyway because maybe the `multiple values C API' > was only experimental. If it is okay, I will add it. It's OK! Thanks! __

Re: shell scripts in CVS source don't have runable permission

Masao Uebayashi <[EMAIL PROTECTED]> writes: > These have to have '0755' so that autogen.sh can run properly. Is that a real problem in practice? I think when you chmod them once, CVS will keep the permissions across updates. On the other hand, I'm not sure that CVS will keep the permissions co

Re: CVS guile + module system broken

Martin Grabmueller <[EMAIL PROTECTED]> writes: > Hello list, > > mgrabmue@tortoise (~/cvs/guile/x/guile-1.4.1/libguile): >GUILE_LOAD_PATH=~/cvs/guile/x/guile-1.4.1/ ./guile > ERROR: In procedure set-current-module: > ERROR: Wrong type argument in position 1: #f > > > Is this because `set-curr

Re: GUILE_WARN_DEPRECATED_DEFAULT missing?

Bill Schottstaedt <[EMAIL PROTECTED]> writes: > I think this macro is missing from the CVS > guile-core/libguile/deprecation.h. No, it is supposed to be defined in "libguile/scmconfig.h". You probably didn't pick up the change yet in your build setup. Try rerunning "autogen.sh", "configure", e

Re: Problems compiling guile on a Cobalt mips (qube 2)

"Dale P. Smith" <[EMAIL PROTECTED]> writes: > #2 0x2ad30308 in __libc_realloc (oldmem=0x2adde954, bytes=18000) > at malloc.c:3097 > #3 0x2aafb028 in scm_must_realloc (where=0x100260b8, old_size=12000, > size=18000, what=0x2aac93f0 "scm_subr_table") at gc.c:1931 This looks suspicious.

Re: `-' and zero arguments

Martin Grabmueller <[EMAIL PROTECTED]> writes: > guile> (/) > :2:1: In procedure / in expression (/): > :2:1: Wrong type argument in position 1: # > ABORT: (wrong-type-arg) > > I am not sure how to fix this, because of the generic function > dispatch stuff. Should there be a dispatch for a

Re: extra_dot_x_files in configure.in?

Bill Schottstaedt <[EMAIL PROTECTED]> writes: > I'm not sure that my copy of CVS guile-core/configure.in is actually > up-to-date, but I think it needs something like: > > EXTRA_DOT_X_FILES="`echo ${LIBOBJS} | sed 's/\.o/.x/g'`" > > after the similar line for EXTRA_DOT_DOC_FILES, and the > corr

Re: Guile (Developing and Contributing)

Quetzalcoatl Bradley <[EMAIL PROTECTED]> writes: > Repeatable bus error on MacOS X 10.0.2 with guile-1.4 Same on GNU/Linux (segfault instead of bus error, tho). Thanks! 2001-05-10 Marius Vollmer <[EMAIL PROTECTED]> * ports.c (scm_port_revealed, scm_set_port_re

Re: guile-1.3 ported to mips-compaq-nonstopux

Tom Bates <[EMAIL PROTECTED]> writes: > Just a note to say I've ported guile-1.3 to mips-compaq-nonstopux. > I had to make some changes though. Great! To get your changes into mainstream Guile, you would have to port the current CVS version and send us patches. If the patches are significant,

Re: use-modules does not signal error on non-existing modules

Martin Grabmueller <[EMAIL PROTECTED]> writes: > Hello list, > > I suppose this is related to the recent module system changes: > > mgrabmue@tortoise (~/cvs/guile/guile-core/libguile): >GUILE_LOAD_PATH=/home/mgrabmue/cvs/guile/guile-core ./guile > guile> (use-modules (definitely not installed

Re: `-' and zero arguments

Dirk Herrmann <[EMAIL PROTECTED]> writes: > [zero argument methods] > > It's not usefull, right. But, does it do any harm? I don't know. Let's just leave it as it is. ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/

Re: CVS Guile is core dumping

Ariel Rios <[EMAIL PROTECTED]> writes: > (gdb) run > Starting program: /usr/local/bin/guile > > Program received signal SIGSEGV, Segmentation fault. > 0xff794f0 in scm_hash_fn_create_handle_x () at ../libguile/hashtab.x:21 > 21scm_make_gsubr (s_scm_hash_fold , 3 , 0 , 0 , (SCM (*)

Re: gentemp deprecation

"Dale P. Smith" <[EMAIL PROTECTED]> writes: > gentemp is being deprecated, but is still used all over the > place. Well, it's used in expect.scm, match.scm, psyntax.pp and > psyntax.ss. These should probably all be changed to use gensym > instead. Yes, thanks! _

Uninterned symbols

Martin Grabmueller <[EMAIL PROTECTED]> writes: > > From: "Dale P. Smith" <[EMAIL PROTECTED]> > > > > BTW: gensym does not return unique symbols: > > [...] > > Wasn't this fixed a while back? Or was that gentemp? > > Well, it was noticed a while ago, but AFAICT, nobody fixed it. I > wanted to w

Re: Missing paren in goops.scm

Oops. The shame. It's fixed. ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile

Re: Build probs under Solaris

Martin Grabmueller <[EMAIL PROTECTED]> writes: > I have just tried to build a fresh CVS Guile under Solaris, but got no > luck. After updating and a make clean, autogen.sh gave the following > warnings: This might be because we have removed the copy of libtool.m4 from acinclude.m4. Now aclocal

Re: (use-syntax (ice-9 syncase)) broke with --disable-deprecated

"Dale P. Smith" <[EMAIL PROTECTED]> writes: > guile> (use-syntax (ice-9 syncase)) > > : While evaluating arguments to fluid-set! in expression > (fluid-set! scm:eval-transformer (module-transformer #)): > : Unbound variable: scm:eval-transformer > ABORT: (unbound-variable) Thanks! Fixed. I ev

Re: awk portability

"Golubev I. N." <[EMAIL PROTECTED]> writes: > To allow guile work with native awk it needs at least one patch. We already have a fix for SCO nawk in CVS. Does it help? 2000-10-02 Michael Livshin <[EMAIL PROTECTED]> * guile-func-name-check.in: now should not confuse SCO nawk

Re: awk portability

Michael Livshin <[EMAIL PROTECTED]> writes: > looks like the awk script should be replaced as soon as possible... Ok, and all of them, I suppose. I would like it if they could be replaced with Guile programs, even if that means a slightly more contorted build procedure. I don't have agood over

Re: awk portability

"Golubev I. N." <[EMAIL PROTECTED]> writes: > But why do not I see this change neither in snapshot in > > nor in `:pserver:anoncvs@source{ware.cygnus,s.redhat}.com:/cvs/guile' > (which snapshot seems to be derived from)? The

Re: outdated places/Re: awk portability

"Golubev I. N." <[EMAIL PROTECTED]> writes: > > http://savannah.gnu.org/projects/guile > > It does not contain `snapshot' word at all, but refers to > which still refers to > . Yes, I know, s

Re: !have mkstemp

"Golubev I. N." <[EMAIL PROTECTED]> writes: > Since `mkstemp' implementation should be highly portable (require > nothing beyond posix), it may be reasonable to take one from gnu libc > and do AC_REPLACE_FUNC. I did that. Please test. Thanks! ___ Bu

Re: hash.c:101: pointers are not permitted as case values

Alexander Klimov <[EMAIL PROTECTED]> writes: > > If that helps, we will use that fix. > Yes, the following patch solves the problem Thanks! Applied. 2001-06-05 Marius Vollmer <[EMAIL PROTECTED]> * hash.c (scm_hasher): Use SCM_UNPACK in the case labels so that

Re: scm_hash_fn_create_handle_x?

Masao Uebayashi <[EMAIL PROTECTED]> writes: > I can avoid core dump by the following patch. > This is not the best way, though. The reason Guile dumps core is that it wants to output a deprecation warning at a time when the deprecation mechanism has not been initialized yet. It tried to output

Re: scm_hash_fn_create_handle_x?

Masao Uebayashi <[EMAIL PROTECTED]> writes: > % gmake > : > (snip) > : > Segmentation fault - core dumped I recognize this. Remove libguile/cpp_err_symbols.c and libguile/cpp_sig_symbols.c and rebuild. ___ Bug-guile mailing list [EMAIL PROTECTED] h

Re: Bug in find-and-link-dynamic-module

Thomas Wawrzinek <[EMAIL PROTECTED]> writes: > When playing around with dynamically loadable modules written in > pure C I found that on my Linux box guile tries to access weirdly > named libraries (that do not exist), like libfoo.la.la or > libfoo.so.la. That code has been deprecated recently.

Re: CVS guile does not build

Martin Grabmueller <[EMAIL PROTECTED]> writes: > after the latest type renaming, Guile does not build anymore for me: Fixed! ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile

Re: Problems building guile-readline

"Dale P. Smith" <[EMAIL PROTECTED]> writes: > configure: configuring in guile-readline > configure: running /bin/sh './configure' --disable-deprecated > --with-gnu-ld --disable-static --enable-ltdl-convenience > --cache-file=/dev/null --srcdir=. > ./configure: line 893: syntax error near unexpec

Re: uniform arrays & vectors

Martin Grabmueller <[EMAIL PROTECTED]> writes: > well, we all know that Guile's uniform vectors & arrays are strange, > but the following is really buggy, isn't it? (taken from unif.c:315) Yes, I can't figure it out, either. The code (in toto) looks quite complicated, but I'm not sure whether t

Re: couldnt compile guile

Martin Grabmueller <[EMAIL PROTECTED]> writes: > But anyway, where did you download the snapshort from? www.glug.org > or www.red-bean.com. The latter could be out of date, because it is > (or was?) created from an outdated CVS repository, but I am not sure.. Yes, this seems to be the case. I

Re: make dist fails

"Dale P. Smith" <[EMAIL PROTECTED]> writes: > Current cvs fails on a "make dist" after "./autogen.sh; ./configure". > > Here is the error: Looks like a automake bug to me. I have reported this to <[EMAIL PROTECTED]>. The following patch to automake seems to work, for the time being: --- /us

Re: missing .x files

"Dale P. Smith" <[EMAIL PROTECTED]> writes: > I just tried to compile cvs guile on a cobalt Qube 3 (intel, 2.2.x > kernel, hacked over RedHat distro) from a "make dist" that I made on my > Debian unstable (latest auto* tools) machine. Works for me. That is, I can build a distro that I made with

Re: Problem building guile 1.4

Andrew Koenig <[EMAIL PROTECTED]> writes: > Following is the output from running "configure" -- look for the > first line with "**" in it. Please also show the contents of `guile-readline/config.log'. The test program for rl_getc_function did not compile, which could have many causes besides th

Re: Problem building guile 1.4

Andrew Koenig <[EMAIL PROTECTED]> writes: > The output seems to suggest that readline puts its header file > somewhere that guile doesn't know about. Right. Where is it, then? Guile makes no special efforts for finding header files in non-standard locations. __

Re: Infinite loops with scm_read_0str and scm_eval_0str

"Dale P. Smith" <[EMAIL PROTECTED]> writes: > The deprecated functions are calling themselves instead of the new > funcions. Boy! I'm s sloppy. :-( Thanks! ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-gui

Re: NetBSD needs inttypes.h for uintptr_t

Masao Uebayashi <[EMAIL PROTECTED]> writes: > Without this, any file can't be compiled because of lack of the > definition of uintptr_t. uintptr_t is defined in inttypes.h on my > NetBSD box, but I'm not sure if the proper entry point is it or not. configure should check for the availability of

  1   2   3   >