IRC channel logs

***vicenteH` is now known as vicenteH

***haroldwu_ is now known as haroldwu

<bhattigurjot>is there a deb package for guile-2.0.11?

<mark_weaver>not yet, but rlb is working on it

<mark_weaver>but it will probably take a while to propagate from there to mint

<bhattigurjot>ok and 2.0.10 or 2.0.9?

<mark_weaver>2.0.9 is widely available as debian packages

<mark_weaver>2.0.10 was released just a couple of days before 2.0.11, and had a serious bug.

<mark_weaver>so 2.0.10 shouldn't be used

<civodul>Hello Guilers!

<wingo>moin

<aidalgol>evenin'

<bhattigurjot>hi

<bhattigurjot>mark_weaver: Hi, the PKG_CONFIG_PATH didn't work, I set it to "/usr/include/guile/2.0/" and even tried "/usr/lib/pkgconfig/", but no luck. So included the library as an option to configure, like "./configure --includedir=/usr/include/guile/2.0/"

<bhattigurjot>and it worked

<bhattigurjot>is it right or just a work around?

<bhattigurjot>oops! --includedir=/usr/local/include/guile/2.0/

<mark_weaver>you shouldn't need that.

<mark_weaver>the GUILE_FLAGS macro should set GUILE_CFLAGS to something that includes the relevant -I flag.

<mark_weaver>and the dr-geo build system should use that in the appropriate place(s).

<mark_weaver>anyway, if you need PKG_CONFIG_PATH, it should be /usr/local/lib/pkgconfig

<mark_weaver>all the details of what ./configure did should be in config.log. you should be able to see what GUILE_CFLAGS was set to there.

<mark_weaver>bhattigurjot: ^^

<bhattigurjot>mark_weaver: "GUILE_CFLAGS='-pthread -I/usr/local/include/guile/2.0'" see it already sets to the correct position but I'm still getting the make error. :/

<mark_weaver>then that flag is not getting where it needs to be.

<mark_weaver>it doesn't magically happen. GUILE_CFLAGS is not automatically added to the compile flags of everything.

<mark_weaver>but at least we know that GUILE_FLAGS is doing its job.

*mark_weaver goes afk for a bit

<bhattigurjot>yeah

<bhattigurjot>the Makefile.am file does include this GUILE_CFLAGS in it.

<bhattigurjot>but also I can see that during 'make' command, this GUILE_CFLAGS path is not included and rest all are shown.. wonder why?

<mark_weaver>you need to run 'autoreconf' to update Makefile.in from Makefile.am, and then ./configure to update Makefile from Makefile.in

<bhattigurjot>no change I'm afraid

<davexunit>is it okay to have an add-hook! call at the top-level of a module?

<davexunit>my feeling is that any side-effect at the top-level of a module is probably a bad thing.

<civodul>davexunit: same feeling for me :-)

<davexunit>civodul: guile-2d does some bad things in that regard that I'm trying to fix.

<davexunit>but it's difficult when I want to have variables like mouse-x that always contain the mouse x coordinate.

<davexunit>and in my case, it's a "signal" variable that receives updates from a hook.

<davexunit>but it appears I was right to be dubious of adding hooks when a module is imported. need to figure out a better solution.

***ijp is now known as notijp

***notijp is now known as ijp

***jao is now known as Guest40294

***Guest40294 is now known as jao

<dsmith-work>hey hey

***ngz` is now known as ngz

***ft_ is now known as ft

***_zxq9_ is now known as zxq9

IRC channel logs

2014-04-07.log