Summary: | app-backup/amanda fails tests | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | New packages | Assignee: | Robin Johnson <robbat2> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dustin, lists |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Build log |
Description
Diego Elio Pettenò (RETIRED)
2009-12-12 14:27:23 UTC
Created attachment 212790 [details]
Build log
Cool, Amanda got tinderboxed! The error is occuring while syntax-checking amcheckdump.pl. Unfortunately, perl's -c flag does a bit more than "syntax check", so it ends up loading extension modules. ERROR:glib-util.c:48:glib_init: assertion failed: (!g_thread_supported()) This is a check that glib's threads haven't been initialized before libcurl is initialized. This function is the only place threads are initialized, and it's protected against multiple invocations (without a mutex, but it's invoked before threads are started, so that should be OK). I'm using dev-libs/glib-2.20.5-r1, and not seeing this error. Our buildbots build against a lot of other linux distros, and also haven't generated this particular error. Is there something peculiar about this build environment that might cause this problem? I'm kind of grasping at straws here. Ah, I figured it out. The perl syntax checks use a hack to get perl to load the appropriate shared objects. The build directory really isn't set up the way perl expects, so this doesn't work too well. I'm seeing similar errors on my system now, and I think the reason is that the emerging Amanda is testing itself against the installed perl libraries, with predictably disastrous results. I would suggest configuring with --disable-syntax-checks, which will disable this particular hack, but not the other checks accessible from 'make check'. I'll admit that's relatively few checks. Unfortunately, Amanda is very hard to test before it is installed, due to some fundamental design assumptions. While I'm on the topic, please do *not* run the installchecks as part of the ebuild process, as they *will* stomp on user data. Hopefully the required CLOBBER_MY_CONFIG=OK environment variable already made this obvious :) Mostly resolved in 3.1.2. Pending glib issue on bug 331111. |