Summary: | dev-lang/mono-4.0.3.20 : /.../libtool: No such file or directory | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | dotnet project <dotnet> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
dev-lang:mono-4.0.3.20:20150930-195053.log.bz2
emerge-history.txt |
Description
Toralf Förster
2015-09-30 20:16:29 UTC
Created attachment 413390 [details]
dev-lang:mono-4.0.3.20:20150930-195053.log.bz2
Created attachment 413392 [details]
emerge-history.txt
The warning in the snippet is just incorrect use of certain autoconf/libtool constructs on upstream side, but likely irrelevant. The content of the log hints strongly towards a parallel make problem. (In reply to Rafał Mużyło from comment #3) > The content of the log hints strongly towards a parallel make problem. Hhm, the tinderbox runs -j1 usually. (In reply to Toralf Förster from comment #4) > (In reply to Rafał Mużyło from comment #3) > > > The content of the log hints strongly towards a parallel make problem. > Hhm, the tinderbox runs -j1 usually. Sorry, missed that. Though, '--disable-silent-rules' doesn't seem enough - in at least one place, the build system explicitly checks for V=1. Also, it seems that this version of mono bootstraps, so it requires an existing mono installation - that's my reading of the README file anyway (and some of the commits to that file seem to confirm that). PS: Isn't 'rm -f' a command that *can't* fail unless rm isn't present ? looks solved in 4.4.1.0 |