Summary: | Autoconf problems in ebuilding rpm, lablgtk & evince | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Robert Bradbury <robert.bradbury> |
Component: | [OLD] Development | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED NEEDINFO | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build log
automake-*.out emerge --info Logfile of example of failed aclocal. |
Description
Robert Bradbury
2008-04-05 11:30:56 UTC
that URL is just the homepage of automake ... it isnt redhat specific what you've shown are warnings, not errors evince unpacks fine for me ... are you sure the log you posted (which should be as an attachment, not inlined) is the one from the failure ? Created attachment 148968 [details]
build log
I'm also having trouble emerging Evince 2.22.0, dies at automake stage:
* Running automake --add-missing --copy ... [ !! ]
* Failed Running automake !
*
* Include in your bugreport the contents of:
*
* /var/tmp/portage/app-text/evince-2.22.0/temp/automake-25419.out
*
* ERROR: app-text/evince-2.22.0 failed.
* Call stack:
* ebuild.sh, line 49: Called src_unpack
* environment, line 2799: Called eautoreconf
* environment, line 884: Called eautomake
* environment, line 858: Called autotools_run_tool 'src_unpack' 'src_unpack' 'automake'
* environment, line 378: Called die
* The specific snippet of code:
* die "Failed Running $1 !";
* The die message:
* Failed Running automake !
*
Created attachment 148969 [details]
automake-*.out
Created attachment 148970 [details]
emerge --info
Nearly forgot ;-)
Created attachment 149005 [details]
Logfile of example of failed aclocal.
Attached is a trace of the failure of aclocal. Currently, I cannot reproduce this problem, after returning "oaf.m4" and "progsreiserfs.m4" to /usr/share/aclocal.
It was the contents of:
/root2/var/tmp/portage/app-arch/rpm-4.4.6-r3/temp/aclocal-22235.out
that lead me to the conclusion that there were old ".m4" files that needed to be removed.
The RedHat automake documentation, section 6.3.3 is what lead me to think that the ".m4" files contained underquoted definitions. But I am far from an expert on m4.
The only thing I can think right now is that there may have been some inconsistancy between the ebuilds and the package upgrade sources because rpm seem to build correctly both with and without the troublesome .m4 files.
none of the logs you posted include underquoted warnings. also, what package does this "oaf.m4" file come from ? lets focus on one package at a time, presumably the ones that are still failing. if rpm is now working, ignore it. if evince is currently failing, we'll investigate that. go into the build directory and run automake by hand: automake --add-missing --copy echo $? |