IRC channel logs

<mra>quick question about haunt's blog builder. does the prefix argument not apply to collections? i set #:prefix to "blog", thinking that this would move the recent posts collection page to blog/index.html, but it didn't seem to

<mra>do i need to explicitly set that collection to something like `("blog/index.html" ...)?

<mra>ah, looked closer and it seems like yes, pardon the noise

<inv>hiya, does guile have any way to display records with all their fields automatically without manually setting a record type printer? the default way records get displayed is not exactly informative..

<inv>wait im actually dumb i didnt realize the code i was viewing actually set a custom type printer which is why it was so unhelpful.......

<muabdalaleam>Hello I am new here i want to install and build Guile from the tarball how can i do that because I didn't found that in the download manual.

<muabdalaleam>Oh never mind I found that in the INSTALL file

<muabdalaleam>Why after i ran autoreconf -vif I got this wierd error message below:

<muabdalaleam>configure.ac:39: error: possibly undefined macro: AC_ENABLE_SHARED

<muabdalaleam> If this token and others are legitimate, please use m4_pattern_allow.

<muabdalaleam> See the Autoconf documentation.

<muabdalaleam>And i didn't understood anything from Autoconf's docs so what should I do

<adhoc>what did you run?

<muabdalaleam>autoreconf -vif

<muabdalaleam>I followed "Where to get the collector" section in https://www.hboehm.info/gc/

<adhoc>ok

<adhoc>what system are you trying to install on to ?

<muabdalaleam>I was trying to install bdwgc

<adhoc>ok

<adhoc>which operating system ?

<muabdalaleam>Because guile required it

<muabdalaleam>GNU/Linux

<adhoc>yes, I just had to do that same

<adhoc>which distro ?

<muabdalaleam>Void linux

<adhoc>ah, ok

<adhoc>is there a package called soething like; libgc-dev ?

<muabdalaleam>I found gc-devel

<muabdalaleam>should i install it right?

<adhoc>what is Void Linux based on, RedHat .*?

<muabdalaleam>No it's not based on anything it's just based

<muabdalaleam>It has it's own packege maneger

<adhoc>ok, try installing it and run the ./configure again.

<adhoc>muabdalaleam: ok, I have not tried that one.

<muabdalaleam>I think it should work because it's entry in the search results was: [-] gc-devel-8.2.8_1 Garbage collector for C and C++ - development files

<adhoc>sounds about right to me.

<adhoc>Package: libgc-dev

<adhoc>Source: libgc

<adhoc>Version: 1:8.2.2-3

<Arsen>muabdalaleam: did you read HACKING?

<adhoc>sounds about right

<Arsen>I can't even see references to AC_ENABLE_SHARED

<adhoc>Arsen: i think that is in the gc library

<muabdalaleam>No when i was installing Guile I got that bdw-gc is not found

<muabdalaleam>so that error is from the bdw-gc installer

<muabdalaleam>adhoc: THANKS IT WORKED

<adhoc>most excellent!

<muabdalaleam>I really appreciate it :)

<adhoc>happy hacking =)

<muabdalaleam>I was going to shift to CHICKEN instead because it wasn't installing

<adhoc>Arsen: sounds like there are a lot more dependencies that need to go in that file =)

<Arsen>patches welcome

<adhoc>Arsen: fair call =)

<Arsen>but, if the error is in the build for bdw-gc, I don't see why it should be in HACKING

<adhoc>bdw-gc is in that doco as a dependency?

<adhoc>an, no, but instead; README: ./configure --with-bdw-gc=bdw-gc-threaded

<muabdalaleam>I didn't know that I should have the dev files for any garbage collector i thought it should be bdwgc spessifcally

<muabdalaleam>and for some reason bdw-gc didn't work for me

<Arsen>you usually need dev files when building something that uses a library

<Arsen>but you don't need them to run the thing you built

<adhoc>it has; --with-bdw-gc=bdw-gc-threaded

<adhoc>can we run --without-bdw-gc ?

<muabdalaleam>Arsen: I know but why did Guile specify bdw-gc though gc worked fine when i installed it.

<Arsen>libgc is actually the BDW gc - it has many names

<Arsen>(I know, it gets confusing..)

<adhoc>ah, the section under; Required External Packages

<adhoc>I just ran ./configure and followed my nose

<muabdalaleam>Arsen: Oh thanks so it's the problem of my distro's packege maneger

<adhoc>muabdalaleam: got to learn some how =)

<muabdalaleam>Maybe i will notify them about that

<muabdalaleam>Btw why is the compilation taking so long currently the make is showing me this: BOOTSTRAP(stage0) GUILEC language/tree-il/compile-cps.go

<identity>muabdalaleam: bootstrap can take quite some time, it should finish sooner or later

<muabdalaleam>what's bootstrap?

<muabdalaleam>Why is Guile taking too much longer in building than CHICKEN

<identity>muabdalaleam: guile is partially written in guile, so you need guile to compile guile, which is a problem when you do not have guile already, so the build proccess has to, figuratively, "pull itself up by the bootstraps", first building an interpreter in which it runs the compiler, and interpreted code is quite slow compared to compiled

<muabdalaleam>Oh thanks

<muabdalaleam>maybe i also forgot to do make -j 8

<adhoc>identity: does this hinder the process to get guile working on new platforms ?

<adhoc>i see there are a handful of platforms in prebuilt/

<adhoc>so, 32bit x86, MIPS and ARMv7 ?

<adhoc>also PowerPC

<adhoc>I wonder if that will run on my Power4+ machines?

<adhoc>"Build fixes for `powerpc-ibm-aix5.3.0.0' (AIX 5.3)"

<adhoc>sounds promising =)

<identity>adhoc: i do not think it should be a major problem, though i am only in passing familiarity with Guile's internals

<adhoc>ok

<muabdalaleam>Curios question, does guile work on RISC-V architure

<adhoc>I would like to owrite on the x86-64 machine and then push things to some very low power arm64 machines at home that are always on

<muabdalaleam>architecture*

<adhoc>"** Recognize RISC-V compilation targets in (system base target)"

<adhoc>maybe ?

<adhoc>from NEWS

<muabdalaleam>oh i didn't read that but Sick. I don't know who might need that but good to know

<adhoc>there are more embedded boards with Arm and RISC-V cores on them now.

<adhoc>and quite low power.

<adhoc>is a very attractive angle for building embedded systems,

<muabdalaleam>Why is Guile compilation still running it started 25~ mins ago

<muabdalaleam>Should i stop it and rerun it with make 0j 8

<muabdalaleam>-j *

<muabdalaleam>I reached BOOTSTRAP(stage0) GUILEC ice-9/session.go

<adhoc>yes, make -j (CPUS-1)

<adhoc>makes sense, that is what I did half and hour ago ;)

<adhoc>anyhow, night folks

<wingo>good day

<muabdalaleam>wingo: Wow you are one of the core maintainers of Guile right?

<identity>muabdalaleam: correct

<wingo>yes

<muabdalaleam>Sorry again but now after i built and installed guile why when i ran `guile` I got guile: error while loading shared libraries: libguile-3.0.so.1: cannot open shared object file: No such file or directory

<muabdalaleam>I did everything in the INSTALL manual

<muabdalaleam>only that I used sudo make install instead of make install

<muabdalaleam>When i ran make installcheck i got fatal error: libguile.h: No such file or directory

<muabdalaleam>And when i run make install I get /usr/bin/install: cannot create regular file '/usr/local/bin/guile-config': Permission denied

<Arsen>installcheck IIRC runs tests against installed guile

<Arsen>and yeah, to run make install, you usually need root perms (or a different DESTDIR)

<Arsen>but why not use the guile packaged in void?

<muabdalaleam>Arsen: Now i did that instead

<muabdalaleam>Now i am facing the older problem that I tried building to fix, Why when I am importing <guile/3.0/libguile.h> I get `in included file 'libguile/scmconfig.h' is not found`

<muabdalaleam>* Now i am using Void's guile and guile-devel

<noe>muabdalaleam, you should add the absolute path to “include/guile/3.0“ to your include path

<Arsen>you should add the result of pkg-config --cflags guile-3.0 to your cflags

<muabdalaleam>noe: wdym ?

<muabdalaleam>Arsen: Ok i will try that

<Arsen>also need pkg-config --libs guile-3.0 in your LIBS/LDFLAGS (depend on your build system)

<Arsen>meson and autoconf can do this automatically for you

<Arsen>dependency('guile-3.0') and GUILE_PKG([3.0])

<Arsen>(respectively)

<muabdalaleam>I am using GNU Make I think i should do $(pkg-config --libs guile-3.0)

<Arsen>$(shell ...) but yes

<Arsen>ACTION thinks you ought to use a more complete build system though

<muabdalaleam>Still i am getting #include "libguile/scmconfig.h" file not found when i import <guile/3.0/libguile.h>

<muabdalaleam>Here's my LDFLAGS -shared -fPIC -lglfw -lGL $(shell pkg-config --libs guile-3.0)

<muabdalaleam>Oh wait a minute

<muabdalaleam>Still the same $(TESTFLAGS) := $(CFLAGS) -lglfw -lGL -lstylo $(shell pkg-config --libs guile-3.0) result

<Arsen>don't use that header, use libguile.h directly, and make sure you also added the cflags

<Arsen>note that the cflags invocation has --cflags

<Arsen>(and, again, you'd have an easier time using meson for instance, which automatically handles this)

<muabdalaleam>Is it known that 'libguile.h' doesn't work most of the time ???

<muabdalaleam>Is this a bug or is it an internal header only

<Arsen>neither.. you just haven't included it correctly..

<Arsen>it does work correctly, always, if you included it correctly

<Arsen>as I pointed out, your CFLAGS are wrong - they should contain $(pkg-config --cflags guile-3.0)

<muabdalaleam>Arsen: THANKS it finally worked you were right i needed those flags

<muabdalaleam>Arsen: Really appreciate it :)

<Arsen>happy to help :)

<Arsen>happy hacking!

<muabdalaleam>You guys here are 10x better than asking an LLM thanks again.

<cow_2001>does it make sense to mask modules?

<cow_2001>guile has GUILE_LOAD_PATH, right? it is a list of paths, supposedly the order of module search is from the left to right, like in PATH

<cow_2001>so what if i put in my own (srfi srfi-1) module in there?

<cow_2001>or any other module that comes prepackaged with guile

<identity>cow_2001: you will load your own module, probably

<old>such is the power of the Guile modules

<old>don't like the core implementation? Role your own. But somes modules are defined in C so you can't really change them

<rlb>adhoc: guile's pretty good with respect to arch support, e.g. https://buildd.debian.org/status/package.php?p=guile%2d3%2e0

<rlb>And yes, bootstrapping can take a long time -- m68k took around 63 hours last time I think.

<rlb>:)

<rlb>Oh, but 3.0.10 is still broken on 32-bit architectures unless you add the patches Debian has cherry-picked from main.

<rlb>fwiw

<rlb>(or similar)

<sneek>Yey! dsmith is back :)

<dsmith>sneek, botsnack

<sneek>:)

<dsmith>There's a good bot

<sneek>ACTION wags

IRC channel logs

2025-06-12.log