bug#79006: hash of f32vectors is constant

Hello, Hashing two different f32vectors returns the same value: ``` (equal? (hash (f32vector 1) most-positive-fixnum) (hash (f32vector 2) most-positive-fixnum)) ; => #t ``` This is wrong since these vectors are not equal?: ``` (equal? (f32vector 1) (f32vector 2)) ; => #f ``` T

bug#79000: hash of f32vectors is constant

Hello, Hashing two different f32vectors returns the same value: ``` (equal? (hash (f32vector 1) most-positive-fixnum) (hash (f32vector 2) most-positive-fixnum)) ; => #t ``` This is wrong since these vectors are not equal?: ``` (equal? (f32vector 1) (f32vector 2)) ; => #f ``` Th

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#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

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#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#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 because it uses both

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#74696: [PATCH] srfi-1: map!: Re-use cons cells of first argument.

* module/srfi/srfi-1.scm (map!): Re-use cons cells of first argument. * test-suite/tests/srfi-1.test: Test map!. --- Hi Ludo, Thanks for your patience in getting this together. I've added some tests for map!. Let me know if you think there are more cases that should be tested. As a sidenote, i

bug#75958: Guile gnulib module missing ffs

Hi, I've been trying to build Guile with a mingw-w64-ucrt toolchain and I've come across an error, undefined reference to ffs. I believe the current distribution of Guile 3.0.10 is missing this in its gnulib modules. Dane Johnson

bug#69314: [PATCH] Speed up stage0 bootstrap build using prebuilts

On Sun, 2024-07-14 at 19:55 +0200, Jonas Hahnfeld wrote: > On Mon, 2024-05-06 at 21:12 +0200, Jonas Hahnfeld wrote: > > On Mon, 2024-05-06 at 11:34 +0200, Ludovic Courtès wrote: > > > Hi Jonas, > > > > > > Jonas Hahnfeld skribis: > > > > > > > On Thu, 2024-01-04 at 11:57 +0100, Jonas Hahnfeld wr

bug#75583: Can't retrieve key from keys.openpgp.org for release verification

Hello guile maintainers, I just tried to install Guile via the asdf-guile plugin. Sadly the automated verification fails with the following error: |gpg: Signature made Sun 23 Jun 2024 11:52:58 PM CEST gpg: using RSA key 4FD4D288D445934E0A14F9A5A8803732E4436885 gpg: requesting key A8803732E4436

bug#75078: Guile 3.0.10 fails to build for i686 cygwin

On Mon, 6 Jan 2025, Rob Browning wrote: > Jeremy Drake writes: > > > ice-9/boot-9.scm:1676:22: In procedure raise-exception: > > Value out of range 0 to< 18446744073709551615: -505802029 > > make[2]: *** [Makefile:2515: language/cps/guile-vm/reify-primitives.go] > > Error 1 > > Is this with the r

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

Dear All,   Please review the attached patch.   Thanks,Hannes 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/sc

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

Dear All, Please review the attached patch.   Thanks, HannesFrom 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-port

bug#75078: Guile 3.0.10 fails to build for i686 cygwin

3.0.8 and 3.0.9 build, but 3.0.10 fails in BOOTSTRAP(stage1) with: Backtrace: In ice-9/boot-9.scm: 1755:12 19 (with-exception-handler _ _ #:unwind? _ #:unwind-for-type _) In system/base/compile.scm: 69:11 18 (_) 190:11 17 (_ #) 309:6 16 (read-and-compile # #:from _ #:to _ #:env _ #:op

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

* module/srfi/srfi-1.scm (map!): Re-use cons cells of first argument. --- Hello, This patch rewrites map! to update its first argument in-place. I based the implementation on the description in the Guile manual. Most of the code is copied from regular map with different argument checking logic.

bug#74210: No unbound variable warning when via 'export'

Forwarded e-mail/bug report from guile-devel From: Tommi Höynälänmaa Date: dinsdag 5 november 2024 8:25 To: guile-de...@gnu.org Subject: Re: Exporting a nonexistent variable Here is another example: --- mod1.scm --- (define-module (mod1)) (export myproc) (define (myproc0)   (display "Hello\n"

bug#71684: [PATCH v4] doc: Document the peek and pk procedures.

* doc/ref/api-debug.texi: Document the peek and pk procedures. --- doc/ref/api-debug.texi | 120 + 1 file changed, 109 insertions(+), 11 deletions(-) Hi Janneke, Thanks for the catch! That's fixed in this version :) Best, Juli diff --git a/doc/ref/api-d

bug#73707: Missing functions for R7RS small

Hi, You don't implement the functions string->vector and vector->string which are in R7RS small per the index at scheme.org: https://index.scheme.org/filterset/r7rs_small/search?query=string-%3Evector Simon

bug#73561: Acknowledgement (Couple of typos in the documentation)

Found two more typos today: >From 0c090dcfe3b156436f35b52e4492575b71cf621f Mon Sep 17 00:00:00 2001 From: Matthias Kaak Date: Mon, 30 Sep 2024 13:10:43 + Subject: [PATCH] Fixed a couple typos in the documentation * doc/ref/apu-scheduling.texi: Fixed one typo of "if" from "ff" * doc/ref/apu-u

bug#73561: Couple of typos in the documentation

Package: guile Version: 3.0.10 Severity: minor Tags: patch There are a couple typos of missing brackets/parentheses in the documentation (for example in the PDF on page 127 under integer-expt or in the first code block of page 601). As I don't know texinfo (only (La)TeX), I don't know if this p

bug#71300: [PATCH v4] doc: Document SRFI 64.

>> Based on this I believe it describes the specification. > >That's correct. It's been slightly modified in places where it said >things like "left to the implementation" and I was able to verify what >the current implementation in Guix does. I assume Guix->Guile. This modification of “left to

bug#71684: [PATCH v3] doc: Document the peek and pk procedures.

* doc/ref/api-debug.texi: Document the peek and pk procedures. --- Hey y'all, Thanks for the feedback! I've incorporated both suggestions in this new patch. Best, Juli doc/ref/api-debug.texi | 120 + 1 file changed, 109 insertions(+), 11 deletions(-) d

bug#73167: [PATCH] Fix setjmp/longjmp-related crashes on Windows

Hi all, recently an user reported a bug to the LilyPond project, where he tried to print a data structure with (pretty-print), which silently failed at a certain point inside the data structure: https://gitlab.com/lilypond/lilypond/-/issues/6737#note_2049515997 The error did only affect LilyPond

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

I think I ran into this issue in a different place. Guile does not support the ((library (foo bar) ...) form in cond-expand, so one way around it is to have (cond-expand (srfi-N ... ) ((library (srfi N)) ...) but in a situation where srfi-N is false Guile tries to evaluate the (library ... fo

bug#18932: string->number errors on e.g. "1e400xyz"

still happens on the latest guile. trying to (write) a symbol that starts with large scientific notation also causes this problem. (write (string->symbol "1e400xyz"))

bug#72347: Mismatch between documentation and real implementation of list-index

Thank you for the quick response, El 29 de julio de 2024 10:28:00 UTC, Tomas Volf <~@wolfsden.cz> escribió: >Hello, > >On 2024-07-29 00:34:14 +0000, Marius via Bug reports for GUILE, GNU's >Ubiquitous Extension Language wrote: >> Good evening, >> >> I d

bug#72347: Mismatch between documentation and real implementation of list-index

Good evening, I don't know if this is actually a Guile bug or a documentation bug, but I'm currently learning Guile from the "Guile reference manual" and I've found a mismatch between what the documentation says and what "my" guile does. I use Guile 3.0.9. In my Guile instance (from what I can

bug#71684: [PATCH] doc: Document the peek and pk procedures.

hi, this looks good to me. let's merge it y'all! -- all best, jgart

bug#72209: Texinfo: stexi->texi: Anchor label becomes empty

STEPS TO REPRODUCE 1. Start a Guile REPL 2. Run the following code:    #+begin_src scheme    (use-modules (texinfo serialize))    (stexi->texi '(anchor "some-label"))    #+end_src EXPECTED RESULT A string like this: "@anchor{some-label}" UNEXPECTED RESULT The label part is empty: "@anchor{

bug#71684: [PATCH v2] doc: Document the peek and pk procedures.

Hi y'all, Thanks for the (continued) reviews! I hadn't commented on that last sentence before, but if I knew how to have the Guile debugger reliably break where I want it to (I don't, or somehow haven't managed to have it work well), I don't think using 'pk', which requires editing files befor

bug#69314: [PATCH] Speed up stage0 bootstrap build using prebuilts

On Mon, 2024-05-06 at 21:12 +0200, Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library wrote: > On Mon, 2024-05-06 at 11:34 +0200, Ludovic Courtès wrote: > > Hi Jonas, > > > > Jonas Hahnfeld skribis: > > > > > On Thu, 2024-01-04 at 11:57 +0100, Jonas Hahnfeld wrote: > > >

bug#72092: [PATCH] fix file descriptor leak in piped_process/system*/popen/etc

fix is attached test code: (use-modules (ice-9 ftw)) (use-modules (ice-9 popen)) (define (print-open) (format #t "~a\n" (length (scandir "/proc/self/fd" (let ((p (%make-void-port "rw"))) (print-open) (parameterize ((current-output-port p) (current-input-port p) (current-error-port p

bug#72095: Non-local exit with thunk from system-async-mark doesn't restore asyncs block level

TLDR: abort-to-prompt restores asyncs block level. abort-to-prompt from a procedure scheduled with system-async-mark doesn't restore asyncs block level. Some more context: I was trying to implement interruptible and reusable threads on top of delimited continuations and asynchronous interrupts.

bug#72065: (rnrs io ports) lacks documentation

Hello, It seems that not all publicly-exported procedures in (rnrs io ports) are documented. I noticed this with the `open--[input|output]-port' procedures (eg `open-string-output-port') in particular, though I suspect others may also lack documentation. Best, Juli

bug#71684: [PATCH v2] doc: Document the peek and pk procedures.

* doc/ref/api-debug.texi: Document the peek and pk procedures. --- Hi Maxim, Thanks for the quick review! I thought I'd made sure to double-space after periods, but I guess my Emacs fill settings overwrote that when I made sure everything flowed properly. The contemporary consensus on double spac

bug#71684: [PATCH] doc: Document the peek and pk procedures.

* doc/ref/api-debug.texi: Document the peek and pk procedures. --- doc/ref/api-debug.texi | 187 +++-- 1 file changed, 179 insertions(+), 8 deletions(-) diff --git a/doc/ref/api-debug.texi b/doc/ref/api-debug.texi index faa0c40bd..486473cdb 100644 --- a/doc/ref

bug#46009: exception from inside false-if-exception?

> Also, I don’t see a fundamental change in meaning >>just look at my test.scm: >>without the explicit (let/ec return ...) wrapper, and the explicit use of >>(return ...) in the handlers, the two invocations lead to different flow of >>control. >>It's icing on the cake that if the underlying ERR

bug#46009: exception from inside false-if-exception?

I don’t think we are going to agree on much here, but some new points of agreement pop up occassionally. Continuing this … >> What is lousy and expectation-violating about a keyword argument >> doing what it name describes? >well, this should have been discussed at the R6RS committee, but... Thi

bug#46009: exception from inside false-if-exception?

>it's a tangential, but namely, when #:unwind #t then the handler in a w-e-h >returns from the w-e-h block, but with #:unwind #f it tries to return to the >RAISE that raised the condition. i.e. a lousy little keyword arg (usually a >page down) fundamentally changes the behavior of w-e-h. yet ano

bug#71383: Guile 3.0.9 / error missing auxiliary stack implementation for architecture

Dear Guile devs, I've got a build time error, related to my specific architecture "e2k-mcst-linux-gnu" (i believe): --- snip --- Making all in libguile make[2]: Entering directory '/srv/home/static/src/guile-3.0.9/libguile' SNARF continuations.x lcc: "continuations.c", line 147: catastrophic

bug#71334: GNU Guile 3.0.7 bug report

Reproduce as follows: Using Ubuntu 22.04. 1. sudo apt install guile-3.0-dev guile-3.0-dev is already the newest version (3.0.7-1). 2. Create a file run.scm with content as following: (define (k n t) (logand (ash n t) 4294967295))(define run (lambda (q) (k (+ (ash (k q -96) 30) (ash (k q -96) -2))

bug#69314: [PATCH] Speed up stage0 bootstrap build using prebuilts

On Mon, 2024-05-06 at 11:34 +0200, Ludovic Courtès wrote: > Hi Jonas, > > Jonas Hahnfeld skribis: > > > On Thu, 2024-01-04 at 11:57 +0100, Jonas Hahnfeld wrote: > > > From 95f15821c535537c7ad4fdae1988855314d56ece Mon Sep 17 00:00:00 2001 > > > From: Jonas Hahnfeld > > > Date: Thu, 4 Jan 2024 11

bug#70144: system* affects signal handlers

Hi Ludo, Ludovic Courtès writes: > Unless I’m mistaken, we can remove the ‘scm_dynwind_sigaction’ calls > from ‘scm_system_star’: now that we use ‘posix_spawn’, this is all taken > care of. > > This can be seen by running: > > strace -o /tmp/log.strace -f guile -c '(system* "/bin/sh" "-c" "ech

bug#70778: `include' is unable to include local file

Guile include logic fails when '-L incdir' option is provided.   The `syntax-source' function in such case strips out file's directory; as a result the `call-with-include-port' function is trying to open file from current directory. Note that `incdir' here is equal to file folder:   amaya@t460s:~/

bug#70534: eval-string: wrong environment for compilation

Hi! I'm pretty sure there is a bug in (ice-9 eval-string) implementation. If #:compile? is true it doesn't pass current module to the read-and-compile procedure which in my opinion leads to undesired behavior: This code snippet doesn't work --8<---cut here---start-

bug#70142: [PATCH] Fix error messages containing format strings

Hi all, I recently ran into the issue that some error messages in Guile are not formatted properly. As a simple reproducer, fire up a REPL and do ,option on-error 'foo Which will yield "While executing meta-command: Bad on-error value ~a; expected one of ~a foo (debug backtrace report pass)" T

bug#70033: Possible Bug: Inconsistent Evaluation Environment

Hello there, I have bumped into an interesting issue with GNU Guile 3.0.9 (as shipped via GNU GUIX). Consider a file -- file1.scm -- with the following definition over-riding the built-in procedure vector-length: (define (vector-length whatever) "over-ridden") Now, consider another file -- fi

bug#69315: [PATCH] Build system fixes

On Thu, 2024-02-22 at 22:14 +0100, Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library wrote: > Dear Guile maintainers, > > please find attached two patches for changes that we have been carrying > downstream in LilyPond so far: one fix to make a sed invocation fully > port

bug#69921: [PATCH] eval-string: Fix setting port column

On Thu, 2024-03-14 at 17:11 +0600, Nikita Domnitskii wrote: > --- > module/ice-9/eval-string.scm | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/module/ice-9/eval-string.scm b/module/ice-9/eval-string.scm > index ea0f1..9cac03632 100644 > --- a/module/ice-9/eval-strin

bug#69438: basename faulty with nul and suffix

Trying out the basename function in Guile 3.0.9: scheme@(guile-user)> (basename "foo/bar") $1 = "bar" scheme@(guile-user)> (basename "foo/bar" "r") $2 = "ba" scheme@(guile-user)> (basename "foo/bar" "x") $3 = "bar" scheme@(guile-user)> (basename "foo/bar\0baz/quux") $4 = "bar" scheme@(guile-user)>

bug#69436: confused by changing absolute pathname

The guile(1) command-line interface is documented to take the filename of a script to execute. Here's how well it resolves filenames (testing on Guile 3.0.5): $ mkdir a $ cd a $ echo '(display "ok") (newline)' > ok.scm $ perl -e 'chdir ".."; while(1) { rename("a", "b"); rename("b", "a"); }' & [1]

bug#69437: basename fails with suffix containing slash

$ guile-3.0.9 -c '(write (basename "foo/bar" "o/bar")) (newline)' Backtrace: [...] ERROR: In procedure basename: Value out of range: 18446744073709551614 Looks like this decides based on the whole pathname that the five-character suffix matches, and then tries to remove that suffix from the three-

bug#69315: [PATCH] Build system fixes

Dear Guile maintainers, please find attached two patches for changes that we have been carrying downstream in LilyPond so far: one fix to make a sed invocation fully portable, and a fix for cross-compilation in out-of-tree-builds. Regards Jonas From 428d1b17c5f664d3cb8da4cd5687bd47bdd87877 Mon Se

bug#69314: [PATCH] Speed up stage0 bootstrap build using prebuilts

Dear Guile maintainers, please consider below patch to speed up the build from release tarballs that include prebuilt bytecode. Jonas On Thu, 2024-01-04 at 11:57 +0100, Jonas Hahnfeld wrote: > From 95f15821c535537c7ad4fdae1988855314d56ece Mon Sep 17 00:00:00 2001 > From: Jonas Hahnfeld > Date:

bug#69288: [PATCH] Fix typo in documentation for output buffering.

* doc/ref/api-control.texi (Buffering): Fix typo. --- doc/ref/api-io.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/ref/api-io.texi b/doc/ref/api-io.texi index e263e2985..38b553b80 100644 --- a/doc/ref/api-io.texi +++ b/doc/ref/api-io.texi @@ -754,7 +754,7 @@ line-buf

bug#69247: [PATCH] Support XDG Base Directory specification for init file

Implements a small code change to load a `guilerc` file as an alternative to the `~/.guile` init file, from directories following the XDG Base Directory Specification, `$XDG_CONFIG_HOME` or `$HOME/.config`. Prioritises existing behaviour to avoid causing anyone trouble. * module/ice-9/boot-9.scm (

bug#49693: Patch can be accepted

Hi, In early 2024, the address was still incorrect (as of commit fb1f5e28). I believe the patch can be accepted. Thanks! Kind regards Felix

bug#62590: Strange put-char encoding-error "conversion to port encoding failed"

Hi, > (encoding-error put-char conversion to port encoding failed 84 > # s) Could the error be due to the 7-bit encoding in HTTP headers? [1] The "84" is EILSEQ from errno.h. [2] Wingo added the functionality here. [3] I also submitted a patch to resolve in the errno. [4] A similar issue appear

bug#68624: [PATCH] Decode errno for encoding errors.

* libguile/strings.c (scm_encoding_error): Decode errno. --- Hi, Even experienced users do not memorize errno values. [1][2] Why not decode them as a courtesy? Kind regards Felix Lechner [1] https://debbugs.gnu.org/62590 [2] https://debbugs.gnu.org/59510 libguile/strings.c | 2 +- 1 file chang

bug#67797: non-free license listed in module/ice-9/psyntax.scm

> Hi Mike, > Do I understand correctly that any copyright license comes with an > implicit "lawful" condition so as to be considered valid, per the law of > USA at least?  And that making this explicit is thus not considered a > restriction on the use? That is how I understand it. I am not a lawy

bug#67797: non-free license listed in module/ice-9/psyntax.scm

On Tuesday, December 12, 2023 at 12:51:11 PM PST, Maxim Cournoyer wrote: >> This confirms my hunch that there is no issue with the license. >That's great, but... why is it not a problem?  :-) >When we find out, we should add an explanation next to the license text, >why it's deemed alright. M

bug#66531: [PATCH] ftw: Fix getuid-or-false, getgid-or-false macros.

I haven't forgotten about this. My linux devel box died. Maybe someone else can make the push, otherwise, I'll be back in business in a couple weeks. On Friday, October 13, 2023 at 11:20:11 AM PDT, Tomas Volf wrote: On 2023-10-13 17:30:06 +, Mike Gran wrote: > > Both macros were

bug#66531: [PATCH] ftw: Fix getuid-or-false, getgid-or-false macros.

> Both macros were missing a quote for the procedure call, causing the > actual return value to be compiled into the ftw.go, instead of the >procedure call.  Snippet from disassembly of ftw.go does confirm that: Looks good to me. If you don't have commit approval, I can take the action to commit

bug#43364: with-output-to-port works with file ports

Hi, In an interesting (or perhaps maddening) inconsistency, 'with-output-to-port' captures stdout from system* here (call-with-output-file "/tmp/test.log" (lambda (port) (with-output-to-port port (lambda () (system* "mktemp" "-d") but 'with-output-to-string' does no

bug#64723: [PATCH] Improve DLL search strategy for load-foreign-library

> The new non-libltdl foreign library loading algorithm from 3.0.6 > fails to cover common cases regarding how libtool names and installs > DLL files.  Notably, it fails to recognize when libtool has added the > major version number into the filename itself, such as libfoo-1.dll > Also, it does not

bug#65399: [PATCH] web: Fix non-IPv4 default socket.

PF_INET sockets were being created by default with #:family AF_INET6 or AF_UNIX, resulting in In procedure bind: Address family not supported by protocol * module/web/server/http.scm (make-default-socket): Use #:family. * doc/ref/web.texi (Web Server): Fix quoting in documentation, bind to su

bug#64723: [PATCH] Improve DLL search strategy for load-foreign-library

The new non-libltdl foreign library loading algorithm from 3.0.6 fails to cover common cases regarding how libtool names and installs DLL files. Notably, it fails to recognize when libtool has added the major version number into the filename itself, such as libfoo-1.dll Also, it does not search

bug#64723: load-foreign-library has incomplete support for libtool-generated DLLs

The new non-libltdl foreign library loading algorithm from 3.0.6 fails to cover common cases regarding how libtool names and installs DLL files. Notably, it fails to recognize when libtool has added the major version number into the filename itself, such as libfoo-1.dll Also, it does not search in

bug#64293: Dead link to Joe Marshall's syntax-rules Primer for the Merely Eccentric

Hi, The link [1] to Joe Marshall's "syntax-rules Primer for the Merely Eccentric" in the reference manual [2] yields a 404 Page Not Found Error. Please carbon-copy me on any replies, as I am not subscribed to your list. Thanks! Kind regards Felix [1] http://sites.google.com/site/evalapply/eccen

bug#64039: C-procedure runs when called from C-code, but hags when called from Guile

Actually, no, you're right. I've just never seen a do/while w/o braces. On Tuesday, June 13, 2023 at 06:37:01 AM PDT, Mike Gran via "Bug reports for GUILE, GNU's Ubiquitous Extension Language wrote: Hello- I don't see the problem with the shutter. But the

bug#64039: C-procedure runs when called from C-code, but hags when called from Guile

Hello- I don't see the problem with the shutter. But the GetStatus lines should be more like what is below. Your current code only checks status once. do {   GetStatus(&status); } while (status== DRV_ACQUIRING); On Tuesday, June 13, 2023 at 04:29:46 AM PDT, Михаил Бахтерев wrote: Gr

bug#63826: Posix Spawn on MinGW

The recent addition of the posix_spawn gnulib module raises the possibility of getting this functionality to work on MinGW, since the gnulib module provides portability to MinGW and friends. The first step is to remove the HAVE_FORK ifdefs where unnecessary in posix.c, since piped_process() does n

bug#63304: srfi-69 weak table bug

Tested on: Fedora, Guix Fedora's guile package: guile30-3.0.7-8.fc38.x86_64 Fedora guile --version: 3.0.7 Guix guile package: 1.4.0-5.286cdf0 Guix guile --version: 3.0.9 How to reproduce: ```scheme (use-modules (srfi srfi-69)) (define tmp (make-hash-table #:weak 'key)) (hash-table-set! tmp 'test

bug#63269: Guile compiler supresses initalization of autoloaded modules

Guile compiler drives out part of initialization for autoloaded modules (typically,  statements in `side-effects only' form). Please find below an example. Interpreter produces expected result;  compiler works fine when `define-public’ form is used in autoloaded module for `f’ definition.    amaya

bug#62872: doc: Texinfo Processing: Indicate which version(s) of Texinfo are supported

Hi, Guile's documentation on Texinfo Processing doesn't seem to mention that the Texinfo format is *partially supported* or whether a particular version or versions of the format are supported. Processing documents written in Texinfo 6.x and 7.x, I found that some commands lead to parsing er

bug#62870: Texinfo: stexi->texi: Itemize End command not in a line of its own

Hi, The command ending an itemization (end command) is not placed in a line of its own, but it should: "Block commands: These commands are written at the start of a line, with general text on following lines, terminated by a matching '@end' command on a line of its own." — Texinfo manual, @-

bug#62869: Texinfo: texi-fragment->stexi: Parsing verbatim fails when no newline

Hi, When a "verbatim" fragment doesn't end in a newline character, parsing fails. This failure seems like a defect to me because it only happens with the "verbatim" command, and not with similar block commands like "example", "lisp", "display" and "format". Operating system: Guix System x86_

bug#62729: [PATCH] Fix dangling pointers in `environ'

From: Olivier Dion When calling `environ', Guile set the global variable `environ' to a list allocated with the GC. Strings in it are also allocated with the GC. However, if an user call the Scheme setenv() procedure, the resulting call to putenv() in libc might reallocate `environ' to a new po

bug#61095: possible misuse of posix_spawn API on non-linux OSes

Hi Ludo, Ludovic Courtès writes: > Coming next is an updated patch series addressing this as proposed > above. Let me know what y’all think! > > I tested the ‘posix_spawn_file_actions_addclosefrom_np’ path by building in: > > guix time-machine --branch=core-updates -- shell -CP -D -f guix.scm

bug#62510: [PATCH] docs: Add example clarifying how syntax-case renames symbols

I encountered these renamed symbols in the wild, and it took quite a while for me to figure out what was going on. I'm glad to have learned a lot about syntax-case in the process, all the way through to Primer for the Mildly Insane, but I think it would spare future learners some trouble to have an

bug#61095: possible misuse of posix_spawn API on non-linux OSes

Hi Ludo, Ludovic Courtès writes: > - posix_spawn_file_actions_addclose (actions, fd); > + /* Adding invalid file descriptors to an 'addclose' action leads > + to 'posix_spawn' failures on some operating systems: > + . Hence the extra check.

bug#62456: [PATCH] Fix typo.

--- libguile/list.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libguile/list.c b/libguile/list.c index 82aab8a5d..cd05e77b8 100644 --- a/libguile/list.c +++ b/libguile/list.c @@ -224,7 +224,7 @@ SCM_DEFINE (scm_length, "length", 1, 0, 0, SCM_DEFINE (scm_append, "append"

bug#62053: Guile compiler is unable to compile tiny program

Guile compiler is unable to compile tiny program:   (define (fn l)     (define (ok l)    (or (and (pair? l) l)    (error "list is empty")))     (cons (reverse (car l)) (ok l)))   amaya@picasso:~/tmp/guile-3.0.9 $ ../prefix/bin/guile ~/tmp/guile-compiler-bug.scm ;;; note: auto-compilati

bug#61058: [PATCH] Fix asymetric mutex locking when joining thread.

From: Olivier Dion If `join-thread' timeout, the thread mutex is not unlocked, resulting in deadlock to the next call to it or deadlock of the thread itself when it terminates. Thus, always unlock the mutex. Fix: #55356 * module/ice-9/threads.scm (join-thread): Always unlock thread mutex. ---

bug#60928: [PATCH] bugfix/make_hash_table: fix segfault when arg< 0 for make-hash-table

lloda writes: > It seems this is the same bug as https://bugs.gnu.org/60488 and > https://bugs.gnu.org/58154, at least it doesn't segfault in main > anymore. oh sorry about the false patch then, I had searched my local repo for commits containing the word segfault and didn't find any mention,

bug#60928: [PATCH] bugfix/make_hash_table: fix segfault when arg< 0 for make-hash-table

* libguile/hashtab.c (make_hash_table): FIX SEGMENTATION FAULT Currently on Guix if a user evokes (make-hash-table arg) where arg < 0, guile segfaults. This patch adds the most straight forward solution, checking if the value passed to make-hash-table is less than 0, and if so, throwing an error w

bug#52835: [PATCH 0/2] Fix spawning a child not setting standard fds properly

Hello Josselin & Ludo, Thanks for your work on this, posix_spawn is a nice improvement! My comments on the changes in the wip-posix-spawn branch follow. In doc/ref/posix.texi: @quotation Note If you are only looking to fork+exec with some pipes set up, using pipes or the more @code{spawn} p

bug#52835: [PATCH v8 1/2] Add spawn.

* libguile/posix.c: Include spawn.h from Gnulib. (do_spawn, scm_spawn_process): New functions. --- doc/ref/posix.texi | 34 -- libguile/posix.c | 162 - libguile/posix.h | 1 + 3 files changed, 192 insertions(+), 5 deletions(-) diff --git

bug#52835: [PATCH 0/2] Fix spawning a child not setting standard fds properly

Hi Ludo, Happy new year! Ludovic Courtès writes: > ‘spawn*’ is expressive enough, but a procedure with 6 positional > arguments cannot be exposed as-is IMO. > > One tiny thing that’s missing is a boolean to choose between > ‘posix_spawn’ and ‘posix_spawnp’. > > So we need either ‘spawn’ defined

bug#52835: [PATCH v8 2/2] Make system* and piped-process internally use spawn.

* libguile/posix.c (scm_system_star, scm_piped_process): Use do_spawn. (start_child): Remove function. Co-authored-by: Ludovic Courtès --- libguile/posix.c | 231 --- 1 file changed, 77 insertions(+), 154 deletions(-) diff --git a/libguile/posix.c b/l

bug#52835: [PATCH v7 1/2] Add spawn* and spawn.

* libguile/posix.c: Include spawn.h from Gnulib. (do_spawn, scm_spawn_process): New functions. * module/ice-9/spawn.scm: New file (spawn): New procedure. --- libguile/posix.c | 82 ++ libguile/posix.h | 2 ++ module/ice-9/spawn.scm | 54

bug#52835: [PATCH v7 2/2] Make system* and piped-process internally use spawn.

* libguile/posix.c (scm_system_star, scm_piped_process): Use do_spawn. (start_child): Remove function. Co-authored-by: Ludovic Courtès --- libguile/posix.c | 233 --- 1 file changed, 78 insertions(+), 155 deletions(-) diff --git a/libguile/posix.c b/l

  1   2   >