ekohl / samba4

Gentoo overlay with samba4 (related) ebuilds
5 stars 2 forks source link

tevent breaking 4.9999 config #7

Closed neclimdul closed 12 years ago

neclimdul commented 12 years ago

Not really sure what to say on this one. Started a build last night to see where things stood and got this rather odd error.

ekohl commented 12 years ago

It sounds like you compiled USE="-python" tevent, but at least in my repo that is no optional USE-flag. Perhaps tevent is compiled for the wrong python version like 2.6 while samba is trying to compile with 2.7? I'd try re-merging tevent and then samba.

neclimdul commented 12 years ago

Tried recompiling several times. Haven't been able to get past this config check yet.

vladonv commented 12 years ago

tevent build with python - bad result. perhaps wrong search path module pytevent?

Checking for HAVE_WARN_UNUSED_RESULT : ok
Checking for system talloc >= 2.0.7 : yes Checking for system pytalloc-util >= 2.0.7 : yes Checking for stylesheet http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl : ok Checking for program python : /usr/bin/python Checking for Python version >= 2.4.2 : ok 2.7.2 Checking for python headers : using cache Checking linker accepts -Wl,-no-undefined : yes Checking linker accepts ['-undefined', 'dynamic_lookup'] : no Checking for system tevent >= 0.9.14 : yes ERROR: Python module pytevent of version 0.9.14 not found, and bundling disabled

ekohl commented 12 years ago

I had some time to try and was able to reproduce. The samba git version requires a git version of tevent. I'll see if I can switch samba-4.9999 to use the bundled tevent instead.

neclimdul commented 12 years ago

@ekohl Thanks for that! Very misleading error, that explains why I wasn't getting anywhere debugging it.

ekohl commented 12 years ago

I just pushed 37186260f3f55a4ab766c6dfbf9038cd1f840358 so it uses the system tevent (and ldb because tevent requires it). This fixes it for me.

neclimdul commented 12 years ago

This bug definitely seems fixed. Getting a different error now but while linking so will investigate and if needed open a new issue. Thanks!