Summary: | mono-1.0.1-r1 fails to emerge | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Pantelis Panayiotou <oss> |
Component: | [OLD] Development | Assignee: | dotnet project <dotnet> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2004.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Pantelis Panayiotou
2004-08-18 05:43:19 UTC
Ugh. Okay, this should have bailed. If using NPTL, you should use the new 1.0.1-r2, which is package.masked. I'll look into why you weren't given the appropriate error messages and information regarding this. Okay, i've just added a better check for NPTL, so when you sync, trying to emerge 1.0.1-r1 should give you an informative message telling you to use the package.masked 1.0.1-r2 version of mono. Please test that if you can before trying -r2. Nope, the new error message does not appear, and emerge still fails: # emerge sync # emerge mono ... make[1]: Leaving directory `/var/tmp/portage/mono-1.0.1-r1/work/mono-1.0.1' make: *** [all] Error 2 !!! ERROR: dev-dotnet/mono-1.0.1-r1 failed. !!! Function src_compile, Line 40, Exitcode 2 !!! MONO compilation failure The same happens even when I do: # USE="-nptl" emerge mono It may not have hit your rsync mirror yet. Check the date of the top changelog entry for mono, make sure it shows my latest addition. If not, wait for a while, sync, and try again. If it is there.. well.. sh*t. cause it should die the second it finds the 'nptl' USE flag. Okay, turns out the configure script was trying really hard to screw things up, and was setting tls to __thread, even though NPTL wasn't there. I just commited a fix for this, so try waiting a bit longer and try then. *sigh* Seems to work fine now. Thanks ;-) |