bug#40809: Apology: documentation for srfi-modules broken?

Hello Guilers! I submitted my patch for srfi-171 which got merged. I built it (or rather: I believe I did) on my little arm board without issues. However, after finally getting some computer time yesterday I tried to build guile master on my Mac, and when I checked the terminal window quickly

bug#40809: Apology: documentation for srfi-modules broken?

Hello Guilers! I submitted my patch for srfi-171 which got merged. I built it (or rather: I believe I did) on my little arm board without issues. However, after finally getting some computer time yesterday I tried to build guile master on my Mac, and when I checked the terminal window quickly

bug#36808: Unable to find GNU libunistring when building Guile 2.2.6

I'm closing this, suspecting that the issue has been resolved in newer versions of Guile or the platform, or... But please feel free to re-open it if that's mistaken. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B

bug#72086: scm_i_utf8_string_hash overruns buffer when len is zero

The first patch attempts to fix that, and the second is an optimization when then input is ASCII (since we already have the information we need to detect that): >From 619e3d3afec2c116007d9cb2ad32a500fb32a7dd Mon Sep 17 00:00:00 2001 From: Rob Browning Date: Sun, 30 Jun 2024 22:41:40 -0500

bug#72085: test-suite missing dependency on guile-procedures.txt

Some of the tests in the test-suite depend on guile-procedures.txt, but nothing currently indicates that, and so a build in a clean tree may fail. This patch tries to fix that: >From 2e391649fc17c1ecaa297e5ce4bf2bfae0963eaf Mon Sep 17 00:00:00 2001 From: Rob Browning Date: Sun, 30 Jun 2024

bug#72084: GUILE-VERSION changes don't propagate to .version and Makefile(s)

Changing GUILE-VERSION doesn't update these deriviative files. This patch may fix that: >From 485b9c282e0b4e6c6317666129e433e90acf4dea Mon Sep 17 00:00:00 2001 From: Rob Browning Date: Sun, 30 Jun 2024 12:27:38 -0500 Subject: [PATCH 1/1] Ensure GUILE-VERSION changes propagate to .version and

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.

Hi Maxim, On Wed, 10 Jul 2024 at 15:48, Maxim Cournoyer wrote: > I think I'd prefer more simple examples than a single more complicated > one, if we go that route. I think the text explained 'peek' clearly > already, though, so I personally would opt to leave it as is, especially > since

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

Hi Simon, Simon Tournier writes: [...] >> +@lisp >> +(map (lambda (v) >> + (if (number? v) >> + (number->string v) >> + (pk v))) >> + '(1 "2" "3" 4)) >> +@result{} >> + >> +;;; ("2") >> + >> +;;; ("3") >> +("1" "2" "3" "4") >> +@end > > For what it is worth, I

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

Hi, On Tue, 02 Jul 2024 at 12:28, Juliana Sims wrote: > * doc/ref/api-debug.texi: Document the peek and pk procedures. Cool! Thanks. > 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 >

bug#72041: [PATCH] Fix object file format description

* doc/ref/vm.texi (Object File Format): fix .guile.frame-maps section name. --- doc/ref/vm.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/ref/vm.texi b/doc/ref/vm.texi index b0669f0d4..60d69ddb3 100644 --- a/doc/ref/vm.texi +++ b/doc/ref/vm.texi @@ -530,7 +530,7 @@ A

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

Hi Juliana, Juliana Sims writes: > * 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

bug#71980: close 71980

close 71980

bug#71980: close

close

bug#71980: tmpnam

See also bug #71796, which has smaller delta.

bug#71980: [3.0.10] posix.test uses depcrecated tmpnam

On 2024-07-07 09:27:14 -0700, Matt Wette wrote: > With `--disable-tmpnam'  argument to configure, posix.test fails: missing > `tmpnam`. > > patch attached There also is #71796 as a possible patch (since June 27th), which is arguably bit smaller (albeit I am biased since I am the author over there

bug#71980: [3.0.10] posix.test uses depcrecated tmpnam

With `--disable-tmpnam'  argument to configure, posix.test fails: missing `tmpnam`. patch attached --- test-suite/tests/posix.test-orig    2024-07-03 15:45:16.352132881 -0700 +++ test-suite/tests/posix.test    2024-07-07 09:21:53.342855356 -0700 @@ -361,20 +361,21 @@    (status:exit-val

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

bug#71304: [PATCH] Add support for 'else' clause in R7RS cond-expand.

Hello Arne, "Dr. Arne Babenhauserheide" writes: > Maxim Cournoyer writes: > >> * module/ice-9/r7rs-libraries.scm (define-library) >> : Add a pattern to match an 'else' clause. > > This looks good to me. I applied and pushed it. Yay! Thank you. -- Maxim

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

Hi Juliana! Juliana Sims writes: > * doc/ref/api-debug.texi: Document the peek and pk procedures. This looks very useful! Thanks for authoring it. > --- > doc/ref/api-debug.texi | 187 +++-- > 1 file changed, 179 insertions(+), 8 deletions(-) > > diff

bug#71800: [PATCH 0/2] Improve documentation about using modules.

Hi Tomas! Tomas Volf <~@wolfsden.cz> writes: > Document the #:hide argument. Correct text for implication of leaving > all optional arguments out. > > Tomas Volf (2): > doc: Document #:hide. > doc: Fix implication of omitting optional arguments. > This looks good to me. Reviewed-by: Maxim

bug#71891: 3.0.10 may be broken on 32-bit architectures

First noticed via https://buildd.debian.org/guile-3.0 on armel, armhf and i386: https://buildd.debian.org/status/fetch.php?pkg=guile-3.0=armel=3.0.10-1=1719706962=0 https://buildd.debian.org/status/fetch.php?pkg=guile-3.0=armhf=3.0.10-1=1719706478=0

bug#71304: [PATCH] Add support for 'else' clause in R7RS cond-expand.

Maxim Cournoyer writes: > * module/ice-9/r7rs-libraries.scm (define-library) > : Add a pattern to match an 'else' clause. This looks good to me. I applied and pushed it. Best wishes, Arne -- Unpolitisch sein heißt politisch sein, ohne es zu merken. draketo.de signature.asc Description: PGP

bug#71800: [PATCH 1/2] doc: Document #:hide.

* doc/ref/api-modules.texi (Using Guile Modules): Document #:hide. --- doc/ref/api-modules.texi | 29 ++--- 1 file changed, 18 insertions(+), 11 deletions(-) diff --git a/doc/ref/api-modules.texi b/doc/ref/api-modules.texi index 9f2bba02d..efe739a25 100644 ---

bug#71800: [PATCH 2/2] doc: Fix implication of omitting optional arguments.

According to the previous wording, omitting all optional arguments led to empty interface. That however was not the case and was only a documentation bug (as confirmed by wingo on IRC). So let us fix that. * doc/ref/api-modules.texi (Using Guile Modules): Fix implication of omitting optional

bug#71800: [PATCH 0/2] Improve documentation about using modules.

Document the #:hide argument. Correct text for implication of leaving all optional arguments out. Tomas Volf (2): doc: Document #:hide. doc: Fix implication of omitting optional arguments. doc/ref/api-modules.texi | 29 ++--- 1 file changed, 18 insertions(+), 11

bug#71798: [PATCH 1/2] doc: Document #:hide.

* doc/ref/api-modules.texi (Using Guile Modules): Document #:hide. --- doc/ref/api-modules.texi | 29 ++--- 1 file changed, 18 insertions(+), 11 deletions(-) diff --git a/doc/ref/api-modules.texi b/doc/ref/api-modules.texi index 9f2bba02d..efe739a25 100644 ---

bug#71799: [PATCH 2/2] doc: Fix implication of omitting optional arguments.

According to the previous wording, omitting all optional arguments led to empty interface. That however was not the case and was only a documentation bug (as confirmed by wingo on IRC). So let us fix that. * doc/ref/api-modules.texi (Using Guile Modules): Fix implication of omitting optional

bug#71796: [PATCH] Do not depend on tmpnam in posix.test.

`tmpnam' is a deprecated procedure that can be excluded during a configure (`--disable-tmpnam'). There currently was a single test relying on it, and therefore failing is such configuration. This commit switches to mkstemp instead. * test-suite/tests/posix.test ("system*"): Use mkstemp instead

bug#71765: 3.0.10: make check fails when configure --disable-tmpnam

In 3.0.10, if I use the --disable-tmpnam argument to configure, then `make check' fails Running ports.test Running posix.test In execvp of something-that-does-not-exist: No such file or directory In execvp of something-that-does-not-exist: No such file or directory In execvp of

bug#71752: commit 57a889b72 breaks cross compilation of 32bit target on 64bit host

Hello commit 57a889b7282dab303c4cdc49cccbbe22f961bd1c: commit 57a889b7282dab303c4cdc49cccbbe22f961bd1c Author: Jonas Hahnfeld Date: Thu Feb 22 22:09:42 2024 +0100 build: Fix cross-compilation in out-of-tree-builds gen-scmconfig.h is generated in libguile, not

bug#71742: [3.0.10] make check fails when configure --disable-tmpnam

In 3.0.10, if I use the --disable-tmpnam argument to configure, then `make check' fails Running ports.test Running posix.test In execvp of something-that-does-not-exist: No such file or directory In execvp of something-that-does-not-exist: No such file or directory In execvp of

bug#71696: evaling an `eval-when' form leads to errors for guile-3-d2613

If you `eval` an form containing eval-when in a scheme program it fails with a syntax-violation with respect to definitions. Specifically there is a syntax-violation that isn't present in REPL usage: "definition in expression context, where definitions are not allowed in form ~a". This is

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

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

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 ERROR

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

bug#71303: [PATCH] doc: Fix typo in PEG example.

Patch applied in 4fe6d19a5baa43910f346656539c6942d436572b. Thank you!

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

> 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... an API is facilitating efficient reading comprehension when the "verbs" are closer to the beginning of the "sentence" (the

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

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

apparently this has been fixed between 3.0.9 and HEAD. i've wasted my time chasing a ghost... can we please have a new release? :) as a sidenote, i also had some broken expectations in my test.scm. it's a tangential, but namely, when #:unwind #t then the handler in a w-e-h returns from the

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

i was once again hindered by this, so i digged deeper. please find a test.scm attached. looks like (R6RS) WITH-EXCEPTION-HANDLER has such a surprising semantics that i didn't even consider that to be the case. some hours later i found this:

bug#71416: Dead link in the Guile manual

In the documentation page: https://www.gnu.org/software/guile/manual/html_node/Syntax-Rules.html#Further-Information the link to "Joe Marshall’s syntax-rules Primer for the Merely Eccentric" is dead: https://sites.google.com/site/evalapply/eccentric.txt There's an extant (and cleaned up by

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

Ping. I would be grateful if you maintainers could push this Libraries web page fix to guile-web.git. Maxim Cournoyer writes: > Hi Florian, > > "pelzflorian (Florian Pelz)" writes: > >> Hello Maxim, this patch is confusingly about the Guile website, not >> Guix. ;) That is

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)

bug#71304: [PATCH] Add support for 'else' clause in R7RS cond-expand.

* module/ice-9/r7rs-libraries.scm (define-library) : Add a pattern to match an 'else' clause. Series-to: bug-guile@gnu.org --- module/ice-9/r7rs-libraries.scm | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/module/ice-9/r7rs-libraries.scm b/module/ice-9/r7rs-libraries.scm

bug#71303: [PATCH] doc: Fix typo in PEG example.

* doc/ref/api-peg.texi (PEG API Reference): Fix typo in PEG example. --- doc/ref/api-peg.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/ref/api-peg.texi b/doc/ref/api-peg.texi index a6ab7080d..d34ddc64c 100644 --- a/doc/ref/api-peg.texi +++ b/doc/ref/api-peg.texi

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

Hi, Maxim Cournoyer writes: > Hi, > > Mike Gran writes: > >>> 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

bug#71301: [PATCH] module: Add some docstrings to (system base compile).

* module/system/base/compile.scm (next-pass): Add doc. (compute-compiler, read-and-compile, compile): Likewise. --- module/system/base/compile.scm | 11 +++ 1 file changed, 11 insertions(+) diff --git a/module/system/base/compile.scm b/module/system/base/compile.scm index

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

This is an import of the 'Abstract', 'Rationale', and 'Specification' sections from the upstream specification text, with some manual adjustment. * doc/ref/srfi-modules.texi (SRFI 64): New subsection. --- Changes in v3: - Add copyright / license information - Replace SchemeUnit mentions with

bug#71268: [PATCH v5 1/4] (ice-9 boot-9): Fix typo.

* module/ice-9/boot-9.scm (module-use-interfaces!): Fix typo in doc string. --- (no changes since v1) module/ice-9/boot-9.scm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/module/ice-9/boot-9.scm b/module/ice-9/boot-9.scm index 378ae2457..10423d35e 100644 ---

bug#71268: [PATCH v5 2/4] .dir-locals: Set c-basic-offset to 2 for c-mode.

* .dir-locals.el (c-mode): Set c-basic-offset to 2. --- (no changes since v1) .dir-locals.el | 1 + 1 file changed, 1 insertion(+) diff --git a/.dir-locals.el b/.dir-locals.el index 908670479..f63bdc8a3 100644 --- a/.dir-locals.el +++ b/.dir-locals.el @@ -3,6 +3,7 @@ ((nil .

bug#71268: [PATCH v5 4/4] load: Display modules depth in output when using %load-verbosely.

* NEWS: Update news. * THANKS: Add myself. * doc/guile-api.alist (%load-announce, %load-hook): Add DEPTH argument. * doc/ref/api-evaluation.texi (Loading): Document new DEPTH argument for the primitive-load, primitive-load-path and %load-hook procedures. Update %load-hook example. Document

bug#71268: [PATCH v5 3/4] guix.scm: Add git:send-email to environment, for convenience.

* guix.scm (guile) [native-inputs]: Add git:send-email. --- (no changes since v1) .guix/modules/guile-package.scm | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.guix/modules/guile-package.scm b/.guix/modules/guile-package.scm index ad297a010..bca8d3cdf 100644 ---

bug#71268: [PATCH v5 0/4] Add module depth information to %load-verbosely output

This change was made to support investigating cyclic module dependencies that sometimes happen in GNU Guix and are difficult to comprehend/debug. For more context, see: . Changes in v5: - Introduce the usage of keywords for %load-hooks, breaking backward

bug#71262: [PATCH] Try to install C.UTF-8 locale before falling back to C.

If user does not have LANG or LC_ALL set (as does often happen in various sandboxes) glibc will just install C locale. That is fine (and permissible by POSIX), however in Guile's context it is of a mixed usefulness due to the absence of UTF-8 support. This commit changes the locale

bug#71253: [PATCH] doc: minor typo fix

See attachment. From bfeb86d9c7c258ac67de9cdd0b6eabbc01ab0114 Mon Sep 17 00:00:00 2001 From: Nikolaos Chatzikonstantinou Date: Tue, 28 May 2024 23:27:38 -0400 Subject: [PATCH] doc: minor typo fix The incorrect procedure is mentioned; see the example that immediately follows. *

bug#71047: [PATCH] doc: Recommend alist-copy instead of list-copy.

The current recommendation of `list-copy' is not right and does not lead to preserving the original list: scheme@(guile-user)> (define x (list (cons 'a 1) (cons 'b 2))) scheme@(guile-user)> (define y (list-copy x)) scheme@(guile-user)> (assq-set! y 'b 3) $1 = ((a . 1) (b . 3))

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

Hi Florian, "pelzflorian (Florian Pelz)" writes: > Hello Maxim, this patch is confusingly about the Guile website, not > Guix. ;) That is https://git.savannah.gnu.org/git/guile/guile-web.git > > It uses Guix to generate the Guile package list, where guile-gnunet has > homepage

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

Hi Ludo, On lun., 06 mai 2024 at 11:34, Ludovic Courtès wrote: >>> -stage0) >>> GUILE_LOAD_COMPILED_PATH="${top_builddir}/stage0:${top_srcdir}/prebuilt/@SCM_PREBUILT_BINARIES@" >>> ;; >>> +stage0) >>>

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

bug#70144: system* affects signal handlers

Hi, Josselin Poiret skribis: > Yes, I believe this is all taken care of by our use of posix_spawn > (which was the point in the first place :) ). Yup! I pushed the fix as 4ae33f76d6b33ea0bedfa36050d44c88d08c2823. Thanks, Ludo’.

bug#67063: unread-string does not match documented functionality

Hi Juliana, Juliana Sims skribis: > This patch simply fixes bug 67063. > > Thanks, > Juli > > * doc/ref/api-io.texi (Venerable Port Interfaces): Bring unread-string > procedure documentation in line with other procedures in the section. > * libguile/ports.c (scm_unread_string): Make port

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

Hi Michael, Michael Käppler skribis: > The reason is that format strings occurring in the message are > escaped, see `module/ice-9/boot-9.scm`  and > `module/language/tree-il/primitives.scm`. > > So a call of > > `(error "Wrong argument: ~a" 42)` > > is rendered as > > "Wrong argument: ~a 42" >

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

Jonas Hahnfeld skribis: > 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

bug#69315: [PATCH] Build system fixes

Hi Jonas, Jonas Hahnfeld skribis: > From 428d1b17c5f664d3cb8da4cd5687bd47bdd87877 Mon Sep 17 00:00:00 2001 > From: Jonas Hahnfeld > Date: Thu, 22 Feb 2024 21:57:41 +0100 > Subject: [PATCH 1/2] build: Make sed invocation fully portable > > Commit 08041d216f attempted to make the "invocation

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

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:44:55 +0100 >> Subject: [PATCH] Speed up stage0 bootstrap build using

bug#68878: [PATCH] Fix typos throughout codebase.

Hi Morgan, Applied, with one exception: Morgan Smith skribis: > * lib/alloca.in.h: > * lib/c-ctype.h: > * lib/malloca.h: > * lib/nstrftime.c: > * lib/verify.h: > * lib/xalloc-oversized.h: Since these files come from Gnulib, not from Guile, I left them unchanged. Thanks! Ludo’.

bug#69730: Segfault in (spawn) when passed wrong port

Hi, Tomas Volf <~@wolfsden.cz> skribis: > When I pass #f to spawn as a port, it just segfaults: > > $ guile -c '(spawn "true" (list "") #:error #f)' > Segmentation fault This was fixed a while back in the ‘main’ branch: --8<---cut here---start->8---

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"

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:  

bug#70144: system* affects signal handlers

Hi, Mikael Djurfeldt skribis: > system* temporarily re-binds signal handlers to prevent the child process > from killing the parent. Thus, it is not thread safe with regard to SIGINT > (or SIGQUIT if available). So, your code has a race condition with respect > to the signal handler. This

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

[Adding Andy Wingo because of the stack shenanigans] >Subject: exception from inside false-if-exception? Duplicate of #46009 - (backtrace) crash, string->number: Wrong type argument in position 1 (expecting string): #f - GNU bug report logs >the expression pointed to by debug.scm,72:40 is

bug#70645: Reliable HTTPS networking

Christopher Baines writes: > For years now I've been trying to work out how to do reliable HTTPS > networking with Guile, where reliable just means that it can't hang > indefinitely. > > After a few wrong turns, I believe the way to do this is use > non-blocking ports as that combined with

bug#70645: [PATCH 1/2] Allow specifying the socket style for open-socket-for-uri.

Since this allows specifying additional behaviours for the socket through using SOCK_CLOEXEC and/or SOCK_NONBLOCK (when bitwise or'ed with SOCK_STREAM). Note that Guile/guile-gnutls currently doesn't support performing the TLS handshake on a non-blocking socket, so this currently won't work. *

bug#70645: [PATCH 2/2] web: Handle non-blocking ports in tls-wrap.

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 retry of the handshake, after waiting

bug#70645: Reliable HTTPS networking

For years now I've been trying to work out how to do reliable HTTPS networking with Guile, where reliable just means that it can't hang indefinitely. After a few wrong turns, I believe the way to do this is use non-blocking ports as that combined with suspendable ports in Guile allows you to

bug#70640: A Texinfo aware `,describe` command.

Hello hackers, I have noticed there are many docstrings containing Texinfo markup, but when one runs the `,describe` command, one gets the Texinfo markup source, not a render of those Texinfo commands. I wish to write a better `,describe` command that would render Texinfo in a pleasant way.

bug#70628: segmentation fault reading socketpair after fork

Dear Sir/Madam, The 62 lines of code in the attachment result in a segmentation fault when run. I hope you can help suggest a fix or a workaround. user@pcxy:~/$ guile --version guile (GNU Guile) 3.0.7 Packaged by Debian (3.0.7-deb+3.0.7-1) user@pcxy:~/$ make gcc -I/usr/include/guile/3.0 -g -c

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

Hello Maxim, this patch is confusingly about the Guile website, not Guix. ;) That is https://git.savannah.gnu.org/git/guile/guile-web.git It uses Guix to generate the Guile package list, where guile-gnunet has homepage https://gnu.org/software/guix and is thus called Guix in the Guile website

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

Hi Florian, Florian Pelz writes: > * website/apps/base/libraries-page.scm (guix->package)[real-name]: > Add special case. > --- > website/apps/base/libraries-page.scm | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/website/apps/base/libraries-page.scm >

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

This is a nice idea. The way Racket does it is to make with-output-to-string cooperate with system: (with-output-to-string (lambda () (system "date"))) but a quick check shows that Guile does not yet have such cooperation in place. Would that be a good place to start looking? Tony On

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

Dear All , I've been encountering a few times the need for a procedure like 'system' or 'system*' but that might be capable of capturing the output of the program that's being called. While this is something that can be solved with a simple 'open-pipe*' wrapper, the pattern seems relatively

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

bug#70474: [PATCH] Move the spin loop target to the LDAXR instruction.

Andy Wingo in IRC pointed out that the reason the patch appears to work is that the `movr` isn't idempotent! By the time it comes round again, `val` has already been overwritten by LDAXR in the case that `dst == val`. On 22/04/2024 10:18, Tony Garnock-Jones wrote: Oh man. This little patch all

bug#70474: [PATCH] Move the spin loop target to the LDAXR instruction.

Oh man. This little patch all by itself makes the problem behaviour go away. No switching to SWPAL/CASAL, just tightening the spinloop. (And no changes at all to the CAS code, so nothing to do with the fibers bug I guess.) With the patch, the spinloop goes LDAXR-STLXR-CBNZ (which is what GCC

bug#70474: Just adding DMB doesn't help

As an alternative to changing the JIT to produce SWPAL/CASAL, because I wasn't sure if *all* aarch64 targets support these, I tried adding DMB ISH or DMB SY to the end of the generated code sequences. Surprisingly, this did not fix the issue! So there's perhaps something fishy about the

bug#70510: Small documentation error for case-lambda*

Hi, I've been familiarizing myself with scheme and guile by haphazardly reading documentation and experimenting, and I believe I have found an error in the docs here: https://www.gnu.org/software/guile/manual/html_node/Case_002dlambda.html The example at the bottom of the page reads as

bug#70474: [PATCH 2/2] Replace aarch64 CAS and atomic-swap generated JIT code with CASAL and SWPAL instructions

This appears to make the problem go away. I'm new at working with `lightening` so I'm not confident I've covered everything that needs covering, particularly wrt the implementation of cas_atomic. But perhaps this can be a foundation for someone who knows more than I do to work from. ---

bug#70474: [PATCH 1/2] Including the cast makes Apple clang 15.0.0 happy; without it, clang is sad

I'm not sure why, exactly, but I needed this to get builds to work on OSX Sonoma at all. --- libguile/scmsigs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libguile/scmsigs.c b/libguile/scmsigs.c index 7fd3fd8f1..be96dbd5c 100644 --- a/libguile/scmsigs.c +++

bug#70474: Also manifests on an M1 running 14.1.1 and with newer Guile versions

A small bit of extra information: it's not just one machine; the problem also manifests on an M1 running OSX 14.1.1. In addition, it happens with newer Guile versions including `guile-next` from `aconchillo`'s Homebrew tap and including a version I built from Guile git main just now. Regards,

bug#70474: Possible bug with `atomic-box-swap!` on OSX/M3 (?!?!)

Tony Garnock-Jones writes: > I'm seeing some very strange behaviour from `atomic-box-swap!` (but > not `atomic-box-compare-and-swap!`) on Guile 3.0.9 from Homebrew on > OSX Sonoma using an M3 Pro cpu. The issue does not seem to manifest on > x86_64. Could it be some interaction between Guile and

bug#70474: Possible bug with `atomic-box-swap!` on OSX/M3 (?!?!)

Hello all, I'm seeing some very strange behaviour from `atomic-box-swap!` (but not `atomic-box-compare-and-swap!`) on Guile 3.0.9 from Homebrew on OSX Sonoma using an M3 Pro cpu. The issue does not seem to manifest on x86_64. Could it be some interaction between Guile and M3 CPUs? Or am I

bug#20272: Support reproducible builds

On 08/04/2024 19.27, Thompson, David wrote: I don't know what the solution might be, though. I want parallel *and* reproducible builds! For openSUSE we are using -j1 builds everywhere until a better solution is found. https://code.opensuse.org/package/guix/blob/006c5b9d16/f/guix.spec#_112

bug#20272: Support reproducible builds

On Fri, Nov 17, 2023 at 3:29 PM Bernhard M. Wiedemann wrote: > > Parallel builds with guile-3.0.9 still introduce non-determinism I recently learned that the cross-module inlining optimization pass is a source of nondeterminism. If module A imports module B, inlining of procedures from B into A

bug#70144: system* affects signal handlers

system* temporarily re-binds signal handlers to prevent the child process from killing the parent. Thus, it is not thread safe with regard to SIGINT (or SIGQUIT if available). So, your code has a race condition with respect to the signal handler. This common resource can, in principle, be handled

bug#70144: system* affects signal handlers

I've encountered a situation where signal handlers don't seem to run. With the following program, sending it SIGINT won't trigger the handler, however if you remove the system* call, then the handler will run. (use-modules (ice-9 threads)) (call-with-new-thread (lambda () ;; Remove

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)"

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

  1   2   3   4   5   6   7   8   9   10   >