| View previous topic :: View next topic |
| Author |
Message |
mystified
l33t
Joined: 14 Feb 2004
Posts: 771
|
 Posted: Thu Oct 07, 2004 3:28 pm Post subject: cups autoconf failure |
 |
|
cups fails to build
| Code: | >>> Unpacking cups-1.1.20-source.tar.bz2 to /var/tmp/portage/cups-1.1.20-r3/work
* Applying disable-strip.patch... [ ok ]
* Applying cups-1.1.20-str633.patch... [ ok ]
* Applying cups-1.1.20-zero-len-udp-dos.patch... [ ok ]
* Applying str920.patch... [ ok ]
FATAL ERROR: Autoconf version 2.50 or higher is required for this script
!!! ERROR: net-print/cups-1.1.20-r3 failed.
!!! Function src_unpack, Line 36, Exitcode 2
!!! (no error message)
|
This is the version I have installed:
[ebuild R ] sys-devel/autoconf-2.59-r4
This is the 4th install I've tried and something fails each time. I'm really getting frustrated.
Please help.
Thanks |
|
| Back to top |
|
 |
lint
n00b
Joined: 07 Oct 2004
Posts: 2
Location: North Carolina
|
| Posted: Thu Oct 07, 2004 4:38 pm Post subject: |
|
|
I ran into the same problem. What it looks like after doing a little digging was that the autoconf perl script included in autoconf-2.59-r4 has been rolled back to an earlier version that no longer is compatible with the environment variables set in the ebuilds. Cups is the first to to need autoconf>2.5. If you're emerging more than cups, you want to edit /usr/bin/autoconf beneath the comments to be:
| Code: |
sub cat_ { local *F; open F, $_[0] or return; my @l = <F>; wantarray ? @l : join '', @l }
sub ac_version {
return ((@versions = cat_(shift) =~ /^\s*\[?AC_PREREQ\(\[?([^\)]{3}[0-9]?)[^\)]*\]?\)/mg) ? ((sort @versions)[-1]) : '');
}
my $binary = "$0-2.13";
my $binary_new = "$0-2.59";
# Autoconf is really getting out of hand, so rather start supporting
# WANT_AUTOCONF = "2.5" the like. Unfortunately it override the old
# variables, so if not set, just convert the old variables ....
if ($ENV{WANT_AUTOCONF} eq "") {
if ($ENV{WANT_AUTOCONF_2_1}) {
$ENV{WANT_AUTOCONF} = '2.1';
} elsif ($ENV{WANT_AUTOCONF_2_5}) {
$ENV{WANT_AUTOCONF} = '2.5';
}
}
if ($ENV{WANT_AUTOCONF} ne '2.1') {
if ((! -x $binary) # handle stuff like autom4te, where only 2.59 have the binary
|| (-x $binary_new # user may have only 2.13
&& (($ENV{WANT_AUTOCONF} eq '2.5')
|| -r 'configure.ac'
|| ac_version('configure.in') gt '2.13'
|| (cat_('configure') =~ /^# Generated by Autoconf (\S+)/m ? $1 : '') gt '2.13'
|| (cat_('Makefile.in') =~ /^# Makefile\.in generated by automake (\S+)/ ? $1 : '') ge '1.6'
|| ac_version('aclocal.m4') gt '2.13'))) {
$ENV{WANT_AUTOCONF} = '2.5'; # to prevent further "cats" and to enhance consistency (possible cwd etc)
$binary = $binary_new;
} else {
$ENV{WANT_AUTOCONF} = '2.1'; # for further consistency
}
}
# Set AUTOM4TE to the proper version (bug #40983).
# Do not set it for 2.13 though, as it does not ship autom4te.
if(($ENV{AUTOM4TE} eq "")
&& ($ENV{WANT_AUTOCONF} = '2.5')
&& ($0 ne 'autom4te')) {
$ENV{AUTOM4TE} = "autom4te-2.59";
}
$ENV{WANT_ACWRAPPER_DEBUG} and print STDERR "ac-wrapper: will execute <$binary>\n";
exec $binary, @ARGV;
die "ac-wrapper: ouch, couldn't call binary ($binary).\n";
|
If you are just doing cups, you can use:
WANT_AUTOCONF_2_5=1 emerge cups
Otherwise, you can wait until a fixed ebuild is out.
Mark
Edit: Fixed the code since my copy/paste mangled it. Be careful with line breaks.
Last edited by lint on Thu Oct 07, 2004 5:39 pm; edited 1 time in total |
|
| Back to top |
|
|
mystified
l33t
Joined: 14 Feb 2004
Posts: 771
|
| Posted: Thu Oct 07, 2004 4:52 pm Post subject: |
|
|
| Thanks for the help. I'm trying it now. |
|
| Back to top |
|
|
ManiacNL
n00b
Joined: 20 Sep 2004
Posts: 44
Location: Oostburg
|
| Posted: Sat Oct 09, 2004 12:46 pm Post subject: |
|
|
i just deleted /usr/bin/autoconf-2.13
autoconf-2.59 was also in that folder, after check autoconf --version it was turned into 2.59 
cups installed just fine after this  |
|
| Back to top |
|
|
irf2003
Veteran
Joined: 10 Sep 2003
Posts: 1078
|
| Posted: Sat Oct 09, 2004 5:31 pm Post subject: |
|
|
edit the cups ebuild, in "src_unpack()"
change:
| Code: |
WANT_AUTOCONF=2.5 autoconf || die
|
to:
| Code: |
WANT_AUTOCONF_2_5=1 autoconf || die
|
hth |
|
| Back to top |
|
|
ojintoad
n00b
Joined: 31 Mar 2004
Posts: 17
|
| Posted: Sat Oct 09, 2004 7:14 pm Post subject: |
|
|
Have any of you reported this as a bug or have any of the devs been watching the forums and are going to handle this?
I used the strategy of removing the old autoconf directory that Maniac used. But shouldn't it have been removed allready?
| Quote: |
i just deleted /usr/bin/autoconf-2.13
autoconf-2.59 was also in that folder, after check autoconf --version it was turned into 2.59 Smile
cups installed just fine after this Laughing |
People in the gentoo chat rooms are telling me you should use the Want_Autoconf emerge method, not Maniacs. However, I have gotten no information as to why. |
|
| Back to top |
|
|
lint
n00b
Joined: 07 Oct 2004
Posts: 2
Location: North Carolina
|
| Posted: Sun Oct 10, 2004 5:06 pm Post subject: |
|
|
| Some programs still want to use autoconf-2.13, so it is better to keep it around and use the script to appropriatly choose. The issue was with the ac-wrapper script being wrong in cvs. It has been fixed as of autoconf-2.59-r5. The Want_Autoconf=? is supposed to be the new standard method for specifying the version being used. |
|
| Back to top |
|
|
ManiacNL
n00b
Joined: 20 Sep 2004
Posts: 44
Location: Oostburg
|
| Posted: Tue Oct 12, 2004 11:14 am Post subject: |
|
|
| ojintoad wrote: | Have any of you reported this as a bug or have any of the devs been watching the forums and are going to handle this?
I used the strategy of removing the old autoconf directory that Maniac used. But shouldn't it have been removed allready?
| Quote: |
i just deleted /usr/bin/autoconf-2.13
autoconf-2.59 was also in that folder, after check autoconf --version it was turned into 2.59 Smile
cups installed just fine after this Laughing |
People in the gentoo chat rooms are telling me you should use the Want_Autoconf emerge method, not Maniacs. However, I have gotten no information as to why. |
after it i reemerged autoconf and it is restored again, because you can get other problems when 2.13 does not exist anymore
for instance i had problems emerging mozilla, after emerge autoconf this problem was solved |
|
| Back to top |
|
|
|
Portage & Programming
