Re: Logo baseline
Hello, Arne Babenhauserheide skribis: > Ludovic Courtès writes: >> Like I wrote, Guile remains an extension language, no argument here. >> >> However, describing it as “just” an extension language seems odd to me. >> It doesn’t take into account what many have been doing with Guile, and >> it doesn’t match the efforts that have gone into Guile since 2.0. > > I don’t think that it is described as "just" an extension language. The > website makes it very clear that Guile is also a viable application > language. > > Where do you get the impression that Guile is described as "just" an > extension language? This thread is about the logo baseline, which is: “GNU extension language”. I agree that the web site is clearer; I’m just talking about the logo here. >>> Actually I’d love to see Guile become better at this: to make it easier >>> to deploy an application that uses Guile in a statically compiled >>> binary. >>> >>> Basically to generalize what LilyPond is doing. >> >> In what ways could it become “better” for this use case? > > Currently the default way to embed assumes that Guile is provided as a > shared library. But that can be problematic when you want to ship a > binary people can test easily. I think this is no different for Guile than for any other piece of software: some would ship a Docker image, and I’d argue that you can use ‘guix pack’ to generate a minimal standalone tarball or Docker image. (Though I think it’s also perfectly doable to provide a binary that’s statically-linked against libguile.) Thanks, Ludo’.
Re: Segfault while building on 64-bit Cygwin
Yes, gladly, but I don't know how to get one in this context. Do I need to add some flags to the Makefile, and if so, where? (It's a twisty maze of passages, all different.) . Note that this *is* a build with JIT enabled; when I disable it using the env variable, there are no errors and 3.0.0 works fine. Also, it may take some time, as I have to rebuild my Windows system.
Segfault while building on 64-bit Cygwin
Hi John, John Cowan skribis: > Guile 2.9.9, like .8 and .7, does not build on Cygwin (64 bit). Configure > runs without error, but make crashes with this (truncated to just the tail): > > Making all in bootstrap > make[2]: Entering directory > '/cygdrive/c/Users/rr828893/Downloads/guile-2.9.9/bootstrap' > BOOTSTRAP GUILEC ice-9/eval.go > BOOTSTRAP GUILEC ice-9/psyntax-pp.go > BOOTSTRAP GUILEC language/cps/intmap.go > BOOTSTRAP GUILEC language/cps/intset.go > BOOTSTRAP GUILEC language/cps/graphs.go > BOOTSTRAP GUILEC ice-9/vlist.go > BOOTSTRAP GUILEC srfi/srfi-1.go > /bin/sh: line 6: 4294 Segmentation fault (core dumped) > GUILE_AUTO_COMPILE=0 ../meta/build-env guild compile > --target="x86_64-unknown-cygwin" -O1 -Oresolve-primitives -L > "/home/rr828893/Downloads/guile-2.9.9/module" -L > "/home/rr828893/Downloads/guile-2.9.9/guile-readline" -o "srfi/srfi-1.go" > "../module/srfi/srfi-1.scm" > make[2]: *** [Makefile:1930: srfi/srfi-1.go] Error 139 > make[2]: Leaving directory > '/cygdrive/c/Users/rr828893/Downloads/guile-2.9.9/bootstrap' > make[1]: *** [Makefile:1849: all-recursive] Error 1 > make[1]: Leaving directory > '/cygdrive/c/Users/rr828893/Downloads/guile-2.9.9' > make: *** [Makefile:1735: all] Error 2 Could you try building 3.0.0 with JIT enabled and grab a backtrace? Thanks in advance! Ludo’.
