Summary: | dev-util/gtk-doc-am-1.13 fails tests: tester-undocumented.txt: No such file or directory | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dustin Polke <DuPol> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build.log
build.log |
Description
Dustin Polke
2010-04-19 10:36:39 UTC
Created attachment 228367 [details]
build.log
Please try building it with MAKEOPTS="-j1". I am unable to reproduce the problem here :-| (In reply to comment #2) > Please try building it with MAKEOPTS="-j1". I am unable to reproduce the > problem here :-| Investigated this further and it seems that something was broken on my box. Tests failed with MAKEOPTS="-j1" as well. Executing manually "./configure" in ${S} and then "make check" resulted in tests finishing okay. So I decided to upgrade with FEATURES="-test" and then reinstall with tests enabled. Now everything works as expected. Thus closing INVALID. Reproduced this morning in one of my machines. Maybe this problem only occurs when updating from older gtk-doc-am... Created attachment 230561 [details]
build.log
I don't see much sense on running tests for gtk-doc-am when that ebuild doesn't even compile anything. I would restrict them (dev-util/gtk-doc should be enough I think) What does the rest of the team think? Restricting tests sounds good to me. Cheers Just done Thanks |