Re: [PATCH] Fix build of guile-3.0 trunk with gcc-8 on hpux11.11

2020-03-23 Thread John David Anglin
Hi Massimiliano, I don't think so.  I have a recent build of bdwgc from github including this change: https://github.com/ivmai/bdwgc/issues/308 The bdwgc testsuite is clean. The patch that I submitted in issue 308 was to help in debugging issues with guile.  HEURISTIC2 causes faults during star

Re: [PATCH] Fix build of guile-3.0 trunk with gcc-8 on hpux11.11

2020-03-23 Thread Massimiliano Gubinelli
Hi John, could maybe be a bug with the Boehm-gc? I had some recent issues compiling Guile 2.2.7 in Haiku and discovered that there is a new version (8.1.0, next release development) of the GC here https://github.com/ivmai/bdwgc which has some changes, in parti

Re: [PATCH] Add srfi-171 to guile

2020-03-23 Thread Linus Björnstam
Hi Ludo! All things except some of the docstrings are fixed. The reason not all of the docstrings are fixed according to the suggestion is that the reducers you specifically used as examples do not return reducers, but ARE reducers, and specifically they are srfi-171-styled reducers. i.e: they

Re: Python on guile

2020-03-23 Thread Arne Babenhauserheide
Stefan Israelsson Tampe writes: > Now in corona times I'm working quite a lot with python-on-guile fixing > bugs in the parser and compiler. Trying to add and test more python > modules. My test case is to get IPython running on python on guile. You’re awesome! Thank you! It sounds like the t

[PATCH] Fix build of guile-3.0 trunk with gcc-8 on hpux11.11

2020-03-23 Thread John David Anglin
The following change fixes the build of guile-3.0 using gcc-8 on hpux11.11. There are three issues addressed: 1) The printf function does not support %zu. Since all the type sizes are small, we can use %u and cast the sizeof results to unsigned int. 2) HP-UX 11.11 does not have readdir64 or rea

Re: definitions in macros?

2020-03-23 Thread Han-Wen Nienhuys
On Sun, Mar 22, 2020 at 10:09 PM David Kastrup wrote: > > In the code below, it looks like only one of the two definitions in > > the body of my-macro-new takes effect. Is this expected, and if so, > > why? > > > > (defmacro-public my-macro-old (command-and-args . definition) > > (module-define!