<ngz>Hello. I have a package that complains about "ld: cannot find -lglew" at the end of the compilation process (CMake build system). I added glew to the input to no avail. Is there a common workaround for that issue?
<cbaines>At least with my upgrade SSD, my system comes back to life after the python package build kills it :/
<cbaines>I think before I managed to kill the tests during the package build... but I'm struggling to replicate the same feat without htop, which I can't build without python :(
<civodul>cbaines: great that it worked! that was a nasty bug...
<civodul>cbaines: re python, do you take substitutes from berlin.guixsd.org?
<civodul>ngz: i'd check in the 'environment-variables' file whether glew really is in $LIBRARY_PATH
<apteryx>Nov 11 20:41:09 localhost dhclient: No DHCPOFFERS received --> followed by --> Nov 11 20:41:09 localhost dhclient: No working leases in persistent database - sleeping. --> then my network cuts.
<apteryx>My AP is configured to act as a DHCP server, and until the last message from dhclient my connectivity is working (I have an IP).
<apteryx>somehow now managed to get: Nov 11 20:41:49 localhost dhclient: bound to 192.168.1.111 -- renewal in 2147483648 seconds.
<apteryx>I should be good for a while although I'd like to understand this erratic behaviour...
<apteryx>nope... Nov 11 20:46:12 localhost dhclient: DHCPDISCOVER on wlp18s0 to 255.255.255.255 port 67 interval 3
<snape>The output of 'guix refresh --list-dependent postgresql' is "Building the following 267 packages would ensure 501 dependent packages are rebuilt" -> what is the number of dependent packages, 267 or 501?
<snape>maybe the 267 packages are the direct dependencies (those that explicity have postgresql as input) and the other one are induced
<snape>Hmm that doesn't make sense (there are very few packages with postgres as direct input)
<g_bor>rekado: Actually there is an ambiguity in the text I see.
<g_bor>It is this The deadline for selecting an intern is Nov. 12, 2018 at 4pm UTC. Once mentors select their interns, the community coordinator will need to assign funding sources. The Outreachy organizers will then approve the intern selection and funding source.
<g_bor>So, it is possible that you will only see that only after this deadline is passed.
<g_bor>If this is the case, then I can send a report and propose a clearer text. WDYT?
<g_bor>(i.e. it is not clear that coordinators see the founding allocation only after this deadline, and it is also not clear what deadline applies to allocating founding)
<g_bor>ok, I've found this: Deadline Nov. 12, 2018: Coordinators decide which interns will be funded from the available sponsorship funds, and which interns won't be funded. If the organization wants to accept more interns than they have sponsorship funds, the coordinator can mark the intern asking for Outreachy general funds. This community has sponsors who will fund up to 1 interns.
<roptat>hi civodul. I'll be able to come for the guix meetup before r-b summit, but I won't be able to attend the summit itself because I took too much time to think about it
<rekado>I have a user ask about libc++ for use with clang. Our “make-libstdc++” procedure only works with GCC. Does anyone know more about clang/llvm to tell me how clang + clang-runtime + llvm are supposed to be used with libc++?
<snape>Hi, I have cache issues. I need to rm /var/guix/substitue/cache every time I build something, otherwise guix doesn't fetch substitutes. And it seems that 'guix package -m manifest.scm' messes up with the cache.
<snape>Could someone give me a hint on how to troubleshoot it?
<snape>civodul, rekado: for some reason guix-modular evaluations fail on Berlin. (And they succeed on my machine...)
<rekado>snape: civodul wrote yesterday that this seems to be a hook failure, not an actual build failure.
<apteryx>rekado: congrats for the successful deployments of new disk arrays :)
<rekado>apteryx: thanks, I hope it’ll last. We’ll need to make a few changes to Guix to make this setup a little easier to maintain.
<mbakke>rekado: Commit a7e231a2a3edbd6a70949432c1ff434d87f625ff broke a lot of Haskell packages on core-updates.
<rekado>hmm, this means that a lot of packages previously passed the build by accident, no?
<rekado>civodul: do you plan to have dinner together on Dec 10? I’m looking for a bus connection to/from Berlin and the last bus back to Berlin is at 7:35pm.
<mbakke>rekado: I don't think so, the error is about missing dependencies, but it does not show up when reverting the commit.
<civodul>mbakke: guix.sjd.se seems to have enough space available
<rekado>mbakke: no, I don’t see how there could be a race. A “configure” script only exists in some packages. Or do you mean that “ghc-pkg --package-db=… recache” might not be finished by the time the “configure” phase starts?
<roptat>speaking of which, I think some build systems still use (zero? (system* ...))
<lfam>Hm, with the new Go 1.11 build system, Syncthing failed its tests the first time, but succeeded on the second run. The test was 'github.com/syncthing/syncthing/lib/model' and the successful run took ~42 seconds (!)