Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 511706 - x11-proto/xproto-7.0.25 - .../work/xproto-7.0.25/missing: line 81: aclocal-1.14: command not found
Summary: x11-proto/xproto-7.0.25 - .../work/xproto-7.0.25/missing: line 81: aclocal-1....
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Library (show other bugs)
Hardware: AMD64 Linux
: Normal normal
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-28 17:23 UTC by Brian McKee
Modified: 2014-06-03 07:07 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info output (emerge--info.txt,6.22 KB, text/plain)
2014-05-28 17:23 UTC, Brian McKee
Details
build.log (build.log,9.34 KB, text/plain)
2014-05-29 01:48 UTC, Brian McKee
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Brian McKee 2014-05-28 17:23:16 UTC
Created attachment 377782 [details]
emerge --info output

xproto won't build on my laptop. This problem appears to be unique to me as I have found no information on google or in the forums. To resolve this have have eliminated all "~amd64" keywords (except the media ones that are necessary to build). I have rebuilt perl with perl-cleaner --reallyall and I have tried a few other things.

The error indicates it's looking for the latest version of automake which won't build on my system either. But according to the forum help I got, automake 1.14 should not necessary for this ebuild.

Here's the error output:

>>> Source configured.
>>> Compiling source in /var/tmp/portage/x11-proto/xproto-7.0.25/work/xproto-7.0.25 ...
 * abi_x86_64.amd64: running multilib-minimal_abi_src_compile
make -j8 
CDPATH="${ZSH_VERSION+.}:" && cd /var/tmp/portage/x11-proto/xproto-7.0.25/work/xproto-7.0.25 && /bin/sh /var/tmp/portage/x11-proto/xproto-7.0.25/work/xproto-7.0.25/missing aclocal-1.14 
/var/tmp/portage/x11-proto/xproto-7.0.25/work/xproto-7.0.25/missing: line 81: aclocal-1.14: command not found
WARNING: 'aclocal-1.14' is missing on your system.
         You should only need it if you modified 'acinclude.m4' or
         'configure.ac' or m4 files included by 'configure.ac'.
         The 'aclocal' program is part of the GNU Automake package:
         <http://www.gnu.org/software/automake>
         It also requires GNU Autoconf, GNU m4 and Perl in order to run:
         <http://www.gnu.org/software/autoconf>
         <http://www.gnu.org/software/m4/>
         <http://www.perl.org/>
make: *** [/var/tmp/portage/x11-proto/xproto-7.0.25/work/xproto-7.0.25/aclocal.m4] Error 127
 * ERROR: x11-proto/xproto-7.0.25::gentoo failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=x11-proto/xproto-7.0.25::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=x11-proto/xproto-7.0.25::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/x11-proto/xproto-7.0.25/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/x11-proto/xproto-7.0.25/temp/environment'.
 * Working directory: '/var/tmp/portage/x11-proto/xproto-7.0.25/work/xproto-7.0.25-abi_x86_64.amd64'
 * S: '/var/tmp/portage/x11-proto/xproto-7.0.25/work/xproto-7.0.25'

>>> Failed to emerge x11-proto/xproto-7.0.25, Log file:

>>>  '/var/tmp/portage/x11-proto/xproto-7.0.25/temp/build.log'

 * Messages for package x11-proto/xproto-7.0.25:

 * ERROR: x11-proto/xproto-7.0.25::gentoo failed (compile phase):
 *   emake failed
Comment 1 Jeroen Roovers (RETIRED) gentoo-dev 2014-05-28 23:24:20 UTC
Please attach the entire build log to this bug report.
Comment 2 Brian McKee 2014-05-29 01:48:50 UTC
Created attachment 377798 [details]
build.log
Comment 3 Jeroen Roovers (RETIRED) gentoo-dev 2014-05-29 03:56:18 UTC
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?
Comment 4 Brian McKee 2014-05-30 15:57:43 UTC
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?
Comment 5 Brian McKee 2014-06-01 16:39:56 UTC
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.
Comment 6 Jeroen Roovers (RETIRED) gentoo-dev 2014-06-03 00:27:02 UTC
(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.
Comment 7 Brian McKee 2014-06-03 02:09:46 UTC
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.
Comment 8 Tom Wijsman (TomWij) (RETIRED) gentoo-dev 2014-06-03 07:07:38 UTC
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.