Updating Portage Breaks at Libtool

prolific · Apprentice Joined: 19 Apr 2002 Posts: 237

I tried updating portage today.. [ebuild U ] sys-apps/portage-2.0.48-r1 [2.0.47-r10] ... When sys-devel/libtool-1.4.3-r1 was emerging i got this error:

checking for dl.h... no
checking for dld.h... no
checking for string.h... yes
checking for strchr... yes
checking for strrchr... yes
checking whether libtool supports -dlopen/-dlpreopen... yes
checking for dlopen in -ldl... yes
checking for shl_load... no
checking for shl_load in -ldld... no
checking for dld_link in -ldld... no
checking for dlerror... yes
checking command to parse /usr/bin/nm -B output... yes
checking for _ prefix in compiled symbols... (cached) no
updating cache .././config.cache
creating ./config.status
creating Makefile
creating config.h
rm -f acinclude.m4
cp ./libtool.m4 acinclude.m4
cd . && aclocal
cd . && automake --gnu --include-deps Makefile
cd . && autoconf
/usr/bin/m4: `changeword' from frozen file not found in builtin table!
autom4te-2.57: /usr/bin/m4 failed with exit status: 1
make: *** [configure] Error 1
make: *** Waiting for unfinished jobs....

!!! ERROR: sys-devel/libtool-1.4.3-r1 failed.
!!! Function src_compile, Line 83, Exitcode 2
!!! (no error message)

Pythonhead · Posted: Sat Jun 07, 2003 11:20 pm Post subject:

Use the stable version of libtools. That one doesn't play nicely with autoconf.

prolific · Apprentice Joined: 19 Apr 2002 Posts: 237

I have libtool 1.4.3-r2 installed right now. But when i do emerge -u portage it will automatically try to install libtool 1.4.3-r1 and that is where the emerge stops.. Can i skip over this libtool 1.4.2-r2 and go onwards with the other stuff that needs to be emerged b4 portage gets updated?

matroskin · Apprentice Joined: 21 Jan 2003 Posts: 214

try to emerge automake first
[edit] you need automake version 1.7 to compile some packages, so upgrade automake and everything will work [/edit]