bug#14789: BUG: Modules compile as ELF's on PE/PE+ architecture

Hi, Thanks fro trying the development branch. Sorry that it was in a non-working state when you were using it. In the meantime, we are getting close to a 2.2 release finally, so please do report any issues you have with 2.1.3 as new bugs. I'm archiving this report as there is nothing to do. An

bug#14756: threads - par-map - multicore issue

I see this, but I'm not quite sure what's going on. What I do see is that par-map of 1+ on a list is horribly slow, both on 2.0 and master. Ludovic do you know what's going on here? Andy On Sun 30 Jun 2013 20:00, David Pirotte writes: > Hello, > > guile --version > guile (GNU Guile

bug#14653: Test failure when building on Debian armel

Hi Adam, Thanks for the report and for following up, and sorry we dropped the ball. In the meantime there are newer libgc and Guile releases, and for that reason I'm going to archive this report. Please open a new one if you have trouble with Guile 2.0.11 or 2.1.3. Be sure to use an up-to-date

bug#14640: SA_RESTART prevents execution of signal handlers

On Mon 17 Jun 2013 15:54, ludovic.cour...@inria.fr (Ludovic Courtès) writes: > When using SA_RESTART, signal handlers are never executed, as in this > example (checked on 2.0.9+): > > (sigaction SIGALRM > (lambda (signum) > (pk 'sig signum)) > SA_RESTART) > (alarm 3) > (pk 'char (read-char

bug#19676: madvise bug in guile-git

On Mon, Jun 20, 2016 at 10:34 AM, Andy Wingo wrote: > On Sat 24 Jan 2015 23:52, Linas Vepstas writes: > > > I've got a test where hit guile with maybe a dozen threads doing > > assorted things. Doing this, I then see handful of these messages: > > "madvise failed: Cannot allocate memory" every

bug#22447: (rnrs hashtables): Mutation of immutable hashtable ignored

Pinging this thread with a (very slightly) updated patch. :-) >From 7f35d515d711e255bba5a89a013d9d92034edf41 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Taylan=20Ulrich=20Bay=C4=B1rl=C4=B1/Kammer?= Date: Tue, 21 Jun 2016 00:25:19 +0200 Subject: [PATCH] Hashtable-set! errors on immutable hashtable.

bug#22446: (rnrs hashtables): Hash functions of eq? and eqv? hashtables

Also pinging this thread with a (very slightly) updated patch. :-) >From 17599f6ce7ba0beb100e80455ff99af07333d871 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Taylan=20Ulrich=20Bay=C4=B1rl=C4=B1/Kammer?= Date: Tue, 21 Jun 2016 00:23:29 +0200 Subject: [PATCH] Hashtable-hash-function returns #f on eq

bug#14549: warning while compiling guile 2.0.9

Hi, Expiring this bug due to inactivity. If you have a problem compiling Guile 2.0.11, stable-2.0, the upcoming 2.0.12, or the beta 2.1.3, let us know in new reports. Thanks! Andy On Tue 04 Jun 2013 15:43, a...@euve8129.vserver.de writes: > Hi Ludovic, > > thanks for the reply. > The compilat

bug#14361: Building guile 2.0.9 under mingw + msys

Hi Eli :) Thank you for your ongoing work on MinGW and Guile, it's really appreciated. I just wanted to say that explicitly here, even though I'm closing this bug, as I understand that things have progressed a bit in these 3 years; anyway. Your work is so valuable to many users. Thanks! Andy

bug#14347: reset, shift, continuation values truncated inconsistently

On Sat 04 May 2013 09:47, Jussi Piitulainen writes: > Hi, the following seems at least inconsistent to > me and possibly unintended: I believe it > demonstrates that the continuation captured by > `shift' passes all its values to its continuation > when it's called directly, but truncates them to

bug#14171: Aw: Re: bug#14171: REPL doesn't work on windows min-gw

Hi, Expiring this old bug. I understand that things are working better on MinGW these days but if you find a new problem with Guile 2.0.11 or the stable-2.0 branch, please file a new bug. Cheers :) Andy On Mon 15 Apr 2013 08:37, Jan Schukat writes: > Just a quick follow-up. Tried to run the

bug#14080: Guile bug building from source with pkg-config

Expiring this old bug. Please open a new one if you have new compilation failures. Thanks! Andy On Thu 28 Mar 2013 09:11, Mark Sutton writes: > Hi, > > I can ./configure make make install guile-2.0.7 from source, however, > when I then try in build guile-clutter or guile-ncurses from source I

bug#13995: Problem with macros whose expansions define and use auxiliary macros

So, this example works on master, but for reasons you don't like. We can't fix it on 2.0. If you feel that the solution for macro-introduced identifiers in 2.2 is a release blocker, let's open a thread on -devel again and talk about it, see if we can find some solutions :) In the meantime, closi

bug#13966: inlining issue?

On Fri 15 Mar 2013 13:57, Daniel Llorens writes: > Compare > > (define f (lambda (a) a)) > (call-with-values (lambda () (values 3 3)) f) > > vs > > (call-with-values (lambda () (values 3 3)) (lambda (a) a)) > > The first one fails with > > :1:0: In procedure f: > :1:0: Wrong number of arguments

bug#22152: fat_mutex owner corruption (fmoc) inside fat_mutex_unlock (guile-v2.0.11)

Mark H Weaver writes: > Iwan Aucamp writes: >> We sporadically get "mutex not locked" and "mutex not locked by current >> thread" >> exceptions on Solaris 10u10 with guile-2.0.11. > > Thanks very much for your detailed analysis and proposed fix. > > I've attached a patch that hopefully fixes th

bug#22406: Cannot compile for Windows x64 due to LLP64 model

Peter TB Brett writes: > It is not currently possible to compile Guile 2.0.11 for Windows x64 > (in particular 64-bit Windows running on the x86-64 arch). > > Most operating systems' C libraries for x86-64 use an "LP64" model, > where sizeof(long int) == sizeof(void *) == 8. > > However, for back

bug#18592: FFI should have portable access to ‘errno’

Mark H Weaver writes: > Nala Ginrut writes: > >> Is there still problem? I'm fine with the patch, and I'm expecting to >> merge it ASAP. Anyway, please don't hesitate to tell me if there's still >> any problem, I'm glad to help to do it better. I really need it. > > Sorry for the delay, but I'm

bug#12827: [PATCH] Tweak web modules, support relative URIs

I would like to apply this patch, to master at least. Any objections? We need documentation for the new exports, is the only missing thing. Andy On Sat 16 Mar 2013 15:25, Daniel Hartwig writes: > On 13 March 2013 19:05, Andy Wingo wrote: >> What's the status here, Daniel? Would be nice to fi

bug#12207: repl and comments or tabs

A very kind ping :) You didn't sign up to do this but maybe you would like to do it? I'll never know if I don't ask :) Hope you are well, & happy hacking :) Andy On Wed 15 Aug 2012 22:11, Andy Wingo writes: > Hi Neil, > > Mailing you since you were the last to touch the REPL, and perhaps you

bug#11776: bug#11784: Guile on GNU/Hurd

No update in some years; let's archive this one and if you find a new build issue with 2.0.11 or 2.1.3, let's work from there :) Andy On Mon 25 Jun 2012 23:13, l...@gnu.org (Ludovic Courtès) writes: > Hi Cyril! > > Cyril Roelandt skribis: > >> When compiling with --without-threads, I can run (+

bug#11083: guile-2.0.5 bug report

Closing as it's been 3 years without any update. Please feel free to test the latest 2.0.11 release from the 2.0 series and if you still see the bug, let us know. Cheers, Andy On Wed 13 Mar 2013 11:55, Andy Wingo writes: > Hi Kiyoshi, > > We're following up on some bugs in anticipation of a 2

bug#10627: char-ready? is broken for multibyte encodings

On Tue 26 Feb 2013 20:59, Andy Wingo writes: > On Tue 26 Feb 2013 20:50, Mark H Weaver writes: > >> Andy Wingo writes: >>> Are you proposing that `char-ready?' do a nonblocking read if >>> the buffer is empty? That could work. >> >> Yes. I suspect that something along these lines is already i

bug#22742: guile-2.1.2 make failed on Solaris10 x86

On Sat 20 Feb 2016 06:21, Kiyoshi KANAZAWA writes: > Make failed on Solaris10 x86. I believe this should be fixed with 2.1.3. Please give it a go and file another bug if that fails :) Cheers, Andy

bug#23051: segfault in master (2.1)

On Fri 18 Mar 2016 16:35, Daniel Llorens writes: > The error seems to happen in the error reporting, not actually because of the > shift. > > The following backtrace is with Guile compiled with -O1 -g, the same error > happens with -O2. > > GNU Guile 2.1.1.125-ae0380-dirty > Copyright (C) 1995-

bug#19676: madvise bug in guile-git

On Sat 24 Jan 2015 23:52, Linas Vepstas writes: > I've got a test where hit guile with maybe a dozen threads doing > assorted things. Doing this, I then see handful of these messages: > "madvise failed: Cannot allocate memory" every 5 or 10 seconds. Do you still get this with Guile 2.1.3? And

bug#22902: GUILE_INSTALL_LOCALE not equivalent to setlocale

On Fri 04 Mar 2016 04:34, Zefram writes: > The documentation claims that setting GUILE_INSTALL_LOCALE=1 in the > environment is equivalent to calling (setlocale LC_ALL "") at startup. > Actually there is at least one difference: calling setlocale causes ports > (both primordial and later-opened)

bug#22667: string->bytevector encoding error

On Sun 14 Feb 2016 23:18, Josep Portella Florit writes: > 'string->bytevector' throws 'encoding-error' when the encoding is > "UTF-16" and the length of the string is greater than 128. The same > for the encoding "UTF-32" and a string of length greater than 64. > > Tested on Guile 2.0.11 and 2.1

bug#22901: drain-input doesn't decode

On Fri 04 Mar 2016 04:09, Zefram writes: > The documentation for drain-input says that it returns a string of > characters, implying that the result is equivalent to what you'd get > from calling read-char some number of times. In fact it differs in a > significant respect: whereas read-char dec

bug#23000: update from wingo

tags 2300 +notabug close thanks On Tue 03 May 2016 11:07, Amirouche Boubekki writes: > wingo said: > >> wingo | i don't think that's a guile bug -- i think in that case you >> need to handle SIGPIPE >> wingo | b/c posix is weird >> wingo | (sigaction SIGPIPE SIG_IGN) >> wingo | the web server do

bug#21901: bit shift wrong on maximal right shift

On Fri 13 Nov 2015 11:22, Zefram writes: > With Guile 2.0.11: > > scheme@(guile-user)> (ash 123 (ash -1 63)) > $1 = 123 > > Correct result would of course be zero. Problem only occurs for > exactly this shift distance: one bit less produces the right answer. > Problem also occurs on Guile 1.8.8.

bug#21900: map is not continuation-safe

On Fri 13 Nov 2015 09:34, Zefram writes: > With Guile 2.0.11: > > scheme@(guile-user)> (define cc #f) > scheme@(guile-user)> (map (lambda (v) (if (= v 0) (call/cc (lambda (c) (set! > cc c) 0)) (+ v 1))) '(10 20 30 0 40 50 60)) > $1 = (11 21 31 0 41 51 61) > scheme@(guile-user)> (cc 5) > $2 = (61

bug#21221: guile-2.2 socket ports used with display does not send utf8 !

On Sun 09 Aug 2015 04:20, Linas Vepstas writes: > The following simple client-server program fails for me. > For simplicity, for the server, just use netcat listening on port : > > $ nc -l > > In a guile shell, try this: > (setlocale LC_ALL "") > (define sss (socket PF_INET SOCK_STREAM 0

bug#20272: Support reproducible builds

On Thu 04 Feb 2016 03:41, Mark H Weaver writes: >> Probably, ‘syntax-session-id’ would have to be a SRFI-39 parameter > > This might adversely affect the efficiency of our macro expander on > platforms with slow thread local variables I think you shouldn't worry about this. The VM keeps a point

bug#20272: Support reproducible builds

On Fri 12 Feb 2016 17:29, Mark H Weaver writes: > Mark H Weaver writes: > >> l...@gnu.org (Ludovic Courtès) writes: >> >>> Currently .go files embed randomly-generated symbols stemming from >>> ‘syntax-session-id’, which prevents reproducible builds (see >>>

bug#13827: faulty range check in bytevector accessor

Hi! Thank you very much for the bug report and fix! Applied to master, will be part of 2.1.4. Cheers, Andy On Mon 28 Jul 2014 16:35, "Ben Rocer" writes: > [resubmitting to bug-guile@gnu.org as debbugs seems to have eaten my > first mail] > > When I tried to reproduce this bug on a 32-bit x8