emerge -u world ... >>> emerge sys-devel/autoconf-1.6.1-r6 to / ... configure: errror: Autoconf 2.52 or better is required ... !!! Function src_compile, Line 20, Exitcode 1 ... This effectively blocks any further updates of anything that depends on autoconf, unless I explicitly specify each one, being careful to force the ones with dependencies on autoconf to skip building dependencies. I'll switch to Mandrake before I do that. Autoconf is the most recent unmasked version; 'emerge -u autoconf' gives nothing but 'regenerating GNU info directory index'. A rebuild of autoconf gives this: emerge autoconf Calculating dependencies ..done! >>> emerge sys-devel/autoconf-2.53a to / ... Can't locate IO/Handle.pm in @INC (@INC contains: /var/tmp/portage/autoconf-2.53a/work/autoconf-2.53a/lib /usr/lib/perl5/5.6.1/i686-linux /usr/lib/perl5/5.6.1 /usr/lib/perl5/site_perl/5.6.1 /usr/lib/perl5/site_perl .) at /usr/lib/perl5/5.6.1/i686-linux/IO/Seekable.pm line 101. ... !!! Function src_compile, Line 11, Exitcode 2 This leads me to believe that this is a Perl problem. Handle.pm exists, but not in IO. Should I symlink this? And if so, why isn't it already symlinked?
I have here: nosferatu 3.1 # find /usr/lib/ -name Handle.pm /usr/lib/perl5/5.6.1/i686-linux/IO/Handle.pm /usr/lib/perl5/5.6.1/Tie/Handle.pm nosferatu 3.1 #
Remerging perl maybe fixes it ?
Wierd. It works now, after I rebuilt Perl and updated Portage. Don't know which it was, though. Anyone care to confirm? Once again, Gentoo manages to pull itself together, if you try again.
Well, I never had that problem, and also didnt run into it when doing a gcc-3.1 bootstrap and emerge system this weekend.
