bug#79479: Issue with substring/shared

On Sun, Sep 21, 2025 at 12:47 AM Nikolaos Chatzikonstantinou wrote: > > Hello bug-guile, > > I have a structure (srfi srfi-9 gnu) that keeps parts of strings in a > binary tree (it's a rope). The intention was to have it immutable, so > I used substring/shared. I kept ge

bug#79415: [PATCH] Fix tmpfile close on execute

Fixed in main: via https://codeberg.org/guile/guile/commit/37b4f7146c1a93b38fb3a3945d74ba6f4f6b81ce 37b4f7146c1a93b38fb3a3945d74ba6f4f6b81ce tmpfile: preserve O_CLOEXEC so children won't prevent removal Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E

bug#79549: SRFI-13 is missing KMP string search procedure

sting KMP. I wanted to put this bug report out in the list; I might work on this as it affects something that I need. Regards, Nikolaos Chatzikonstantinou

bug#79483: Segmentation fault: set-car! in compiled code

On Mon, Sep 22, 2025 at 09:27:54PM +0200, Tomas Volf wrote: > writes: > > > On Mon, Sep 22, 2025 at 12:50:57AM +0300, var-vniiaes--- via Bug reports > > for GUILE, GNU's Ubiquitous Extension Language wrote: > >> > >> Hello, > >>   > &g

bug#79494: Issue with posix_spawn_file_actions_addclosefrom_np on FreeBSD 13.1+ and 14+

Hello list, I would like to summarize an issue [1] that first came up on the FreeBSD bugzilla for Guile 3.0.10. It's a segfault due to the incorrect mixing of two separate APIs for Posix spawn. As Tobias Kortkamp clarifies there, the gnulib rpl_posix_spawn*() functions are picked up by Guile's au

bug#79483: Segmentation fault: set-car! in compiled code

writes: > On Mon, Sep 22, 2025 at 12:50:57AM +0300, var-vniiaes--- via Bug reports for > GUILE, GNU's Ubiquitous Extension Language wrote: >> >> Hello, >>   >> Execution of   (set-car! '(0) 1)   *in compiled code*  leads to segfault: > > First of a

bug#79483: Segmentation fault: set-car! in compiled code

On Mon, Sep 22, 2025 at 12:50:57AM +0300, var-vniiaes--- via Bug reports for GUILE, GNU's Ubiquitous Extension Language wrote: > > Hello, >   > Execution of   (set-car! '(0) 1)   *in compiled code*  leads to segfault: First of all: you shouldn't be doing that :) You

bug#79483: Segmentation fault: set-car! in compiled code

Hello,   Execution of   (set-car! '(0) 1)   *in compiled code*  leads to segfault:   amaya@AM4:~$ guile-3.0 --version guile (GNU Guile) 3.0.10 Packaged by Debian (3.0.10+really3.0.10-4) Copyright (C) 2024 Free Software Foundation, Inc.   License LGPLv3+: GNU LGPL 3 or later

bug#79479: Issue with substring/shared

Hello bug-guile, I have a structure (srfi srfi-9 gnu) that keeps parts of strings in a binary tree (it's a rope). The intention was to have it immutable, so I used substring/shared. I kept getting errors on my unit tests when I referenced individual characters; I could not replicate these e

bug#79461: n-par-for-each do not propagate exceptions

Hi, The documentation of `n-par-for-each' (info "(guile) Parallel Forms") does not mention that errors thrown in the procedure run in parallel are absorbed, instead of relayed to the control code to be handled. Here's an example: --8<---cut here---start->8---

bug#79451: (web server http) make-default-socket hard-codes PF_INET

scheme@(guile-user)> (use-modules (web server)) scheme@(guile-user)> (define (handler request body) (values '((content-type . (text/plain))) "Hello world")) scheme@(guile-user)> (run-server handler 'http `(#:family ,AF_INET6 #:port 8081)) Expected result: A Web server starts and serves "Hello wo

bug#79450: (web server) documentation is wrong

INET6 #:port 8081)) Note that this example currently doesn't work because of another bug (make- default-socket hard-codes PF_INET) which I have reported in another message. I would fix the manual myself but I don't know texinfo. (Question: Did anyone test this example before publishing

bug#78789: make-struct/no-tail segfault

Version: 3.0.11 Ido Yariv writes: > Calling make-struct/no-tail with an incorrect layout type could lead > to a segmentation fault. Thanks for the report. Should be fixed in main now via commit 9b00131539ca11a8112a4e88187e45bd40a6f7a7 make-struct/no-tail scm_c_make_structv: ensure layout

bug#79415: [PATCH] Fix tmpfile close on execute

From: Olivier Dion Guile duplicates the underlying file descriptor stored in a FILE pointer returned by tmpfile(3). This is done to manage the file descriptor with Guile's ports abstraction instead of using the C FILE pointer abstraction. However, the dup(2) system call does not copy the file d

bug#76589: [PATCH] Exclude the finalizer thread from the ‘all-threads’ result.

Version: 3.0.11 Looks like this patch has been applied to the main branch, and I believe Oliver Dion is planning to create a new bug for any remaining concerns. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A

bug#77978: [feature request] Document in-vicinity

Looks like this has been addressed for the pending 3.0.11. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

bug#79100: segfault with thread initialization

a aa writes: > # Intended behaviour > According to the [documentation]( > https://www.gnu.org/software/guile/manual/html_node/Guile-Initialization-Functions.html), > you should be able to call `scm_with_guile` concurrently. It looks like this is an issue in thread.c when multiple threads are rac

bug#79365: wrong irritant for 'wrong number of arguments' exception inside modules

Hey, so first off, I guess just for what my expected behavior is here, here's an example of calling a function with the wrong number of arguments under an exception handler. And you can see that the irritant that it gives back points to the function where you called the wrong number of arguments,

bug#79268: Build error

gging. Some test(s) failed. Please report this to bug-guile@gn

bug#79194: Segfault with 0 byte symbol

Was fixed in 35f13806af653ef9ed656708dddcd1d2c8f8da9e. Closing. -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors.

bug#79194: Fwd: bug#79194: Segfault with 0 byte symbol

-- Forwarded message - From: a aa Date: Mon, Aug 11, 2025 at 11:40 PM Subject: Re: bug#79194: Segfault with 0 byte symbol To: Tomas Volf <~@wolfsden.cz> Hello, Tomas <~@wolfsden.cz> > You wrote "handle 0 byte *strings*" (emphasis mine). That is not wh

bug#79194: Segfault with 0 byte symbol

Hi, a aa writes: > Hello, > > how to reproduce: > cc main.c `pkg-config --libs --cflags guile-3.0` && ./a.out > > incorrect behaviour: > The second parameter for scm_from_utf8_symboln should be how many bytes are > pointed to by the pointer however the pointer still gets read if the length > is

bug#79194: Segfault with 0 byte symbol

Hello, how to reproduce: cc main.c `pkg-config --libs --cflags guile-3.0` && ./a.out incorrect behaviour: The second parameter for scm_from_utf8_symboln should be how many bytes are pointed to by the pointer however the pointer still gets read if the length is zero. Being able to handle 0 byte st

bug#79100: segfault with thread initialization

# version 3.0.10 # `config.guess` x86_64-pc-linux-gnu # `config.status` `--prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --datarootdir=/usr/share --disable-depend

bug#79006: hash of f32vectors is constant

gt; #f ``` This has been tester on Guile v3.0.10-1.402e0df (guile-next install using Guix) and on Guile v3.0.9 (guile install using Guix) on a Debian Linux. The same behavior can be observed using f64vectors. This is in my opinion quite a serious bug since it degrades performance of hash tables to

bug#79000: hash of f32vectors is constant

gt; #f ``` This has been tester on Guile v3.0.10-1.402e0df (guile-next install using Guix) and on Guile v3.0.9 (guile install using Guix) on a Debian Linux. The same behavior can be observed using f64vectors. This is in my opinion quite a serious bug since it degrades performance of hash tables to linea

bug#44965: guile 3.0.4 segfault

Cannot reproduce on 3.0.10.214-755f.

bug#78895: 转发：Guile-2.2.7 ELF format file does not satisfy the safe compilation options

发自我的手机 原始邮件 发件人： zp1224248...@163.com日期： 2025年6月25日周三 21:28收件人： bug-guile@gnu.org主题： Guile-2.2.7 ELF format file does not satisfy the safe compilation optionsHi，Guile-2.2.7 now uses the standard ELF format for its compiled code，but the compilation to generate ELF format file

bug#78908: Fix typo in the guile-opengl manual.

Hi, there is a typo in the manual. This patch fixes it. Many thanks, Yuval Langer. p.s. Also sent to bug-guile-...@gnu.org by accident. Sorry about that. From ee6008784886b38eb877bc99b609e929b3db5a62 Mon Sep 17 00:00:00 2001 From: Yuval Langer Date: Fri, 27 Jun 2025 00:17:31 +0300 Subject

bug#78895: Guile-2.2.7 ELF format file does not satisfy the safe compilation options

Hi，Guile-2.2.7 now uses the standard ELF format for its compiled code，but the compilation to generate ELF format file does not satisfy the safe compilation options bindNow，nx，relro，fs。How to solve the problem in version 2.2.7？It is possible in guile-2.2 as in guile-2.0 compiles Scheme code to bytec

bug#78831: [PATCH 1/2] language/bf: rewire compiling to scheme

Trying to compile bf to scheme fails with an impressive backtrace: "In ice-9/boot-9.scm: 1752:10 13 (with-exception-handler _ _ #:unwind? _ # _) In unknown file: 12 (apply-smob/0 #) In ice-9/boot-9.scm: 724:2 11 (call-with-prompt _ _ #) In ice-9/eval.scm: 619:8 10 (_ #(#(#))) I

bug#78832: [PATCH 2/2] language/bf: do not drop first op

The output of the infamous bf "Hello World!" program is actually A[bbePehbZ if that program is first compiled to 'scheme and then to 'value. If one stares way too long at that output, the bf program and compile-scheme.scm one realizes that a loop has run nine times instead of ten. This is ap

bug#78789: make-struct/no-tail segfault

Hi, Calling make-struct/no-tail with an incorrect layout type could lead to a segmentation fault. For example the following: ``` (make-struct/no-tail (make-vtable standard-vtable-fields #f) 0) ``` results in: ``` Thread 1 "guile" received signal SIGSEGV, Segmentation fault. scm_is_valid_vtable_la

bug#58524: Use ffi_prep_cif_var in pointer->procedure

Hi Zhu Zihao, > It's possible to support foreign function use varargs by using > ffi_prep_cif_var. I'd like to use it. Did you get it working? Thanks! Kind regards, Felix Lechner

bug#78650: Guile 3.0.10: regexp-compile not exported by (ice-9 regex) module

Hi, Tomas Volf <~@wolfsden.cz> writes: > Shalok Shalom via "Bug reports for GUILE, GNU's Ubiquitous Extension > Language" writes: > >> In the Guile 3.0.10 package provided by this distribution, the >> standard procedure regexp-compile is not export

bug#56665: Segfault in SRFI-37 when raising ERROR in ARGS-FOLD

Hi, I don't have a fix for you, but for what it is worth, it is possible to avoid the segfault by wrapping the `args-fold` form with a `with-exception-handle` with `#:unwind? #t` like so: (with-exception-handler (lambda (exn) (raise-exception exn)) (lambda () (args-fold ...)) #

bug#78650: Guile 3.0.10: regexp-compile not exported by (ice-9 regex) module

Shalok Shalom via "Bug reports for GUILE, GNU's Ubiquitous Extension Language" writes: > In the Guile 3.0.10 package provided by this distribution, the standard > procedure regexp-compile is not exported by the (ice-9 regex) module. > This causes an "Unbound variabl

bug#78650: Guile 3.0.10: regexp-compile not exported by (ice-9 regex) module

In the Guile 3.0.10 package provided by this distribution, the standard procedure regexp-compile is not exported by the (ice-9 regex) module. This causes an "Unbound variable: regexp-compile" error when attempting to use this procedure after loading the module with (use-modules (ice-9 regex)). I

bug#78464: Guile fails to build with GCC 15

larators are used internally for pointers to functions of - any arity. However, these are equivalent to `(void)' in C++, are - obsolescent as of C99, and trigger `strict-prototypes' GCC warnings - (bug #23681). */ -#ifdef BUILDING_LIBGUILE -typedef SCM (* scm_t_subr) (); -#else +

bug#78333: [PATCH] texinfo: Use `arguments' instead of `attributes' for deftp, deftpx.

* module/texinfo.scm (texi-command-specs)[deftp, deftpx]: Use `arguments'. --- module/texinfo.scm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/module/texinfo.scm b/module/texinfo.scm index ff95f182d..9f6eba096 100644 --- a/module/texinfo.scm +++ b/module/texinfo.scm @@ -

bug#77762: [PATCH] web: Add JSON module.

"Thompson, David" writes: > On Sat, Apr 12, 2025 at 12:01 PM Tomas Volf <~@wolfsden.cz> wrote: >> >> > - null is the symbol 'null >> >> Out of curiosity, what are your thoughts about using #nil instead? > > My original patch from 10 years ago did this. Mark Weaver then > explained to me that #nil

bug#78164: Home Page and IRC

Jens Axel Søgaard writes: > Hi All, > > On the home page: https://www.gnu.org/software/guile/ > I clicked at `#guile` and got to: > https://kiwiirc.com/nextclient/irc.libera.chat/?nick=guile-guest#guile > > But when I click the "start" button, I get the error: >> We couldn't connect to that serve

bug#78164: Home Page and IRC

Hi All, On the home page: https://www.gnu.org/software/guile/ I clicked at `#guile` and got to: https://kiwiirc.com/nextclient/irc.libera.chat/?nick=guile-guest#guile But when I click the "start" button, I get the error: > We couldn't connect to that server :frowning: > Unknown error Do Guile st

bug#78151: [patch] GUILE_QUIET env to silence diagnostic compile messages and welcome message

Hi, I’ve been using the GUILE_QUIET change that extends bug 73685¹ for almost a year now and it helps me a lot with exporting from org-mode, so I’d really like to see it merged. > Matt Wette writes: >> users the ability to silence compile and loading messages that occur The GUILE_QU

bug#78004: Unexpected/inconsistent compilation error

Hi there, This is a weird one, but after poking at it, I think it’s a Guile bug. Happy to be wrong about that. I can consistently reproduce it on two separate computers, so this isn’t a hardware failure. To reproduce: 1. Run `git clone https://codeberg.org/ieure/guix.git' 2. Change

bug#77978: [feature request] Document in-vicinity

Hi, `in-vicinity' appears to have value enough to be used in places such as Guix; sadly it is wholly undocumented (it doesn't even have a docstring). This feature request is about adding a docstring to it and documenting it in Guile Reference manual. -- Thanks, Maxim

bug#77977: [feature request] export and document `lchown'

Hi, It was recently discussed in Guix bug#77288 that having the Guile definition of lchown exported and available would be useful. The previously referenced issue duplicate its definition since it's not made available by Guile. -- Thanks, Maxim

bug#77762: [PATCH] web: Add JSON module.

's fine. [...] > The following clause checks for '.'. We need to distinguish between 3 > types of input here: > > - invalid extraneous zeroes like '09' (ECMA-404 says this is not allowed) > - fractional notation like '0.123' > - plain '0&#

bug#77762: [PATCH] web: Add JSON module.

> > + (read-char port) > > + (expt 10 (- (read-integer > > + ((#\+) > > + (read-char port) > > + (expt 10 (read-integer))) > > + (else > > + (expt 10 (read-integer) > > + (else 1))) &g

bug#77762: [PATCH] web: Add JSON module.

Hi David, "Thompson, David" writes: > Attached is a patch that adds a new (web json) module. Some may > remember that I submitted a patch back in 2015 (time flies, eh?) for > an (ice-9 json) module that never made it in. Well, 10 years is a long > time and Guile still doesn't have a built-in JSO

bug#77762: [PATCH] web: Add JSON module.

Hi David, > I mean, Guile doesn't *need* to include anything, but JSON is one of > the most common serialization formats around. Most language > implementations ship with a JSON library. Guile already has a suite > of web modules and so this fits right in with those. Over the years > I've noti

bug#77762: [PATCH] web: Add JSON module.

Hi Arun, On Sat, Apr 12, 2025 at 9:39 PM Arun Isaac wrote: > > Thanks for the patch. I'm just trying to understand: Why do we need a > JSON module in guile itself? Isn't guile-json, the way it is as an > external library, good enough? I mean, Guile doesn't *need* to include anything, but JSON is

bug#77762: [PATCH] web: Add JSON module.

Hi David, Thanks for the patch. I'm just trying to understand: Why do we need a JSON module in guile itself? Isn't guile-json, the way it is as an external library, good enough? > API that can read/write JSON to/from a port using only Scheme data > types that have read syntax (i.e. no hash tabl

bug#77762: [PATCH] web: Add JSON module.

On Sat, Apr 12, 2025 at 12:01 PM Tomas Volf <~@wolfsden.cz> wrote: > > > - null is the symbol 'null > > Out of curiosity, what are your thoughts about using #nil instead? My original patch from 10 years ago did this. Mark Weaver then explained to me that #nil was added specifically for the purpose

bug#77762: [PATCH] web: Add JSON module.

> - null is the symbol 'null Out of curiosity, what are your thoughts about using #nil instead? Tomas -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors.

bug#77762: [PATCH] web: Add JSON module.

Attached is a patch that adds a new (web json) module. Some may remember that I submitted a patch back in 2015 (time flies, eh?) for an (ice-9 json) module that never made it in. Well, 10 years is a long time and Guile still doesn't have a built-in JSON module. Third party libraries like guile-json

bug#73132: [PATCH] fix typo and add link

Hi Danny, do you mean like this? From 0be4ece34752574abdfa75454591291e5f684435 Mon Sep 17 00:00:00 2001 From: Arne Babenhauserheide Date: Sat, 5 Apr 2025 00:17:21 +0200 Subject: [PATCH] doc: Fix typo and link "Using Other Languages" for bug 73132 --- doc/ref/srfi-modules.texi | 3 +

bug#77534: [PATCH 1/1] Add mumi config.

@@ +((debbugs-host . "debbugs.gnu.org") + (patch-email-address . "bug-guile@gnu.org") + (mumi-host . "issues.guix.gnu.org")) -- 2.48.1

bug#77534: [PATCH 0/1] Add mumi CLI client configuration

The mumi instance at issues.guix.gnu.org recently started indexing guile issues. This is already available for use via the web interface at https://issues.guix.gnu.org/guile In addition, we should support use of the mumi CLI client. This patch adds mumi CLI client configuration to the guile reposi

bug#77408: [PATCH] srfi-18: Unlock mutex even when condition variable timeout is hit

Unlock mutex even when condition variable timeout is hit Add tests Relevant srfi-18 documentation: https://srfi.schemers.org/srfi-18/srfi-18.html NOTE: mutex-unlock! is related to the "wait" operation on condition variables available in other thread systems. The main difference is that "wait" au

bug#77392: ‘regexp-exec’ gets match boundaries wrong for multibyte strings

‘regexp-exec’ sometimes gets match boundaries wrong when operating on a Unicode string but in a C locale (this is with af96820e072d18c49ac03e80c6f3466d568dc77d): --8<---cut here---start->8--- scheme@(guile-user)> ,use(ice-9 regex) scheme@(guile-user)> (setlocale

bug#77374: eval causes temporary modules to leak memory

You can call make-module (from boot-9.scm) as much as you want to create empty modules. Memory won't leak. As soon as you call eval with that module, it seems it can't be garbage collected anymore. This bug also appears as part of the (@ (rnrs eval) environment) procedure becau

bug#77329: current-filename does not always work

Guile version: 3.0.10 Machine type: x86_64-pc-linux-gnu Guile binary package version: 3.0.10+really3.0.10-4 Steps to reproduce the bug: 1. Extract the following snippet to file cur-fname1.scm some directory: ---cut here--- (define-module (cur-fname1)) (define-public %current-filename

bug#77264: split-and-decode-uri-path must respect trailing slash

join-uri-path (list "foo" "bar")) returns "foo/bar" whereas (encode-and-join-uri-path (list "foo" "bar" "")) returns "foo/bar/". I'm happy to provide a patch if we agree that this is a bug. Thanks!

bug#76623: [PATCH] filesys.c: Use scm_sendfile to copy files.

Rob Browning skribis: > Ludovic Courtès writes: > >> The patch LGTM but I realize there’s no real ‘copy-file’ test. Not your >> fault but would you mind adding one or two tests? > > I went ahead and added a commit to include some simple tests and pushed > that and this to main. Thank you! Lud

bug#42228: [PATCH 0/3] A few minor typo fixes and documentation improvements

Rob Browning writes: > Arun Isaac writes: > >> A few minor typo fixes and documentation improvements follow. >> >> Arun Isaac (3): >> doc: Fix return value of do loop example. >> texinfo: Fix typo in transform-string docstring. >> doc: Improve documentation of make-shared-array. > > All

bug#42228: [PATCH 0/3] A few minor typo fixes and documentation improvements

That's great, thanks!

bug#75860: Somewhat confusing exception message with append

Tomas Nordin writes: > Do you mean like > > $ guile -c "(append '(a) 'b '())" > [...] > In procedure append: Wrong type argument in position 2 (expecting empty > list): b > > Here the position is reported as 2 (as expected I think). Was that what > you also observed? (Still confusing

bug#76623: [PATCH] filesys.c: Use scm_sendfile to copy files.

Ludovic Courtès writes: > The patch LGTM but I realize there’s no real ‘copy-file’ test. Not your > fault but would you mind adding one or two tests? I went ahead and added a commit to include some simple tests and pushed that and this to main. -- Rob Browning rlb @defaultvalue.org and @debia

bug#75860: Somewhat confusing exception message with append

Hello Rob Rob Browning writes: > Tomas Nordin writes: > >> But, in both cases the faulty argument is reported to be in position 1. >> I would expect maybe position 2 to be complained about from the second >> call. > > ...and it appears to be correct when run via -c or a script. Do you mean lik

bug#76907: Potential buffer overflow in getsockopt

Mike Gran via "Bug reports for GUILE, GNU's Ubiquitous Extension Language" writes: > struct timeval is a potential return value of struct getsockopt, but, > when HAVE_STRUCT_LINGER is not defined, scm_t_getsockopt_result may > be too small to hold a struct timeval. Pus

bug#75860: Somewhat confusing exception message with append

Tomas Nordin writes: > But, in both cases the faulty argument is reported to be in position 1. > I would expect maybe position 2 to be complained about from the second > call. ...and it appears to be correct when run via -c or a script. -- Rob Browning rlb @defaultvalue.org and @debian.org GPG

bug#76907: Potential buffer overflow in getsockopt

Mike Gran writes: > struct timeval is a potential return value of struct getsockopt, but, > when HAVE_STRUCT_LINGER is not defined, scm_t_getsockopt_result may > be too small to hold a struct timeval. > > To fix this, struct timeval can be added to the scm_t_getsockopt_result > union. Also, this

bug#76906: make distcheck fails

Make distcheck on main is not working for me. The issue is when it tries to create a file called .version-t and then move it to .version. It tries to create this file in $top_srcdir, which ought to be read-only. The following patch, in which I build it in $top_builddir, works for me. Regards, Mi

bug#76907: Potential buffer overflow in getsockopt

struct timeval is a potential return value of struct getsockopt, but, when HAVE_STRUCT_LINGER is not defined, scm_t_getsockopt_result may be too small to hold a struct timeval. To fix this, struct timeval can be added to the scm_t_getsockopt_result union. Regards, Mike Gran >From 0ebd33ee05ad02a

bug#36340: [PATCH 0/2] bug#36340 Fixes to --disable-networking

These are fixes for Guile when built with the --disable-networking option. Michael Gran (2): Fixes export of suspendable-ports socket funcs when networking disabled Disable some socket tests when sockets not provided module/ice-9/suspendable-ports.scm | 46

bug#36340: [PATCH 2/2] bug#36340: Disable tests when sockets not provided

* test-suite/tests/00-repl-server.test (call-with-repl-server): throw unsupported when sockets not provided * test-suite/tests/web-server.test (expect, "server is listening"): throw unresolved when socket not provided --- test-suite/tests/00-repl-server.test | 3 ++- test-suite/tests/web-serve

bug#36340: [PATCH 1/2] bug#36340: Fixes suspendable-ports networking disabled

When guile is built with --disable-networking, (ice-9 suspendable-ports) will attempt to re-export non-existent accept and socket functions. * module/ice-9/suspendable-ports.scm (accept, connect): set to #f when (guile) module does not have accept or connect (guile-port-bindings): new variable

bug#53201: string->uri-reference rejects domain names with final ‘.’

Merged — thank you for the report and the fix! - Arne signature.asc Description: PGP signature

bug#75590: ports.test: "SEEK_DATA while in hole" fails on some hosts

Ludovic Courtès writes: > What does ‘path-fs’ do? How can we adapt it for use in the test suite? Oh, right, that's here: https://salsa.debian.org/rlb/deb-guile/-/blob/deb/guile-3.0/d/sid/master/debian/bin/path-fs?ref_type=heads via https://salsa.debian.org/rlb/deb-guile/-/commit/691c5a

bug#75040: [PATCH] Remove lib/malloc/.dirstamp and register to .gitignore.

Applied, thanks!

bug#74696: [PATCH] srfi-1: map!: Re-use cons cells of first argument.

Hello! Juliana Sims skribis: > * module/srfi/srfi-1.scm (map!): Re-use cons cells of first argument. > * test-suite/tests/srfi-1.test: Test map!. This LGTM but it leads to a bunch of unrelated test failures. Could you check on your side? Thanks, Ludo’.

bug#74841: [PATCH v2] srfi-19: Fix ~V converter in date->string.

Tomas Volf <~@wolfsden.cz> skribis: > The ~V is supposed to print ISO week number, not a week number. This > commit fixes that. > > * module/srfi/srfi-19.scm (date-week-number-iso): New procedure taken > from the reference implementation. > (directives)<#\V>: Use it. > * test-suite/tests/srfi-19.

bug#75055: [PATCH 0/3] Minor doc cleanups

Morgan Smith skribis: > I have 3 tiny little cleanups to contribute > > Morgan Smith (3): > Remove all remaining references to GDS > * HACKING: Update mailing list URL > * doc/README: Remove reference to a tutorial that no longer exists Hi! I tweaked the commit logs and applied them, than

bug#75642: A fix for `guile-3.0.pc`

Hi Werner, Werner LEMBERG skribis: >>From d92e90bf2a019fc4cb62b0a7398bddf87740e9f1 Mon Sep 17 00:00:00 2001 > From: Werner Lemberg > Date: Fri, 17 Jan 2025 11:10:26 +0100 > Subject: [PATCH] Add `LIB_GETRANDOM` to `Libs.private` in `.pc` files > > The omission was discovered while cross-compilin

bug#75085: bug report with patch 0004-libguile-scm.h-fix-BUILDING_LIBGUILE-for-Werror-unde.patch

Hannes Müller skribis: > From 696151ca382c7b166d349f704812dd73bc2fa7a7 Mon Sep 17 00:00:00 2001 > From: =?UTF-8?q?Hannes=20M=C3=BCller?= <> > Date: Sat, 21 Dec 2024 19:20:17 +0100 > Subject: [PATCH] libguile/scm.h: fix BUILDING_LIBGUILE for -Werror=undef > > *libguile/scm.h: BUILDING_LIBGUILE is

bug#75084: bug report with patch 0003-Fix-make-custom-port-in-case-encoding-is-f.patch

Hi, Hannes Müller skribis: > From 72b85f8e6a369e6aef4c6bd6bb233c0cacb80b03 Mon Sep 17 00:00:00 2001 > From: =?UTF-8?q?Hannes=20M=C3=BCller?= <> > Date: Sat, 21 Dec 2024 16:55:13 +0100 > Subject: [PATCH] Fix make-custom-port in case encoding is #f > > * module/ice-9/custom-ports.scm (make-custom-

bug#75216: Miscompilation of code with numeric predicates

was debugging today. A call of (foo 8.2) should return 69 and > indeed it does so on Guile 3.0.9. Not so on Guile 3.0.10 where it > returns 138. Bug confirmed on c8a169d38825d5a21da5392b355ca5fc9f33fa55 (post 3.0.10). Ludo’.

bug#75590: ports.test: "SEEK_DATA while in hole" fails on some hosts

Hi Rob, Rob Browning skribis: > +(define (skip-unless-fs-handles-holes-as-expected) > + ;; For now only allow filesystems that should have the seek hole/data > + ;; semantics the tests expect. Filesystems vary both in how they > + ;; handle sparseness in general (e.g. granularity), how they

bug#76621: [PATCH] sxml: Fix typo in a comment.

Tomas Volf <~@wolfsden.cz> skribis: > * module/sxml/xpath.scm: Fix typo in a comment. > * module/sxml/upstream/SXPath-old.scm: Same. > * doc/ref/sxml.texi (SXPath): Reflect in the documentation. Applied, thanks.

bug#76623: [PATCH] filesys.c: Use scm_sendfile to copy files.

Hi, Tomas Volf <~@wolfsden.cz> skribis: > Use scm_sendfile instead of read-write loop. This moves the work into > the kernel, improving performance. This implements Ludovic's suggestion > from bug 68504. > > * libguile/filesys.c (scm_copy_file2): Use scm_sendfile.

bug#75997: (ice-9 match): warning: unused variable `failure'

Ludovic Courtès writes: > Tomas Volf <~@wolfsden.cz> skribis: > >> (lambda (expr) >> (let* ((v expr) >> (failure >>(lambda () >> ((@@ (ice-9 match) throw) >> 'match-error >> "match" >> "no matching pattern" >>

bug#76624: [PATCH] filesys.c: Trim trailing white-space.

* libguile/filesys.c: Trim trailing white-space. --- libguile/filesys.c | 122 ++--- 1 file changed, 61 insertions(+), 61 deletions(-) diff --git a/libguile/filesys.c b/libguile/filesys.c index 0e7078cf0..3bfa5eb91 100644 --- a/libguile/filesys.c +++ b/libg

bug#76623: [PATCH] filesys.c: Use scm_sendfile to copy files.

Use scm_sendfile instead of read-write loop. This moves the work into the kernel, improving performance. This implements Ludovic's suggestion from bug 68504. * libguile/filesys.c (scm_copy_file2): Use scm_sendfile. --- libguile/filesys.c | 21 + 1 file change

bug#76621: [PATCH] sxml: Fix typo in a comment.

* module/sxml/xpath.scm: Fix typo in a comment. * module/sxml/upstream/SXPath-old.scm: Same. * doc/ref/sxml.texi (SXPath): Reflect in the documentation. --- doc/ref/sxml.texi | 2 +- module/sxml/upstream/SXPath-old.scm | 2 +- module/sxml/xpath.scm | 2 +- 3 files c

bug#76589: [PATCH] Exclude the finalizer thread from the ‘all-threads’ result.

ing a single boolean and storing true in it whenever a user thread is created is enough. Thanks, Olivier On Wed, 26 Feb 2025, Ludovic Courtès wrote: > Fixes <https://bugs.gnu.org/76343>. > > Fixes a bug whereby “echo '(environ)' | guile” would wrongfully trigger

bug#69998: [PATCH guile-web] libraries: Use guile-gnunet’s real name.

Hi, Florian Pelz skribis: > * website/apps/base/libraries-page.scm (guix->package)[real-name]: > Add special case. Finally applied. It won’t show up until someone redeploys the web site though… Ludo’.

bug#70645: Reliable HTTPS networking

Christopher Baines skribis: > As described in the GnuTLS documentation on Asynchronous operation, > GNUTLS_NONBLOCK should be passed to gnutls_init, and the Guile > equivalent is passing connection-flag/nonblock to make-session. > > Additionally, error/again or error/interrupted should lead to a

bug#75997: (ice-9 match): warning: unused variable `failure'

Tomas Volf <~@wolfsden.cz> skribis: > (lambda (expr) > (let* ((v expr) > (failure >(lambda () > ((@@ (ice-9 match) throw) > 'match-error > "match" > "no matching pattern" > v) > #f))) > #f)

bug#76589: [PATCH] Exclude the finalizer thread from the ‘all-threads’ result.

Fixes <https://bugs.gnu.org/76343>. Fixes a bug whereby “echo '(environ)' | guile” would wrongfully trigger the multiple-thread warning. * libguile/finalizers.c (finalizer_thread): New variable. (finalization_thread_proc): Set it. (scm_i_is_finalizer_threa

  1   2   3   4   5   6   7   8   9   10   >