Re: Add internal definitions to derived forms

Ludovic Courtès writes: > The reason I’m hesitant is that, while I think it’s nice to be able to > have local ‘define’ in these contexts, I’m wary of diverging from R5RS > and R6RS. Since it’s a one-way change (we won’t be able to revert it > once people rely on it), I thought we’d rather be

Re: GNU Guile 3.0.9rc1 available for testing!

Ludovic Courtès writes: > So something like the patch below? > > Thanks, > Ludo’. > > diff --git a/libguile/posix.c b/libguile/posix.c > index 74c743119..0b1fe2637 100644 > --- a/libguile/posix.c > +++ b/libguile/posix.c > @@ -105,8 +105,8 @@ > # else > # define W_EXITCODE(ret, sig) ((ret)

Re: GNU Guile 3.0.9rc1 available for testing!

Ludovic Courtès writes: > My understanding is that the expectation of being able to later mprotect > that mapping to make it writable is a valid one per POSIX. Quoth > : > > If PROT_WRITE is specified, the application

Re: GNU Guile 3.0.9rc1 available for testing!

Greg Troxel writes: > with or without -j2. I see ice-9/readline.scm in git but not in the > rc tarball. and, in guile-readline/Makefile.am I see if HAVE_READLINE SOURCES += ice-9/readline.scm and I don't see an else with EXTRA_DIST. I think it's a bug for make dist contents t

Re: GNU Guile 3.0.9rc1 available for testing!

My second approach is using the rc tarball in pkgsrc. I had to patch out the verify call. pkgsrc already works around PaX issues mostly, via paxctl on things that do jit, after build and before use, and by --- libguile/loader.c.orig 2018-01-08 16:21:04.790894906 + +++

Re: GNU Guile 3.0.9rc1 available for testing!

lloda writes: > This looks like https://debbugs.gnu.org/60971 > on mac os. Yes, it does. My quick reaction is that if the POSIX-required macros operation on system types that might be struct, then faking up ints for testing is unsound. Maybe only do verify if

Re: GNU Guile 3.0.9rc1 available for testing!

Ludovic Courtès writes: > Hello Guilers! > > (Cc’ing packagers I know; feel free to ping other packagers!) I dropped the CC as I suspect all are on guile-devel. > Please report any issues you may find. I’m particularly interested in > portability regressions (NetBSD and other BSDs, macOS,

Re: [PATCH] web: default to INADDR_ANY instead of INADDR_LOOPBACK

Aleix Conchillo Flaqué writes: >> Using INADDR_ANY instead of INADDR_LOOPBACK makes it convenient when >> starting the web server inside containers without the need to having to >> specify INADDR_ANY all the time. This is the default in most libraries >> and languages. I may be an outlier, but

Re: mmap for guile

Ludovic Courtès writes: > Greg Troxel skribis: > >> I have been meaning to try to build this under NetBSD, to check >> portability. I think the mmap code should by default rely only on what >> POSIX guarantees: >> https://pubs.opengroup.org/onlinepubs/

Re: mmap for guile

Ludovic Courtès writes: > Besides what Maxime points out, some more superficial issues: > > • In documentation, please refer to the relevant glibc section instead > of “See man page” (info "(libc) Memory-mapped I/O"). > > • Please update doc/ref with a section on memory-mapped I/O. > >

Re: GNU Guile 3.0.8 released

Aleix Conchillo Flaqué writes: > On Fri, Feb 11, 2022 at 3:05 AM Maxime Devos wrote: > >> Andy Wingo schreef op vr 11-02-2022 om 08:47 [+0100]: >> > We are delighted to announce GNU Guile release 3.0.8, the latest in the >> [...] >> > The Guile 3.0.8 release mixes maintenance and optimizations

Re: (web server) serving on both ipv6 and ipv4?

"Dr. Arne Babenhauserheide" writes: > Greg Troxel writes: > >> [[PGP Signed Part:Signature made by expired key 1FDA7AE8098ED60E Gregory D. >> Troxel (low security, at work) ]] >> >> Maxime Devos writes: >> >>> Maybe the

Re: (web server) serving on both ipv6 and ipv4?

Maxime Devos writes: > Maybe the IPV6_V6ONLY (see the ipv6(7) man page) is relevant here. > Alternatively, you could run two servers in parallel: one bound to an > IPv4 address and another bound to an IPv6 address. My feeling is that IPV6_ONLY is best avoided, for portability, and because

shlib major change from 3.0.3 to 3.0.4

I am packaging guile 3 in pkgsrc-wip. (It's not promoted to pkgsrc proper because I am still having some issues.) Doing the update from 3.0.3 to 3.0.4 I found this change in install files: -guile/3.0/lib/libguile-3.0.so.3.0.0-gdb.scm +guile/3.0/lib/libguile-3.0.so.1.2.0-gdb.scm and that

pax mprotect and guile build process

(I think I may have reported this earlier but I can't find it.) NetBSD runs with pax mprotect by default. Guile's JIT has trouble with this, due to the nature of JIT. In pkgsrc, we have: NOT_MPROTECT_SAFE+= ${GUILE_PREFIX}/bin/guile to do "paxctl +m" for guile as installed. However,

strange shlib version change in 3.0.4

I am updating the guile 3.0 package in pkgsrc (in pkgsrc-wip for now) from 3.0.3 to 3.0.4. I noticed the following (which is really pkgsrc telling me that the new shlib is different from the old one): ERROR: ERROR: The following files

clang bug on mac, workaround

Recently someone added this line of workaround to pkgsrc: ENV.append_to_cflags "-fno-stack-check" if DevelopmentTools.clang_build_version >= 1010 (from https://github.com/Homebrew/homebrew-core/blob/master/Formula/guile.rb#L42 ) for guile 2.2.7. I don't know yet if this affects 3,

JIT and pax mprotect

In trying to build 3.0.2 on NetBSD 8, I get a permission denied failure in JIT, because of PaX MPROTECT. Disabling that (in the individual file, or globally) allows things to work. This is a security feature that prevents making writable mappings executable. I would expect this to run into

Re: C calling Scheme and garbage collection

Isaac Jurado writes: > On Thu, Jun 27, 2019 at 9:52 PM Greg Troxel wrote: > >> I have been down this path before, with guile and with lua. Basically, >> if C (or non-scheme) has a pointer to a scheme object, then you need to >> hold a logical reference for it and p

Re: C calling Scheme and garbage collection

Isaac Jurado writes: > Hello, > > I'm playing with event loop libraries implemented in C (libev, libevent, > etc... in my case libsystemd), but configuring them from Guile. > > The qsort example in the documentation [1] seems safe because the qsort C > function directly calls back, so the

minor mmap protection issue

pkgsrc has the following patch for 2.2.5. At first glance it looks at least headed in the right direction, but I'd appreciate someone more familiar with the code looking and either making a corresponding fix or explaining the issue more. As I understand it, POSIX is a bit vague on this issue:

Re: Coexistence of different Guile versions

Tommi Höynälänmaa writes: > Guile (at least the Debian version) is designed so that different > versions (e.g. 2.0 and 2.2) can coexist in the same system. However, > this is not so for packages guile-xxx-dev. Consequently, many software > libraries (such as guile-gnome-platform) have to be

Re: moving to gitlab?

Aleix Conchillo Flaqué writes: > Any chance or interest in moving to gitlab? My apologies if this has > been discussed already. Not that I ever contribute anything directly > to Guile (2 patches in 6 years?), but it feels like it would be an > improvement in terms of communication, sending

Re: c99 support

Andy Wingo writes: > Is there anyone who compiles Guile with a compiler that does not support > C99? If so, please give platform and compiler. Not really the question you asked, and pretty fuzzy, but an anecdote about a real situation I am aware of: In 2015--2016, there was some C code

Re: 2.2.0 release plan

Andy Wingo writes: > However! Even though the code says 2.2.0 and the tag says 2.2.0, the > release is not until Thursday. I will not upload the tag yet. I have just barely caught up with 2.0.x in pkgsrc, and haven't gotten to testing 2.1.x yet. I wonder how many platforms

Re: mkostemp portability issues

Matt Wette <matt.we...@gmail.com> writes: >> On Feb 20, 2017, at 6:39 PM, Greg Troxel <g...@lexort.com> wrote: >> + open_flags = O_APPEND|O_DIRECT|O_SHLOCK|O_EXLOCK|O_SYNC|O_CLOEXEC; > > I think you meant `&=‘ Thanks, fixed. Interestingly most of th

mkostemp portability issues

Earlier I reported that 2.0.13 did not build on NetBSD. Matt Wette pointed me to a debbugs entry. The issue seems to be that mkostemp is not a POSIX-specified interface and the list of acceptable flags differs on different platforms. I have included the patch I just added to pkgsrc, which

Re: Native code generation and gcc

Mikael Djurfeldt writes: > Are there fundamental reasons for not re-using the gcc backends for native > code generation? I'm thinking of the (im?)possibility to convert the cps to > some of the intermediate languages of gcc. Also there is llvm. If there are issues, they

Re: Parallel installation of guile-2.1.x

Jan Synáček writes: > I'd like to package guile-2.1.x so it could be used along with 2.0.13. > Using --program-suffix during the configure phase is almost what I > would like, but not quite. The problem is that there still are files > (guile.m4 and guile.info + its parts)

guile-cairo status?

I just changed the guile-cairo entry in pkgsrc to guile 2.0 (we are belatedly switching). It is at 1.4,1, the last actual release. I see on savannah: http://www.nongnu.org/guile-cairo/ that there is a 1.9.91 preelease, but no actual following release. Is there a release later than 1.4.1?

guile-lib, compiled files, packages

(I have been sort of using guile for wicked long time, I think since before 1.0, but I have been not paying attention lately and just lurking.) I am maintaining entries for guile and friends in pkgsrc, a portable packaging system that supports many operating systems, versions of those systems,

Re: boehm-gc troubles with 2.0.11 on NetBSD/i386

A partial update: I am using 2.0.11 now. After updating to libgc 7.4.0, I have the same problem with a similar stack trace. libgc is built without threads and passes it's gmake check. I have the same problem with libgc 7.4.0 on netbsd-5/i386 (libgc passes gmake check on this

Re: guile-2.0.11 build: libtool and readline problems

Ian Grant ian.a.n.gr...@googlemail.com writes: I'm at a loss. I have libtool-2.4 installed in /usr/local and I get this error when 'make'ing after running ../configure --prefix=/usr/local --libdir=/usr/local/lib \ --with-libreadline-prefix=/usr/local [ making lots of stuff

Re: boehm-gc troubles with 2.0.10 on NetBSD/i386

I am using gc-7.2e, which is what pkgsrc has, and which http://www.hboehm.info/gc/ indicates is the latest stable version. This is with gcc 4.5.3 on i386. l...@gnu.org (Ludovic Courtès) writes: Greg, does libgc’s own ‘make check’ pass on this platform? Yes. libgc seems to have multiple

boehm-gc troubles with 2.0.10 on NetBSD/i386

I've been a guile user erratically for a long time, and maintain the entry for guile in pkgsrc. Currently that's at 1.8.8 and it works fine. There's a draft package for guile 2. boehm-gc in pkgsrc on NetBSD is built without threads, and I have --disable-threads passed to guile's configure.

Re: boehm-gc troubles with 2.0.10 on NetBSD/i386

Mark H Weaver m...@netris.org writes: Program received signal SIGSEGV, Segmentation fault. [Switching to LWP 1] 0xbba868ae in GC_find_limit_with_bound () from /usr/pkg/lib/libgc.so.1 (gdb) bt #0 0xbba868ae in GC_find_limit_with_bound () from /usr/pkg/lib/libgc.so.1 #1 0xbba8696e in

Re: 2.0.11 on OS X 10.9 / Xcode 5.1

taylanbayi...@gmail.com (Taylan Ulrich Bayırlı/Kammer) writes: taylanbayi...@gmail.com (Taylan Ulrich Bayırlı/Kammer) writes: On OS X 10.9 with Xcode 5.1, make fails unless -O0 is used; the output of ./configure make during the failure is here: http://sprunge.us/PLGI After a successful

Re: About Guile crypto support

Nala Ginrut nalagin...@gmail.com writes: On Sat, 2013-02-09 at 16:12 +0100, Ludovic Courtès wrote: Daniel Hartwig mand...@gmail.com skribis: An issue with the FFI is distros where .la and .so files are only available in the -dev package, because then ‘dynamic-link’ won’t work unless that

Re: Building on OpenBSD

Taylan Ulrich B. taylanbayi...@gmail.com writes: I wanted to note that, given a working boehm-gc (the next release, 7.2d, should work on OpenBSD 5.1, but newer OpenBSD versions, having switched to rthreads, will break it again), and a set of build flags similar to the following (these are

Re: Portability fixes for win32 cross compiling

Volker Grabsch v...@notjusthosting.com writes: Volker Grabsch v...@notjusthosting.com schrieb: Okay, I just implemented that approach and it seems to work fine. There were several other issues I had to fix. Please have a look at the attached patches (6 in total). All of them seem to be

Re: Reconsideration of MinGW work

Ken Raeburn raeb...@raeburn.org writes: One nagging concern I've got about my Guile-Emacs project is the seemingly narrow focus of active Guile developers as far as platforms are concerned. I'm one of, what, two or three people testing the development versions on Mac OS X now and then, and

Re: request tmpfile(3) wrapping in Guile 1.9 libguile

That said, welcome back to Guile! I'm really glad to hear this - we scheme weenies are few enough in this world that we need to stick together! pgpk2RfJafl3B.pgp Description: PGP signature

Re: Deprecate vs. discourage

l...@gnu.org (Ludovic Courtès) writes: I think things like ‘uniform-vector-read’ should be discouraged rather than deprecated, since it matches the definition in ‘discouraged.h’: A discouraged feature is one that shouldn't be used in new code since we have a better alternative now.

Re: TLS support on NetBSD

Thanks - I think there is actually no tls support yet. I will take a look at the autoconf issue when I have time - but I'm very busy at work this week.

Re: master with threaded gc

Thanks for all the replies. I'm not sure when I'll have a chance to look at this again, but master is building better on netbsd than it has in a long time! pgpYu8YEPA1Ki.pgp Description: PGP signature

Re: build of master now fails much earlier

are we really adding dependencies while we are 'frozen'??? checking for BDW_GC... configure: error: Package requirements (bdw-gc) were not met: Sorry if we did not communicate clearly; the plan was definitely to merge in bdw-gc before the release, and possibly during the freeze

build of master now fails much earlier

are we really adding dependencies while we are 'frozen'??? checking for BDW_GC... configure: error: Package requirements (bdw-gc) were not met: No package 'bdw-gc' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix.

Re: build failures of master on netbsd/5 amd64

The end of my build, from a few hours ago: /bin/ksh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -DBUILDING_LIBGUILE=1 -I.. -I.. -I../lib -I../lib -I/usr/pkg/include -I/usr/y0/include -I/usr/pkg/include -I/usr/y0/include -pthread -Wall -Wmissing-prototypes -Werror

netbsd/amd64 build getting further...

/bin/ksh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -DBUILDING_LIBGUILE=1 -I.. -I.. -I../lib -I../lib -I/usr/pkg/include -I/usr/y0/include -I/usr/pkg/include -I/usr/y0/include -pthread -Wall -Wmissing-prototypes -Werror -fvisibility=hidden -g -O2 -MT libguile_la-read.lo -MD

build failures of master on netbsd/5 amd64

I ran 'gmake -k' to get all the warnings at once. I think there are just two groups: gmake all-recursive gmake[1]: Entering directory `/home/gdt/BUILD-GUILE-master/guile' gmake[2]: Entering directory `/home/gdt/BUILD-GUILE-master/guile/libguile' gmake all-am gmake[3]: Entering directory

apparenty SCM_I_CHAR is fixed, but:

From my autobuild on master cc1: warnings being treated as errors In file included from vm-engine.c:133, from vm.c:322: vm-i-scheme.c: In function 'vm_regular_engine': vm-i-scheme.c:437: warning: comparison is always true due to limited range of data type vm-i-scheme.c:437:

Re: apparenty SCM_I_CHAR is fixed, but:

l...@gnu.org (Ludovic Courtès) writes: Mike Gran spk...@yahoo.com writes: On Wed, 2009-08-19 at 09:56 -0400, Greg Troxel wrote: From my autobuild on master vm-i-scheme.c:437: warning: comparison is always true due to limited range of data type For gcc, -Wtype-limits will catch

Re: `SCM_MAKE_CHAR ()' signedness issue

I think the problem is that the routine in question is fundamentally written to assume a signed input. Perhaps there should be an unsigned version that takes unsigned chars, and perhaps guile should explicit declare characters as one or the other. Or perhaps just always cast to unsigned char -

Re: i guess we're frozen stuff

l...@gnu.org (Ludovic Courtès) writes: My conclusion so far is that (void *)0 is a legal value for NULL Whether legal or not, under-parenthesized expression-like macros are likely to cause troubles one day or another. Thanks for your work with the upstream people! I now have a pointer to

Re: i guess we're frozen stuff

Today's the 10th, we release on the 15th, ergo we're frozen. What does this mean? Well I think the dilly is that we shouldn't be pushing to master, except to fix things that don't work at all, and to update documentation, NEWS, etc. What if you don't have push access? Well give Guile

Re: i guess we're frozen stuff

I built libunistring and tried to build master. Some tests failed, and also the build failed due to warnings (post to follow). I think all the failed tests are locale related. gmake check output on NetBSD/amd64 5.0 with libunistring 0.9.1: Making check in lib gmake[1]: Entering directory

Re: i guess we're frozen stuff

guile master fails to build on NetBSD because it passes characters to tolower, which is specified to take an int. It's really a macro, and this is a messy situation. The language weenies I've talked to about this think that in this case it's the program that passes a char that's wrong. Hence

Re: i guess we're frozen stuff

Does libunistring's make check pass on this platform? should have tried that. testlocale.c fails on line 38 with: test-locale.c:38: error: expected ')' before numeric constant expanding that with cpp gets me the rather stunning: extern int (* verify_function__ (void)) [(!!sizeof (struct

Re: i guess we're frozen stuff

l...@gnu.org (Ludovic Courtès) writes: Greg Troxel g...@ir.bbn.com writes: #define NULL (void *)0 This is under-parenthesized! Two actions to be taken: 1. Report a bug to your favorite libc maintainers. ;-) I think that's a legal value for NULL per C99. Interestingly it has

Re: Guile 2.x and `pkg-config'

l...@gnu.org (Ludovic Courtès) writes: A recent thread on `guile-user' [0] raises an important concern: what should we do with `guile-1.8.pc' when 2.x is out? How about shipping `guile-1.8.pc' for compatibility, along with `guile.pc' (which would then become the Right One), both with

Re: new dependency?

dsm...@roadrunner.com writes: Neil Jerram n...@ossau.uklinux.net wrote: Greg Troxel g...@ir.bbn.com writes: my autobuild choked with: configure: error: GNU libunistring is required, please install it. and I don't recall seeing any discussion about this. Hi Greg

Re: master build issue

Neil Jerram n...@ossau.uklinux.net writes: configure:52553: ccache gcc -o conftest -g -O2 conftest.c -L/usr/local/lib -lunistring -R/usr/local/lib -lgmp -lcrypt -lm -lltdl 5 gcc: unrecognized option '-R/usr/local/lib' My GCC is version 4.3.2, so pretty recent. Ludo, Andy, I'm

new dependency?

my autobuild choked with: configure: error: GNU libunistring is required, please install it. and I don't recall seeing any discussion about this. pgpTeIae3j2Eu.pgp Description: PGP signature

1.8 branch test failure

Git tree... release_1-8-6-53-g66f3b6c GCC version... gcc (GCC) 4.1.3 20080704 prerelease (NetBSD nb1 20080202) Differences: End differnces. [snip] FAIL: popen.test: open-input-pipe: open-input-pipe process gets (current-input-port) as stdin [snip] Totals for this test run: passes:

git server broken?

My autobuild failed, and on checking: list gdt 12 ~/BUILD-GUILE-1.8/guile git pull git.sv.gnu.org[0: 199.232.41.69]: errno=Connection refused fatal: unable to connect a socket (Connection refused) pgpMCBsYyRpJV.pgp Description: PGP signature

Re: 1.8 autobuild fails

Yes, it's new. Git tree... release_1-8-6-44-ge9c9fd3 This is my 1.8 branch autobuild: http://autobuild.josefsson.org/guile/log-200905090633244263000.txt And yes, including sys/types.h fixes this. At least on BSD, one generally needs to include sys/types.h before random header files in

1.8 autobuild fails

This fails in test-round.c. It's likely like foo.h needs sys/types.h but I haven't looked yet - just wanted to point it out. gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/pkg/include -I../../test-suite/standalone -I../.. -I../.. -I/usr/pkg/include -pthread -g -O2 -Wall -Wmissing-prototypes

buidl failure on master

My autobuild (NetBSD/amd64) for master wedged due to some git lossage (local changes interfering with git pull). I recovered that and it's now failing: cat alist.doc arbiters.doc async.doc backtrace.doc boolean.doc chars.doc continuations.doc debug.doc deprecation.doc deprecated.doc

Re: buidl failure on master

Andy Wingo wi...@pobox.com writes: I think I've fixed this -- at least it works now on OSX 10.5. Can you give it another roll? Builds fine and passes gmake check - thanks. (Plus, it probably won't work with crossbuilding, but even if that's fixed native builds still need to use the

Re: master build failure on netbsd

Andy Wingo wi...@pobox.com writes: Hi, On Thu 02 Apr 2009 05:05, Greg Troxel g...@ir.bbn.com writes: debug.c: In function 'init_stack_limit': debug.c:532: warning: comparison is always false due to limited range of data type debug.c:535: warning: comparison is always false due

master build failure on netbsd

my autobuild failed this morning: /bin/ksh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.. -I.. -I../lib -I../lib -I/usr/pkg/include -I/usr/pkg/include -pthread -Wall -Wmissing-prototypes -Werror -g -O2 -MT libguile_la-debug.lo -MD -MP -MF .deps/libguile_la-debug.Tpo -c -o

Re: vm merged to master

My autobuild failed this morning (1000Z) during the build phase: http://autobuild.josefsson.org/guile/log-200903140604763094000.txt It had previously been failing in make check: http://autobuild.josefsson.org/guile/log-200903130603258959000.txt pgpcq1xhCqM3J.pgp Description: PGP

Re: pthread crash on master

[2. application/octet-stream; 0001-Don-t-try-to-unlock-already-unlocked-heap-mutex.patch]... With that patch, make check runs successfully. log at http://autobuild.josefsson.org/guile/log-200901161104820417000.txt thanks for the fix. pgptHd2B37bCL.pgp Description: PGP signature

pthread crash on master

(Thansk - now I can build master and branch-release_18.) 1.8 passes make check. master fails with a core dump due to mutex abuse in the socket test: http://autobuild.josefsson.org/guile/log-200901151131125464000.txt here is a backtrace of the thread that crashed (gdb) i thr 4 process

Re: git head fails to build

Neil Jerram neiljer...@googlemail.com writes: 2009/1/15 Greg Troxel g...@ir.bbn.com: AB_INIT is not present in master, just in 1.8 (I think - I am still a git newbie). It's hidden somewhere inside gl_INIT or gl_EARLY. hmm, that seems wrong for a library component to be making those sorts

Re: git head fails to build

It does a git pull, adds autobuild stuff, and then builds and mails to the server: http://autobuild.josefsson.org/guile/ but I can reproduce this with autoconf -I m4 The issue seems to be that gl_LOCALCHARSET is used but not defined. Also, autogen.sh is awkward on NetBSD because traditional

Re: git head fails to build

Here's the build-guile script, which I got from someone on this list build-guile.sh Description: Bourne shell script pgpgoc2V8j3RW.pgp Description: PGP signature

Re: git head fails to build

(has anyone else built head of git?) Now I get: list gdt 3 ~/BUILD-GUILE-1.9.0 ./build-guile.sh remote: Counting objects: 8, done. remote: Compressing objects: 100% (5/5), done. remote: Total 5 (delta 3), reused 0 (delta 0) Unpacking objects: 100% (5/5), done. From git://git.sv.gnu.org/guile

Re: is guile thought to work on Mac OS X???

Neil Jerram neiljer...@googlemail.com writes: 2009/1/10 Greg Troxel g...@ir.bbn.com: is load-extension expected to deal with this, and perhaps the problem is a stray .so in a call that shouldn't be there? I would guess that it is libltdl's job to know that the correct suffix on MacOS

is guile thought to work on Mac OS X???

I am the maintainer of the guile package in pkgsrc. I have a Mac OS X 10.5.6 (i386) machine, and I have built and installed guile 1.8.6 from pkgsrc. guile itself runs ok, but when I do (use-modules (ice-9 readline)) I get a complaint about not being able to open libguilereadline-v-17.so which

unlocking unlocked mutex

I resurrected the box that does autobuilds of guile 1.8 and head on NetBSD/amd64. 1.8 is ok, and on 1.9 it fails with unlocking unlocked mutex (NetBSD pthread is very strict). I'll try to look further, but here's the log:n http://autobuild.josefsson.org/guile/log-200901101543078091000.txt

Re: Plan for 2.0

We're clearly moving towards a 2.0 release. Here is my attempt to pull that together a bit and flesh out what needs to be done. That seems like a good plan on all counts, plus perhaps period of feature freeze on master, with testing on many OS and architecture variants, with a special

Re: interactive problem in build?

l...@gnu.org (Ludovic Courtès) writes: Hi Greg, Greg Troxel g...@ir.bbn.com writes: This works fine (module packages not building), except for guile. With guile (1.8 series has done this, not sure about earlier), the process group stops due to tty output. Foregrounding the job for a few

1.8.6 on NetBSD

I updated pkgsrc to 1.8.6 and it passed make check on NetBSD/i386 currentish. pgpKzgjAgnxAy.pgp Description: PGP signature

Re: Guile release planning

Any ideas for binary compatibility for the micro revisions? I recently discovered that a library compiled against 1.8.3 would core dump when used with an application compiled against 1.8.5. Operationally, not a big deal, really; I just recompiled the lib, but emotionally, it did give

Re: Stack calibration

Neil Jerram [EMAIL PROTECTED] writes: On 10/10/2008, Greg Troxel [EMAIL PROTECTED] wrote: I am not really following, but does this make it harder to cross-compile guile than it is now? I don't think so. In the Guile build, 'make' already executes the built guile in order to generate

Re: RFD: drop the GH interface.

Bruce Korb [EMAIL PROTECTED] writes: From a Guile-user and not developer perspective, the sequence needs to be: 1. the most retrograde platform must have all the GH capabilities in the SCM interfaces for their releases. It seems to take quite a few years for BSD to get around to

Re: _GNU_SOURCE redundant define

Greg Troxel [EMAIL PROTECTED] writes: On NetBSD-current/amd64, the branch_release-1-8 branch fails to build. _GNU_SOURCE is defined in config.h, and also in two files. With the following change, it builds and 'gmake check' succeeds. I have figured this out. With autoconf 2.62 on NetBSD

_GNU_SOURCE redundant define

On NetBSD-current/amd64, the branch_release-1-8 branch fails to build. _GNU_SOURCE is defined in config.h, and also in two files. With the following change, it builds and 'gmake check' succeeds. I'm not sure why _GNU_SOURCE is there; it seems guile should be mostly relying on POSIX-specified

Re: Guile FTBFS on hppa - problem in detecting stack direction?

Bernhard R. Link [EMAIL PROTECTED] writes: * Carlos O'Donell [EMAIL PROTECTED] [080807 03:41]: Just because something is part of some ABI is no reason to not try to autodetect it. It's an elementary philisophical idea behind autoconf (and one of its biggest advantages in my POV) that you do

Re: Pace is nothing without guile

My immediate reaction is that test suites aren't good benchmarks because we will often want to add to test suites, while changing the benchmark invalidates previous data so we will not want to change the benchmark. Now, if you mean to use the test suite as a collection of micro-benchmarks, so

Re: math tests on amd64

Neil Jerram [EMAIL PROTECTED] writes: guile (version) 1.8.5 guile (eqv? 0.0 (exp -inf.0)) #f guile (exp -inf.0) +nan.0 On i386 and sparc64 this passes. I ran paranoia and that passed (with not even flaws). Does this test pass for others on other operating systems on amd64?

Re: how does one debug a SEGV in scm_threads_prehistory?

Bruce Korb [EMAIL PROTECTED] writes: It depends on which Linux: SuSE is x86_64 and Debian amd64. Unclear why the first name needed to be rethought. Whatever. Thanks - I don't know why NetBSD chose amd64 either. Can you trigger this with a simple example? I have i386 and now amd64 boxes,

Re: guile-1.8.4 build failed on Leopard.

I intend to get around to fixing guile building from pkgsrc on mac os x, but have not. Someone in my group when working on amanda I think found that 10.5 libtool was messed up. So you might try pkgsrc (at pkgsrc.org) and build guile and see what happens - I suspect it builds libtool from pkgsrc

Re: The Big Switch to Git

From: [EMAIL PROTECTED] (Ludovic Courtès) That sounds ok. I think not having bidirectional gateways is the right call. I would be tempted to transfer the other modules; the plan you stated leaves some things in cvs and some not, and you want to disable writes to cvs after the cutover. It

Re: guile-config link reports LDFLAGS it has been compiled with

Wait, no: the argument for `$CPPFLAGS' also applies to `$LDFLAGS'. That is, if `-L' flags are passed through `$LDFLAGS' to `configure', like `-L/path/to/gmp', then they must be reported by guile-config link. Admittedly, it has the undesirable side-effect of reporting completely

Re: Pkgsrc patches

[EMAIL PROTECTED] (Ludovic Courtès) writes: Hi, Aleksej Saushev [EMAIL PROTECTED] writes: Also I want to point, that pkgsrc provides patches for Guile and related packages, see here, for instance: http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/lang/guile/patches/ It would be great if Greg

Re: Pkgsrc patches: patch-ae

This just adds defines for more platforms, plus fixes a comment typo. $NetBSD: patch-ae,v 1.13 2007/07/20 00:09:22 gdt Exp $ support for NetBSD/alpha, NetBSD/sparc64, and NetBSD/x86_64 --- libguile/gc_os_dep.c.orig 2007-05-09 16:22:03.0 -0400 +++ libguile/gc_os_dep.c @@ -110,6 +110,11

Re: Pkgsrc patches: patch-aj

I am not 100% clear on this one, but I think the basic issue is that the code was defining errno always, and that could lose depending on whether it matched the system definition. Perhaps we need HAVE_ERRNO_H, but in general I'm in favor of checking for C99/etc. and trying that, and only if not

Re: Pkgsrc patches

OK, I've sent all 5 pkgsrc patches, of which I think 4 should probably be applied. Please feel free to ask about any of them, although I'll point out that I'm not the originator of some of these. In addition to the patches, pkgsrc bashes the slib support, and avoids the rpath addition on Darwin.

  1   2   >