Summary: | x11-proto/xproto-7.0.25 - .../work/xproto-7.0.25/missing: line 81: aclocal-1.14: command not found | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Brian McKee <btmckee9> |
Component: | [OLD] Library | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge --info output
build.log |
Description
Brian McKee
2014-05-28 17:23:16 UTC
Please attach the entire build log to this bug report. Created attachment 377798 [details]
build.log
Comment on attachment 377798 [details] build.log >>> Unpacking xproto-7.0.25.tar.bz2 to /var/tmp/portage/x11-proto/xproto-7.0.25/work >>> Source unpacked in /var/tmp/portage/x11-proto/xproto-7.0.25/work sed: can't read configure.in: No such file or directory >>> Preparing source in /var/tmp/portage/x11-proto/xproto-7.0.25/work/xproto-7.0.25 ... What is that sed call doing there? I'm still stuck and I've found another package with the same error. mpg123 bails with the same 'aclocal-1.14' is missing on your system. Its been a month since my last emerge, should I just bail and re-install? I worked around this by installing automake-1.14.1 by hand. tar xvzf automake-1.14.1.tar.gz ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --docdir=/usr/share/doc/automake-1.14.1 HELP2MAN=true make -j8 APIVERSION=1.14 pkgvdatadir=/usr/share/automake-1.14 make install After that, xproto built. I'm trying to emerge -DNuv @world my system now. (In reply to Brian McKee from comment #5) > I worked around this by installing automake-1.14.1 by hand. Now you can be certain you won't see any support. Its strange you would say that. I still can't emerge it. Its still broken. I can still replicate the problem. But I couldn't let my machine sit in a partially emerged state, things could go wrong if I do. Surely you understand my plight? A system that is partially built that needs emerge @preserved-rebuild is not a stable system is it? I'm here to help, just tell me what to do. In case that you've missed it: (In reply to Jeroen Roovers from comment #3) > What is that sed call doing there? Think about that and then read the entire WARNING output, there's something going on there that we don't know about yet; feel free to share /var/tmp/portage/x11-proto/xproto-7.0.25/temp/environment with us, in the case that you're unaware of any local modifications and suspect this sed call to come from an other place. |