<davidh`>how can i tell autoconf to use the system guile, not that in my $HOME? ***davidh` is now known as davidh
<davidh>ft: shouldn't pkg-config figure out the right thing? <davidh>that's how i run configure PKG_CONFIG_PATH="" ./configure <davidh>it actually says it found "2.0" and in my $HOME is devel <davidh>so i suspect it's some pkg config stuff that finds the wrong binary <ft>I don't know. I may have answered to quickly without knowing the complete problem. ☺ <davidh>but as i wrote configure.ac it's very likely that the error sits in front of the screen. Is it problematic to have stable and devel installed? <ft>I don't think it should be a problem since everything is kept pretty separate. But then, I don't how then autoconf integration works. <madsy>davidh: Native build or cross-compiling? <madsy>pkg-config should work with no problems for native builds. When cross-compiling however, you need pkg-config for that toolchain, not the native pkg-config <madsy>Or else pkg-config returns paths for a different toolchain <madsy>davidh: Also, if you built the dependencies yourself, the .pc and .la files might contain incomplete information <madsy>Built without thread support, for now <neiljerram>Just looking at my FOSDEM planning, and wondering if Guile stuff is going on on Sunday as well as Saturday? <neiljerram>Saturday is unfortunately starting to look difficult for me... <civodul>neiljerram: the schedule for sessions is pretty much set in stone now <civodul>it might be possible to move your talk, but only within that slot that we have <neiljerram>Well something that I can't miss (at my son's school) has been announced for the Friday evening, and I'm also presenting (in a different dev room) mid Sunday. So I'm quite strongly inclined now to come on Sunday only. <wingo>it would be too bad if you weren't able to present! if you can't make it though, someone can fill it ***profan_ is now known as profan
<civodul>neiljerram: please email Pjotr to let him know <civodul>someone else may have to fill the slot, indeed <civodul>BTW wingo, you didn't submit a talk, did you? <wingo>civodul: i didn't, ran out of time. i'd be happy to fill in if needed tho <neiljerram>Thanks ludo and andy; I'm sorry to let you down on this. But I will email Pjotr, and I will also be around on Sunday afternoon in case any Guilers are still there then. <civodul>wingo: cool, let's do that if neiljerram cannot make it <sirgazil>Hi :) Do you know any library to do desktop notification? <sirgazil>Maybe GNOME-Guile has something for GNOME's libnotify? I can't seem to find anything... <neiljerram>Seems sirgazil has gone, but I couldn't resist knocking up his/her request using the FFI... <neiljerram>(notify-notification-show (notify-notification-new (string->pointer "Hello!") <daviid>neiljerram: cool. do you have this code as a module somewhere? <madsy>Would be nice if someone not on Ubuntu or Debian could test it <mark_weaver>thanks neiljerram! alas, sirgazil is no longer on channel <mark_weaver>sirgazil is the creator of the new guile and guix web sites, by the way. <neiljerram>Ah, OK, I didn't know that. I could drop that into an email, then :-) <daviid>neiljerram: notify-init should go in a eval-when expr imo <madsy>mark_weaver: I managed to make Guile truly freestanding on Windows. That is, it can be put anywhere <madsy>I'm not sure it is patches that would benefit the general build system really. <madsy>I patched libguile/Makefile.in to tell libtool to link guile.exe with -all-static <madsy>And when starting Guile on Windows, it is done with a batch script which temporarily sets up the load paths correctly, agnostic to the actual directory tree <madsy>Basically by finding the installation "root" <madsy>mark_weaver: Still only got 2.0.9 and 2.0.11 working though. Some bug introduced in 2.1.0 breaks builds without <sys/mman.h> <daviid>neiljerram: cool, just played with your code. I wonder what would be the best way to check that there is a desktop and it is libnotify compat ? <wingo>that sounds like what guix does <madsy>wingo: Thanks for the link to make-bootstrap.scm yesterday. That gave me some insights <ArneBab_>madsy: can you test whether what I build for Windows actually runs on Windows? <madsy>ArneBab_: Yes, that's no problem :) <madsy>Or you could just use my script and do it yourself <madsy>ArneBab_: I can find the exact versions of the tools and library dependencies I've used, if that helps <madsy>Or, if you can already successfully build guile for gentoo, then my script doesn't require anything else <ArneBab_>madsy: I get libtool: compile: unrecognized option `-DPACKAGE_VERSION_STRING=\\"1.14\\"' <madsy>Hm.. what's your libtool version? <madsy>And automake and autoconfig versions <madsy>ArneBab_: Uh.. silly question, but have you actually installed MinGW-w64? <madsy>And did ./configure find its binaries? Check config.log <ArneBab_>I first just ran the script to see whether it would work with what I already had installed <madsy>Remember to erase the ./builds and ./binaries directories before retrying <madsy>Or the subdirectory for the tag/commit under those directories <madsy>When building with MinGW-w64 you might run into an issue with building libiconv though, which has to do with threading. <madsy>Does not happen here on my Ubuntu laptop, but does happen on Debian <wingo>ACTION tries to golf down compilation time <ArneBab_>madsy: I have to look into Gentoo crossdev… <madsy>wingo: Yeah, I saw your commit yesterday. It would be amazing if you can shave some minutes off :) <ArneBab_>for that (there’s a warning to use that instead of installing mingw directly) <madsy>ArneBab_: Hm? I don't follow. <madsy>A warning when installing MinGW-w64? <madsy>Yeah, I'm too old for using gentoo <madsy>Don't have time to optimize my calculator GUI app with -O3 -fomit-frame-pointers anymore <ArneBab_>madsy: it seems to be just crossdev -t mingw64 <ArneBab_>madsy: I tried using other distros. I always came back because I broke everything else… <madsy>By the way, I have not tested 64-bit builds yet <ArneBab_>madsy: few distros make it easy to say “everything stable, but cutting edge KDE” <madsy>ArneBab_: If you wait around 20-30 minutes, I have a new commit done <madsy>I'm stupid, and I forgot to let users override the toolchain prefix in the script <madsy>I.e it won't work unless your MinGW executable prefix is i686-w64-mingw32- <ArneBab_>crossdev started a stage1 build — I might have to delay this (will compile GCC at least 3 times) <madsy>Off-topic, but is Guix support for other platforms planned in the future? <ArneBab_>madsy: I’ll have to delay till in a few days — I need to shut down the computer for the night