bug#72936: Compiler in 3.0.10 crashes when inlining 3.0.9 procedure with kw args

This one is because of 2c645571b351a0044911847025b666551a8e4fb5 :/ I will see what I can do.

bug#48368: thanks

Fixed in 17aab66e75136cf23c7f0d4942b61d6947f98f9b. Thanks for the report :)

bug#48368: reduced test case

Test case: (define (f a b) (let ((c (if (and (eq? a 'foo) (eq? b 'bar)) 'ERROR a))) (pk c))) If you run as (f 'not-foo 'bar), you get 'ERROR. Yeeps!

bug#45131: guild fails to compile a Tree-IL file

Thanks for the patch; applied! Andy On Tue 29 Dec 2020 19:09, Leo Prikler writes: > This enables the compilation from "manually" written Tree-IL to > bytecode. See also . > > * system/base/compile.scm (read-and-compile)[(joint #f)]: > Join exps using the default joi

bug#47538: ice-9 regex procedures not found when trying to use from r7rs-style defined library

Hi, On Thu 01 Apr 2021 09:06, Arvydas Silanskas writes: > foo.scm: > (define-library (foo) > (import > (scheme base) > (ice-9 regex)) > (export bar) > > (begin > (define (bar) > (make-regexp "a" The issue AFAIU is that make-regexp is part of (guile),

bug#48098: let/ec compilation bug

Thanks for the report; fixed! On Thu 29 Apr 2021 12:48, Stefan Israelsson Tampe writes: > Here is an interesting test case that shows that fi we define > (define-syntax-rule (letec-m f) (let/ec c (f c))) > (define(letec-f f) (let/ec c (f c))) > > we can get two different beh

bug#40252: Applied

Thanks for the report and fix, and apologies for the delay! Andy

bug#48089: Guile 3.0.6 returns zero-indexed locations for ‘read-error’

Done :) On Thu 29 Apr 2021 11:33, Ludovic Courtès writes: > Ludovic Courtès skribis: > >> Guile 3.0.6 returns zero-indexed (instead of one-indexed) source code >> locations for ‘read-error’. Here’s a 3.0.6/3.0.5 comparison: >> >> $ /gnu/store/r2nr74rwhpqg16y1lyi6l0jn3lwx4yyz-guile-3.0.6/bin/gu

bug#48096: [3.0.6] ‘syntax-error’ exceptions include vectors instead of source location properties

Done! On Thu 29 Apr 2021 11:41, Ludovic Courtès writes: > Hi! > > In 3.0.6, a slight incompatibility crept in: ‘syntax-error’ exceptions > include vectors like #("example.scm" 1 2) instead of good’ol source > property alists. > > Here is a test case that reproduces the problem: > > diff --git a/

bug#46175: Redefinable classes clobber custom slot options

On Fri 29 Jan 2021 17:43, "Thompson, David" writes: > The compute-slots method for does a transformation > of #:allocation #:instance slots to #:allocation #:virtual slots, but > in doing so it discards all slot options besides the standard ones. > This means that a metaclass that inherits from

bug#41131: Bug in hash-table-merge! (and patch)

Applied, thanks! On Fri 08 May 2020 01:50, "Ricardo G. Herdt" writes: > Hi, > > I just found this bug in the hash-table-merge! function > (modul/srfi/srfi-69.scm). Instead of merging both hash tables, it was > ignoring one of them (other-ht). Attached is the fix, where it now folds > over other

bug#40371: [R7RS] Guile does not accept library name parts that are non-negative exact integers

In the concrete case of the SRFI modules, importing e.g. (srfi 9) works AFAIU. Does this not work for you? I think that allowing numbers as module name components, beyond the SRFI modules, is not currently a good idea for Guile. I had a look at it and it's a bit too intrusive. Andy On Wed 01 A

bug#39634: All keyowrds hash to the same value

On Fri 06 Mar 2020 15:42, Ludovic Courtès writes: > Andy Wingo skribis: > >>> variable, >>> hashtable, >>> fluid, >>> dynamic_state, >>> frame, >>> atomic_box, >>> program, >>> vm_cont, >>>

bug#39800: gnutls guile bug receiving https data

Thanks very much for the report! I think this one may be a good one for Ludovic, if I may be so bold. Apologies for the top-post but I couldn't clip your excellent report. Cheers, Andy "franco@gmail.com" writes: > Hello, > I installed gnutls for guile and checked the gnutls module with

bug#39811: Missing dynwind exit application

Stefan Israelsson Tampe writes: > Executing this code on guile-3.0.0: > > (dynamic-wind > (lambda () (pk 'enter)) > (lambda () (catch #t > (lambda () (throw 1)) > (lambda x (pk 'catch x) (apply throw x > (lambda () (pk 'leave))) > > Leads to the output: > > sche

bug#39855: PKG_GUILE does not find guile

Julien Lepiller writes: > I have a project I used to build with guile 2.2. I use the PKG_GUILE m4 > macro in my configure.ac. However, guile 3 comes with a guile.m4 whose > PKG_GUILE only checks for 2.2, 2.0 and 1.8, so configure fails. > > Is this deprecated? Should I use something else to check

bug#39634: All keyowrds hash to the same value

On Thu 20 Feb 2020 17:19, Ludovic Courtès writes: > Of all the scm_tc7_ values listed in ‘scm.h’, the following are not > explicitly listed (so they go to the default case that hashes the first > word): Reformatting your list so I can check one by one :) > variable, > hashtable, > fluid,

bug#39651: /software/guile/docs/ lacks 3.0

Michael Shigorin writes: > Hello, > a forum commenter has brought my attention to the fact that > https://www.gnu.org/software/guile/docs/ page mentions "Preview > Reference Manual for unreleased Guile 2.2 (development branch)" > and fails to mention 3.0 completely (even if it's been releas

bug#39118: Segfault while building on 64-bit Cygwin

Aah, you all are amazing -- thank you!! Applied and merged. Cheers, Andy On Mon 17 Feb 2020 20:27, Charles Stanhope writes: > On 2/16/20, Charles Stanhope wrote: >> On 2/16/20, Mike Gran wrote: >>> >>> I can confirm that Charles's patch, plus another one line patch >>> to define CPU_SETSIZE

bug#39573: [3.0.0] Compiler fails to optimize out side-effect-free expression

On Wed 12 Feb 2020 12:50, Ludovic Courtès writes: > Hello! > > Consider this loop: > > (let loop ((n (expt 2 18)) > (i 1)) > (unless (zero? n) > (loop (- n 1) > (logior 0 (ash i 1) > > Guile 2.2 strips away the computation of ‘i’ (it cannot throw, has no >

bug#39118: Segfault while building on 64-bit Cygwin

On Mon 20 Jan 2020 18:22, Mike Gran writes: > On Mon, Jan 20, 2020 at 11:38:35AM -0500, John Cowan wrote: >> Yes, gladly, but I don't know how to get one in this context. Do I need to >> add some flags to the Makefile, and if so, where? (It's a twisty maze of >> passages, all different.) . Note

bug#36915: make-thread-local-fluid ignores the default value

On Sun 04 Aug 2019 00:46, Caleb Ristvedt writes: > In Guile 2.2.6 as packaged on Guix System (x86-64), the following > happens: > > -- > (define some-fluid (make-thread-local-fluid 42)) > > (display (fluid-ref some-fluid)) > > => #f > --

bug#38263: Bug in srfi-11

Applied to both branches. Thanks for the patch and thanks also to Mark for the review and initial patch! In the future, Tim, if you have larger patches, we should work out copyright assignment paperwork. But less-than-10-line patches are fine without. Let me know if this is of interest to you.

bug#38516: [guile-2.9.6] make failed on Solaris x86/x64

On Sat 07 Dec 2019 01:12, Kiyoshi KANAZAWA writes: > Hello, > > Trying guile-2.9.6. > Make fails on Solaris x86/64 with 32 bit mode. > It does not happen with 64 bit mode. > > $ make >   : >   CC   libguile_3.0_la-ioext.lo >   CC   libguile_3.0_la-jit.lo > jit.c: In function 'compile_s64_

bug#38534: fluid-ref doesn't return defaults for thread local fluids

On Sun 08 Dec 2019 18:41, Rob Browning writes: > For example, in 2.2.6: > > scheme@(guile-user)> (define x (make-thread-local-fluid 'default)) > scheme@(guile-user)> (fluid-ref x) > $1 = #f Applied your patch on both branches; thank you! Andy

bug#38607: unable to build guile 2.9.7 on OS X 10.14.6

On Sat 14 Dec 2019 07:16, Aleix Conchillo Flaqué writes: > BOOTSTRAP GUILEC system/vm/linker.go > /bin/sh: line 1: 69110 Abort trap: 6 GUILE_AUTO_COMPILE=0 > ../meta/build-env guild compile --target="x86_64-apple-darwin18.7.0" -O1 > -Oresolve-primitives -L > "/Users/aleix/guile-2.9.

bug#38672: Core records and R7RS records

On Thu 19 Dec 2019 17:24, Marc Nieper-Wißkirchen writes: > I've read in the news that the upcoming Guile 3.0 will unify records. > > Core records type seem to support the procedure "record-accessor", > which takes a field name as a symbol. > > In R7RS (based on SRFI 9), record field names are, h

bug#38611: Guile 2.9.7 regression: "duplicate" record field names

On Sat 14 Dec 2019 14:31, Göran Weinholt writes: > The following program works in Guile 2.2.6 (and other R6RS > implementations), but raises an exception in Guile 2.9.7. A field called > "name" exists in record type a and record type b, but there is no actual > naming conflict as I understand it.

bug#38617: should internal defines be callable with incorrect number of args?

On Sun 15 Dec 2019 02:02, Christopher Lam writes: > See snippet below. > IMHO the second call to add1 should fail. On guile-2.2.6 it does not error > out. > On guile-2.0 it does throw error (as I think it should). > Is this intentional? OMG what an embarrassing bug! Thank you for finding and

bug#38895: Autoloads behave differently in Guile ≥ 2.9.7

On Fri 03 Jan 2020 16:56, Ludovic Courtès writes: > It seems that since 2.9.7, autoloads have to specify exactly all the > bindings of the autoloaded module that the user will ever reference. > Bindings that are omitted from the #:autoload clause remain unbound: Indeed. This was an unintentiona

bug#38760: R7RS define-library form is not supported

Thanks for the report; fixed! Patches welcome if there are any bugs :) Cheers, Andy

bug#38388: [2.9.5] Inaccurate source location info for unbound variables

On Thu 28 Nov 2019 09:20, Ludovic Courtès writes: >>> I have a test that runs ‘guix system build’ on this file: >>> >>> (use-modules (gnu)) ; 1 >>> (use-service-modules networking) ; 2 >>> >>> (operating-system

bug#38388: [2.9.5] Inaccurate source location info for unbound variables

Hi, On Tue 26 Nov 2019 16:20, Ludovic Courtès writes: > I have a test that runs ‘guix system build’ on this file: > > (use-modules (gnu)) ; 1 > (use-service-modules networking) ; 2 > > (operating-system ;

bug#38348: [2.9.5] Stack overflow when stdout is closed

Hey :) On Sat 23 Nov 2019 17:46, Ludovic Courtès writes: > Hello! > > Guile 2.9.5 segfaults from a C stack overflow when you start it with a > closed stdout: > > /gnu/store/7vwf3nhiacxc2jgcg43w22px4ds3rb36-guile-next-2.9.5/bin/guile -c > '(pk 1)' >&- Fixed, thanks! Cheers, Andy

bug#38236: R7RS reader does not support datum labels

Hey! On Mon 18 Nov 2019 16:10, Mark H Weaver writes: > Andy Wingo writes: > >> R7RS defines a lexical feature called "datum labels"; see section 2.4 in >> the report. An example would be: >> >>#0=(a b c . #0#) >> >> Guile's rea

bug#38239: hungry-eol-escapes reader option doesn't allow intraline whitespace

Guile supports the R7RS idiom whereby this: "foo\ bar" reads as "foobar" In the R6RS, this syntax is specified as allowing intraline whitespace (space, tab, and anything Unicode with category Zs) after the \ but before the newline. However in Guile we don't support this and signal an

bug#38238: (call-with-input-string "( . 42)" read) => 42

Guile has a strange syntax extension, as described in the bug title. It's not explicitly documented AFAIU and it seems it may simply be a mistake. We should consider making ( . 42) a lexical error.

bug#38237: I/O errors do not currently have their own exception type

For R7RS, this should be true: (file-error? (guard (exn (else exn)) (open-input-file " no such file "))) However currently an error during Guile's open-input-file doesn't raise a specific-enough exception for file-error? to be implementable. Something to fix.

bug#38236: R7RS reader does not support datum labels

R7RS defines a lexical feature called "datum labels"; see section 2.4 in the report. An example would be: #0=(a b c . #0#) Guile's reader doesn't support this feature and it's not clear if we should, in general. Note, datum literals appear to be incompatible with array literals. But we coul

bug#38235: string-foldcase bug for trailing sigma

Given the following example, using (rnrs unicode): (string-foldcase "ΜΈΛΟΣ") The expected result is "μέλοσ"; see R6RS libraries section 1.2. However instead Guile's result is "μέλος". Note that although Σ usually downcases to σ, at the end of a string it's ς. This test shows a limitation of

bug#33652: close thanks

close thanks Fixed in master. Thanks very much for the report and patch!

bug#33036: Bug with the procedure nil? inside a specific code

Hi! Thank you, Mark! That looks great. I note also that this is fixed in master, unless I made another bug. See type-fold.scm:66-87 and types.scm:574-617. Cheers! Andy On Sun 14 Oct 2018 06:05, Mark H Weaver writes: > Mark H Weaver writes: > >> calcium writes: >>> Here is the bug that I f

bug#29669: repl-print - requet for iprovement

On Sun 01 Jul 2018 18:26, l...@gnu.org (Ludovic Courtès) writes: > Hello, > > David Pirotte skribis: > >> From d920d22efe3e77d23004122e21cec420c402f531 Mon Sep 17 00:00:00 2001 >> From: David Pirotte >> Date: Mon, 11 Dec 2017 21:28:24 -0200 >> Subject: [PATCH] Updating repl-print to use truncate

bug#30066: 'get-bytevector-some' returns only 1 byte from unbuffered ports

On Fri 12 Jan 2018 11:15, l...@gnu.org (Ludovic Courtès) writes: > Andy Wingo skribis: > >> On Thu 11 Jan 2018 22:55, Mark H Weaver writes: > > [...] > >>>>> Out of curiosity, is there a reason why you're using an unbuffered port >>>>> in

bug#30066: 'get-bytevector-some' returns only 1 byte from unbuffered ports

On Thu 11 Jan 2018 22:55, Mark H Weaver writes: > l...@gnu.org (Ludovic Courtès) writes: > >> Mark H Weaver skribis: >> >>> l...@gnu.org (Ludovic Courtès) writes: >> >> [...] >> + if (SCM_UNBUFFEREDP (port) && (avail < max_buffer_size)) +{ + /* PORT is unbuffered. Read

bug#30066: 'get-bytevector-some' returns only 1 byte from unbuffered ports

On Wed 10 Jan 2018 17:58, Nala Ginrut writes: > hi Andy and Ludo! > > What if developers enabled suspendable-ports and set the port to non-blocking? > For example, in the non-blocking asynchronous server, I registered > read/write waiter for suspendable-ports. And save > delimited-continuations t

bug#30066: 'get-bytevector-some' returns only 1 byte from unbuffered ports

On Wed 10 Jan 2018 16:59, l...@gnu.org (Ludovic Courtès) writes: > l...@gnu.org (Ludovic Courtès) skribis: > >> As discussed on IRC, ‘get-bytevector-some’ returns only 1 byte from >> unbuffered ports: > > Here’s a tentative fix. WDYT? Thanks! Needs a little work though :) Comments inline. > -

bug#19180: Weak tables harmful to GC?

escr’ in weaks.c in > 2.0.) Good idea; fixed. Andy >From 098c4171ef53791d97b5c675218f302efc7bcf26 Mon Sep 17 00:00:00 2001 From: Andy Wingo Date: Tue, 31 Oct 2017 09:10:55 +0100 Subject: [PATCH 2/3] Refactor weak table to use bitmaps for weak entries --- libguile/weak-table.c | 107 +

bug#19180: Weak tables harmful to GC?

>From 6ec4642516eaabf7a63644463a7836eb3efbcd60 Mon Sep 17 00:00:00 2001 From: Andy Wingo Date: Mon, 30 Oct 2017 18:19:37 +0100 Subject: [PATCH] Weak tables are now bucket-and-chain tables This change should make weak tables work better with libgc, as the weak components that need mark functions are smaller, so they don&#x

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

On Tue 21 Jun 2016 15:22, l...@gnu.org (Ludovic Courtès) writes: > Andy Wingo skribis: > >> 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. > > On a quick glance that look

bug#12207: repl and comments or tabs

On Thu 04 Aug 2016 22:55, Andy Wingo writes: > On Thu 28 Jul 2016 19:21, "helpful.user@discard.email" > writes: > >> The following patch to readline should fix the tab issue: >> >> https://lists.gnu.org/archive/html/bug-bash/2014-10/msg00211.html >

bug#26858: Cygwin port of Guile 2.2

Greets, On Fri 12 May 2017 16:13, Derek Upham writes: > Andy Wingo writes: > >> scm_join_thread isn't actually implemented in terms of >> scm_i_pthread_join any more. Probably that's what's going wrong here -- >> and probably that should be fixed to ens

bug#26675: guile-2.2.0 in GNU/Hurd

On Thu 27 Apr 2017 04:35, rennes writes: > We are testing guile-2.2.0 in GNU/Hurd, we have passed the build phase > setting "--disable-largefile" parameter to configure script. > On the other hand in the check phase, get the error: > > wrote > `/tmp/guix-build-guile-2.2.0.drv-0/guile-2.2.0/ca

bug#26151: date-year-day screws up leap days prior to AD 1

On Sat 18 Mar 2017 02:10, Zefram writes: > If I had implemented SRFI-19 myself, without reference to existing > implementations, I would have implemented astronomical year numbering > (consistent AD year numbering, extending linearly in both directions), > as used in ISO 8601. This is the most c

bug#26149: SRFI-19 doc erroneously warns about Gregorian reform

On Wed 19 Apr 2017 18:11, Zefram writes: > Andy Wingo wrote: >>This makes sense to me, FWIW. > > Patch attached. Thank you! Applied. I adapted the change log message to follow Guile conventions; it was: > From 444703940983d559935c4dd2a2c89d7888c67119 Mon Sep 17 00:00:00 2

bug#26583: 2.2.1 syntax objects are not comparable

On Thu 20 Apr 2017 22:52, l...@gnu.org (Ludovic Courtès) writes: > The “new” syntax objects in 2.2.1 cannot be compared with ‘equal?’, > unlike the “old” ones, which were just vectors. I think this is a bug. We can roll another release today. Andy

bug#26013: (srfi srfi-37) chokes on empty string parameter

On Wed 19 Apr 2017 18:32, Thomas Danckaert writes: >> On Tue 07 Mar 2017 16:34, Thomas Danckaert >> writes: >> >>> It looks like Guile's srfi-37 implementation doesn't process empty >>> string arguments correctly. > I don't fully understand the code in srfi-37.scm, but I think the fix > can be a

bug#26570: GC_is_heap_ptr() dep for 2.2.1

On Thu 20 Apr 2017 01:19, Zefram writes: > Compilation of 2.2.1 fails for me, producing a lot of warnings about > implicit declaration of GC_is_heap_ptr(), and ultimately > > CCLD guile > ./.libs/libguile-2.2.so: undefined reference to `GC_is_heap_ptr' > collect2: error: ld returned 1 exit

bug#26570: GC_is_heap_ptr() dep for 2.2.1

On Thu 20 Apr 2017 01:19, Zefram writes: > Compilation of 2.2.1 fails for me, producing a lot of warnings about > implicit declaration of GC_is_heap_ptr(), and ultimately > > CCLD guile > ./.libs/libguile-2.2.so: undefined reference to `GC_is_heap_ptr' > collect2: error: ld returned 1 exit

bug#25509: FreeBSD 11.0

On Thu 16 Mar 2017 04:11, Matt Wette writes: > HI saffron, > > I have been able to get guile-2.1.8 to build on FreeBSD 11.0. > > I had to “pkg install” : pkgconf, gmake, boehm-gc-threaded > > Then to work around following config issue, I “pkg install autotools” > Edit autoconf.ac and find “bdw-gc

bug#25803: [PATCH] guile-snarf: skip -g* arguments to avoid build failure

On Sun 19 Feb 2017 23:58, Sergei Trofimovich writes: > The fix is to ignore -g* flags. They should only affect debugging output. > > * libguile/guile-snarf.in: skip -g* arguments to avoid build failure Applied. Thanks :) Andy

bug#25804: [PATCH] api-procedures.texi: typo: 'an' -> 'on'

On Mon 20 Feb 2017 00:02, Sergei Trofimovich writes: > * doc/ref/api-procedures.texi: fix typo 'an' -> 'on' Applied. Thanks :) Andy

bug#25805: [PATCH] tweak 'u+0007' to 'U+0007' (as the rest of the table)

On Mon 20 Feb 2017 00:02, Sergei Trofimovich writes: > * doc/ref/api-data.texi: tweak codepoint notation Applied; thanks! Andy

bug#26013: (srfi srfi-37) chokes on empty string parameter

On Tue 07 Mar 2017 16:34, Thomas Danckaert writes: > It looks like Guile's srfi-37 implementation doesn't process empty > string arguments correctly. For example, here's a stacktrace I get when > executing guix system list-generations "": > > $ guix system list-generations "" > Backtrace: > In i

bug#26026: Defining a method named zero? breaks primitive zero?

On Wed 08 Mar 2017 12:07, Alejandro Sanchez writes: > If I define a ‘zero?’ predicate method for a custom class the primitive > ‘zero?’ is lost. Here is a simple vector module: > > ;;; File vector2.scm > (define-module (vector2) > #:use-module (oop goops) > #:export (

bug#26027: (system vm trace) creates no output

On Wed 08 Mar 2017 18:01, Mike Gran writes: > Hi- > I created the following file, which I ran under guile-2.0 and master. > There is no tracing output. What am I misunderstanding? > (use-modules > (system vm trace)) > > (define (write-hi) > (write "hi")) > > (define (outer) > (write-hi)) >

bug#26106: Defining a method named '-' with one parameter

On Wed 15 Mar 2017 14:35, Alejandro Sanchez writes: > If I define a method named ‘-‘ which only takes in one parameter, the > expression ‘(- v)’ gets rewritten to ‘(- 0 v)’. Here is a minimal example: > > (use-modules (oop goops)) > > (define-class () > (x #:init-valu

bug#26123: guile-2.2.0: AI_ADDRCONFIG

On Fri 17 Mar 2017 14:11, writes: > Thomas Klausner wrote: >> >> SNARF net_db.doc >> net_db.c:468:***Missing or erroneous `#define FUNC_NAME s_AI_ADDRCONFIG);' >> net_db.c:488:***Missing or erroneous #undef for AI_ADDRCONFIG);: >> >> Compilation continues even though this looks like a

bug#26128: 1 of 1 test failed

On Thu 16 Mar 2017 16:45, Jean Louis writes: > Hello, > > This may help you, it failed on 2.2. Maybe not serious. > > Jean > > Running peval.test > Running poe.test > Running popen.test > Running ports.test > warning: call to primitive-fork while multiple threads are running; > further b

bug#26149: SRFI-19 doc erroneously warns about Gregorian reform

On Sat 18 Mar 2017 00:53, Zefram writes: > The documentation, near the start of the section on SRFI-19, says > > !*Caution*: The current code in this module incorrectly extends the > ! Gregorian calendar leap year rule back prior to the introduction of > ! those reforms in 1582 (or the approp

bug#26164: time-difference mishandles leap seconds

On Sat 18 Mar 2017 23:41, Zefram writes: > Computing the duration of the period between two UTC times, using > SRFI-19 mechanisms: > > scheme@(guile-user)> (use-modules (srfi srfi-19)) > scheme@(guile-user)> (define t0 (date->time-utc (make-date 0 59 59 23 30 6 > 2012 0))) > scheme@(guile-user)

bug#26172: [PATCH] bug: statprof flat display writes summary lines to current-output-port instead of the provided port

On Sun 19 Mar 2017 16:26, Freja Nordsiek writes: > Small bug I found when using the statprof module when using the > statprof procedure with a flat display. The summary lines at the end > are not written to the port provided as an argument and are instead > written to (current-output-port). A pat

bug#26182: cond-expand doc omits guile-2.2 feature

On Mon 20 Mar 2017 02:22, Zefram writes: > As implemented in Guile 2.2.0, the unlisted feature guile-2.2 is also > recognised by cond-expand. Added to doc; tx for report. Andy

bug#26183: patch for guile-2.2.0 on FreeBSD 11.0

On Mon 20 Mar 2017 02:39, Matt Wette writes: > Attached is a patch to apply to guile-2.2.0 to compile on FreeBSD 11.0 > Changes > 1) updated README to indicate which extra FreeBSD packages need to be > installed > 2) minor change to configure.ac (implies autoconf needs to run) to use > bdw-gc-t

bug#26188: Minor typo in manual (7.20.5 SXML Tree Fold)

Hi, On Mon 20 Mar 2017 07:10, Arun Isaac writes: > In the second line of the argument specification of scheme procedure > `fold-layout', "handler-pair" is misspelt as "bandler-pair". Thanks, fixed. Patches welcome in the future too :) Andy

bug#26240: Guile doesn't search for libraries installed in /usr/lib64

On Fri 24 Mar 2017 17:59, "Stewart, Adam James" writes: > $ ls -l /usr/lib64/libltdl.so.7* > lrwxrwxrwx 1 root root 16 Feb 27 11:19 /usr/lib64/libltdl.so.7 -> > libltdl.so.7.3.0 > -rwxr-xr-x 1 root root 41248 Feb 16 2016 /usr/lib64/libltdl.so.7.3.0 > > Do you have any suggestions as to how I can

bug#26259: ~f SRFI-19 format broken for small nanoseconds values

On Sun 26 Mar 2017 04:00, Zefram writes: > scheme@(guile-user)> (date->string (make-date 55 56 34 12 26 3 2017 0) > "~f") > $2 = "56.5e-4" Thanks for the report. Fixed in the the fix for #26260; added the test case anyway. Cheers. Andy

bug#26260: ~f SRFI-19 format specifier mishandles one-digit seconds value

thanks

bug#26260: ~f SRFI-19 format specifier mishandles one-digit seconds value

On Sun 26 Mar 2017 04:09, Zefram writes: > The ~f format specifier for SRFI-19's date->string is documented as: > > #~f seconds and fractional seconds, with locale > # decimal point, eg. `5.2' > > Let's test that example: > > scheme@(guile-user)> (use-modules (srfi srfi-19)) > s

bug#26261: ~N mishandles small nanoseconds value

On Mon 27 Mar 2017 18:06, Andrew Moss writes: > I believe I have fixed this bug, but I'm not sure if I put the test > case in the right place within the file. Please see the attached > patch. > > From e975f8ae8d494985a51faed5b15c5664a557e0e2 Mon Sep 17 00:00:00 2001 > From: Andrew Moss > Date: M

bug#26329: monotonic time not supplied by current-time

On Sat 01 Apr 2017 13:18, Zefram writes: > The SRFI-19 current-time function can return several flavours of the > current time: > > scheme@(guile-user)> (use-modules (srfi srfi-19)) > scheme@(guile-user)> (current-time time-utc) > $1 = # > scheme@(guile-user)> (current-time time-tai) > $2 = # > s

bug#26351: Out of Memory tests failing on i686 and Power64

On Mon 03 Apr 2017 18:04, John Dulaney writes: > I am consistently getting the out of memory test to fail on i686 and 64 bit > Power. > > Build logs are as follows: > > i686 on Fedora Rawhide (what will be F27): > https://kojipkgs.fedoraproject.org//work/tasks/4744/18694744/build.log > > 64 bit P

bug#26476: Help for C primitives not found

On Thu 13 Apr 2017 13:25, writes: > So. (help cons) is no longer working for me with 2.2. > > The output of > > echo '(help cons)' | strace guile > > shows > > stat("/usr/local/share/guile/guile-procedures.txt", 0x7ffd5f923330) = -1 > ENOENT (No such file or directory) > stat("/usr/local/share

bug#26503: Local variables reclaimed early vs. finalizers

On Wed 19 Apr 2017 11:50, l...@gnu.org (Ludovic Courtès) writes: > I need to chew a bit more on this, but the conclusion is probably that > my expectations were incorrect, indeed. :-) OK I close this bug in the meantime then :) Feel free to reopen if there is a thing to do! Andy

bug#26542: guile 2.0.13

Hi, ro...@web.de writes: > Hello, > > The attached simple test calls free functions with bad smob_tag. > I see the same stuff with 2.2.0 > There are no errors using the stable 2.0.11 version. > > static size_t > free_box (SCM box_smob) > { > if (SCM_TYP16(box_smob) != scm_tc16_box) { >

bug#26503: Local variables reclaimed early vs. finalizers

l...@gnu.org (Ludovic Courtès) writes: > Consider this code: > > (use-modules (system foreign)) > > (define %abort > (dynamic-func "abort" (dynamic-link))) > > (let ((ptr (make-pointer 123 %abort))) > (display "hello\n") > (gc)) > > Guile is free to collect ‘ptr’ when ‘gc’ is called since it

bug#26058: utf16->string and utf32->string don't conform to R6RS

On Tue 14 Mar 2017 16:03, taylanbayi...@gmail.com (Taylan Ulrich "Bayırlı/Kammer") writes: > Andy Wingo writes: > >> On Mon 13 Mar 2017 19:10, taylanbayi...@gmail.com (Taylan Ulrich >> "Bayırlı/Kammer") writes: >> >>> If I do binary I/O,

bug#24657: Autoconf macro GUILE_PROGS only looks for guile without version suffix even if given version - patch included

On Tue 14 Mar 2017 15:25, Freja Nordsiek writes: > Found a bug in the modifications you made. Sorry for not catching this > before it got included into the Guile 2.1.8 release. Thank you! Applied. Note that in the gnu coding standards you need an entry in the commit log for every file you modi

bug#25791: address argument to atomic operation must be a pointer to _Atomic type with 2.1.7 on macOS

On Wed 01 Mar 2017 17:43, Andy Wingo writes: > On Sun 19 Feb 2017 09:41, ilove zfs writes: > >> On macOS 10.11 and 10.12 building with Xcode 8, guile 2.1.7 fails to >> compile with several errors saying "address argument to atomic >> operation must be a pointer to

bug#25912: 2.1.7 segfaults on cygwin

On Fri 03 Mar 2017 15:32, Mike Gran writes: > I also can replicate the Cygwin problem as originally described. I understand that with the fix in 2.1.8, that things are working correctly now; closing the report. Thanks for the sleuthing, szgyg and Mike! Andy

bug#25923: pkgsrc patches: improve mkostemp support

On Wed 01 Mar 2017 21:29, Thomas Klausner writes: > --- libguile/filesys.c.orig 2016-12-15 00:03:33.0 + > +++ libguile/filesys.c > @@ -1486,6 +1486,15 @@ SCM_DEFINE (scm_i_mkstemp, "mkstemp!", 1 >mode_bits = scm_i_mode_bits (mode); > } > > +#ifdef __APPLE__ > + /* ht

bug#25922: pkgsrc patches: older Darwin support

On Wed 01 Mar 2017 21:28, Thomas Klausner writes: > Another pkgsrc patch concerns itself with supporting older Darwin > releases, attached. Can you please merge it? > Thomas > > $NetBSD: patch-libguile_stime.c,v 1.1 2016/10/19 14:56:17 adam Exp $ > > Fix building on Darwin. > > --- libguile/stim

bug#25921: pkgsrc patches: Dragonfly support

On Wed 01 Mar 2017 21:27, Thomas Klausner writes: > $NetBSD: patch-lib_signal.in.h,v 1.1 2016/12/03 03:15:33 marino Exp $ > > DragonFly support. > > --- lib/signal.in.h.orig 2016-06-29 09:12:27 UTC > +++ lib/signal.in.h > @@ -61,6 +61,7 @@ > #if (@GNULIB_PTHREAD_SIGMASK@ || defined GNULIB_P

bug#26058: utf16->string and utf32->string don't conform to R6RS

On Mon 13 Mar 2017 19:10, taylanbayi...@gmail.com (Taylan Ulrich "Bayırlı/Kammer") writes: > If I do binary I/O, the following situations are possible: > > 1. I'm guaranteed to get any possible bytes that happen to form a valid >BOM at the start of the stream as-is in the returned bytevector;

bug#26058: utf16->string and utf32->string don't conform to R6RS

On Sat 11 Mar 2017 13:19, taylanbayi...@gmail.com ("Taylan Ulrich "Bayırlı/Kammer"") writes: > See the R6RS Libraries document page 10. The differences: > > - R6RS supports reading a BOM. > > - R6RS mandates an endianness argument to specify the behavior at the > absence of a BOM. > > - R6RS a

bug#26059: Sorry about the duplicate.

On Sat 11 Mar 2017 19:30, taylanbayi...@gmail.com (Taylan Ulrich "Bayırlı/Kammer") writes: > Please ignore this, as it's a duplicate of #26058.

bug#24544: 2.1.4 tarball install fails on GuixSD

On Sat 11 Mar 2017 12:33, l...@gnu.org (Ludovic Courtès) writes: > Andy Wingo skribis: > >> On Sun 25 Sep 2016 21:22, Jan Nieuwenhuizen writes: >> >>> ld-wrapper: error: attempt to use impure library >>> "/home/janneke/guile-2.1.4/lib/libguile-2.2.s

bug#26040: Guile tests that cannot work on MS-Windows and should be disabled

Forwarded bug report from Eli on guile-devel. On Sat 23 Jul 2016 13:49, Eli Zaretskii writes: > These tests are: > > . ftw.test, which fails because ftw is not available: > > FAIL: ftw.test: file-system-fold: test-suite > ERROR: ftw.test: file-system-fold: EACCES - arguments: > ((unb

bug#20938: make-dynamic-state, with-dynamic-state & exceptions

On Fri 03 Mar 2017 23:15, Josep Portella Florit writes: > On 03/01/2017 06:30 PM, Andy Wingo wrote: >> On Wed 01 Mar 2017 16:11, Josep Portella Florit writes: >>> (Today I've tested it with 2.1.7.22-fcebf and it still crashed.) >> >> Ack, I didn't actua

bug#20272: Support reproducible builds

Hi, On Sun 05 Mar 2017 21:49, l...@gnu.org (Ludovic Courtès) writes: > Andy Wingo skribis: > >> On Thu 22 Dec 2016 00:53, l...@gnu.org (Ludovic Courtès) writes: >> >>> +(define (module-generate-unique-id! m) >>> + (let ((i (module-next-unique-id m))) >>

  1   2   3   4   5   6   7   8   9   10   >