IRC channel logs
2014-05-19.log
back to list of logs
<zerwas>civodul, do you care for a patch for GNUnet 0.10.1? <zerwas>Unfortunately I can't compile anything for more than 2 minutes because my computer will overheat and shut down ... <civodul>and report the bugs for you to solve :-) <civodul>zerwas: i fail to apply the patch; could you rebase it on master? <phant0mas>okay I have glibc/hurd and glibc/hurd headers packages, the second inherits from the first <phant0mas>I need to pass a flag to configure that points to an output folder that only exists in the glibc recipe but not in the headers one <phant0mas>Is there a way to only pass the flag when the folder is present? <phant0mas>civodul: I repeat the question from yesterday :P <phant0mas>right now if I use (assoc-ref %outputs "locales") , I get an error at the glibc headers, because it inherits the config flags from glibc but I don't have that output folder there <civodul>phant0mas: i guess "glibc-headers" doesn't have a "locales" outputs <civodul>if you look at its 'outputs' field, right? <phant0mas>it doesn't have because I am the one that removed it :P <civodul>ok, that's why (assoc-ref %outputs "locales") returns #f <phant0mas>but I need the folder to install the glibc locales from the glibc package <civodul>for "glibc", not for "glibc-headers" <civodul>it doesn't make sense for "glibc-headers" to install anything other than the headers <civodul>so it should have just one output, the default one <phant0mas>I see what you mean, but the problem is, I need to pass this flag (string-append "--localedir=" (assoc-ref %outputs "locales") <phant0mas>and glibc headers inherit the config phase from glibc <phant0mas>can I somehow remove this specific flag when it's configuring the headers? <civodul>ok, so you need to somehow get rid of that flag in glibc-headers <civodul>ideally, instead of inheriting all of glibc's 'arguments' field, you could start with an empty fiel <civodul>otherwise, you can use substitute-keyword-arguments to do finer things <civodul>phant0mas: if that ends up being tricky, we can discuss this on the list <civodul>hopefully i can help you better than while chatting ;-) <bavier>is the value returned by time() different during a package build? <bavier>just trying to track down a test failure when building mu <civodul>could be related to timezone info, no? <bavier>yes, it tries to check message queries in some different timezones <bavier>by resetting the TZ environment variable <civodul>then you probably need to add 'tzdata' to the inputs, and set TZDIR to point to $tzdata/share/zoneinfo