View previous topic :: View next topic |
Author |
Message |
Nermal Apprentice
Joined: 18 Apr 2002 Posts: 259 Location: UK
|
Posted: Mon Dec 13, 2004 10:56 am Post subject: libtool version mismatch errors |
|
|
When I emerge quite a few packages (totem 0.99.22 for example) I get the following error:
Code: | *** Gentoo sanity check failed! ***
*** libtool.m4 and ltmain.sh have a version mismatch! ***
*** (libtool.m4 = 1.5.10, ltmain.sh = 1.5) *** |
The solution in the bug reports on bugs.gentoo.org seems to suggest editing the ebuild and adding
Code: | libtoolize --copy --force |
a) This doesn't seem to work for me
b) What is actually causing this problem, and is there a better way to fix it than manually editing ebuilds?
Thanks. |
|
Back to top |
|
|
D1g1talS0ul n00b
Joined: 24 Feb 2004 Posts: 9 Location: whereis me
|
Posted: Mon Dec 13, 2004 9:32 pm Post subject: |
|
|
I had the same issue when emerging kde. I got around the error by adding the following to the ebuild script "/usr/portage/app-admin/fam/fam-2.7.0-r2.ebuild"
At line 28 (or there about) you'll see, chmod u+w ${S}/configure
Below that add cd ${S}; libtoolize --copy --force
Worked for me hope it works for you! |
|
Back to top |
|
|
KayoPs n00b
Joined: 15 Dec 2004 Posts: 3 Location: slocate KayoPs
|
Posted: Wed Dec 15, 2004 9:24 am Post subject: |
|
|
I'm having the same problem, but with diferent ebuids (fam included).
My question is :
Is there a better way to avoid that problem or do I have to edit all the ebuilds manully ?
(the solution given by D1g1talS0ul works :: thank's man). |
|
Back to top |
|
|
eNTi Veteran
Joined: 20 Oct 2002 Posts: 1011 Location: Salzburg, Austria
|
Posted: Wed Dec 15, 2004 11:35 am Post subject: |
|
|
Code: | checking for correct ltmain.sh version... no
*** Gentoo sanity check failed! ***
*** libtool.m4 and ltmain.sh have a version mismatch! ***
*** (libtool.m4 = 1.5.10, ltmain.sh = 1.4.3) ***
Please run:
libtoolize --copy --force
if appropriate, please contact the maintainer of this
package (or your distribution) for help.
make: *** [config.status] Error 1
|
now guess, wether the command above does work, nor is there a elibtoolize in the ebuild. i can't even tell, where to put it in the ebuild. now wtf is happening here? _________________ If you fall off a cliff, you might as well try to fly. After all, you got nothing to lose.
-- John Sheridan - Babylon 5, Season 4 |
|
Back to top |
|
|
FlumMmicH n00b
Joined: 31 Oct 2004 Posts: 58 Location: Sweden
|
Posted: Wed Dec 15, 2004 12:27 pm Post subject: |
|
|
got the exactly same problem.. but with lcms.. I need to fix this.. I can't compile everything now.. wonder how this could happen. _________________ Less is more. |
|
Back to top |
|
|
taskara Advocate
Joined: 10 Apr 2002 Posts: 3763 Location: Australia
|
Posted: Wed Dec 15, 2004 11:50 pm Post subject: |
|
|
you could downgrade to NON keyworded libtool, and try fam again
that should get you working at least.
but I had to UPgrade to latest libtool because of some other problem in my amd64 install.. we'll see if they come back or not in the meantime this works for me. _________________ Kororaa install method - have Gentoo up and running quickly and easily, fully automated with an installer! |
|
Back to top |
|
|
syouth Apprentice
Joined: 18 Sep 2004 Posts: 275
|
Posted: Thu Dec 16, 2004 9:19 am Post subject: |
|
|
i had the same problem with:
Code: | * media-libs/lcms
Latest version available: 1.13
Latest version installed: 1.13
Size of downloaded files: 572 kB
Homepage: http://www.littlecms.com/
Description: A lightweight, speed optimized color management engine
License: LGPL-2.1
|
i downgraded to libtool-1.5.2-r7, which was latest in tree before 1.5.10-r1 and completed lcms emergeing successfuly.
is the problem with libtool-1.5.10-r1 (not with current conf) and it will be repaired next release? _________________ psylove |
|
Back to top |
|
|
cbr Apprentice
Joined: 05 Jan 2004 Posts: 285 Location: Tallinn/Rakvere, Estonia
|
Posted: Thu Dec 16, 2004 12:42 pm Post subject: |
|
|
The same happens with me too. I have only noticed that when emerging lcms though. |
|
Back to top |
|
|
KoolKam n00b
Joined: 27 Feb 2004 Posts: 10 Location: Ontario,Canada
|
Posted: Thu Dec 16, 2004 6:12 pm Post subject: |
|
|
I too am having this problem , how do I fix it ? I am unable to update my world currently should I mask out the latest version and downgrade?
Chris |
|
Back to top |
|
|
KoolKam n00b
Joined: 27 Feb 2004 Posts: 10 Location: Ontario,Canada
|
|
Back to top |
|
|
dkaplowitz Guru
Joined: 22 Nov 2003 Posts: 596 Location: Philadelphia, PA
|
Posted: Thu Dec 16, 2004 6:30 pm Post subject: |
|
|
D1g1talS0ul wrote: | I had the same issue when emerging kde. I got around the error by adding the following to the ebuild script "/usr/portage/app-admin/fam/fam-2.7.0-r2.ebuild"
At line 28 (or there about) you'll see, chmod u+w ${S}/configure
Below that add cd ${S}; libtoolize --copy --force |
Thanks for posting this. Does anyone have any idea why whenever I edit this ebuilld I keep getting a Quote: | Waiting for fam.o.lock to be removed
Waiting for Client.o.lock to be removed | scrolling over and over for eternity whenever I try emerging fam again?
So odd. This fam issue is proving to be quite vexing. _________________ http://dkap.info |
|
Back to top |
|
|
dkaplowitz Guru
Joined: 22 Nov 2003 Posts: 596 Location: Philadelphia, PA
|
Posted: Thu Dec 16, 2004 6:59 pm Post subject: |
|
|
dkaplowitz wrote: | Does anyone have any idea why whenever I edit this ebuilld I keep getting a Quote: | Waiting for fam.o.lock to be removed
Waiting for Client.o.lock to be removed | scrolling over and over for eternity whenever I try emerging fam again? |
Got it...this helped:
Quote: | export enable_libtool_lock="no" |
And I successfully emerged fam with D1g1talS0ul's helpful suggestion.
Thanks all! _________________ http://dkap.info |
|
Back to top |
|
|
i92guboj Bodhisattva
Joined: 30 Nov 2004 Posts: 10315 Location: Córdoba (Spain)
|
Posted: Sun Dec 19, 2004 5:52 pm Post subject: |
|
|
D1g1talS0ul wrote: | I had the same issue when emerging kde. I got around the error by adding the following to the ebuild script "/usr/portage/app-admin/fam/fam-2.7.0-r2.ebuild"
At line 28 (or there about) you'll see, chmod u+w ${S}/configure
Below that add cd ${S}; libtoolize --copy --force
Worked for me hope it works for you! |
Great! Worked for me too... Thanx. |
|
Back to top |
|
|
evilshenaniganz Tux's lil' helper
Joined: 18 Dec 2003 Posts: 107 Location: /dev/random
|
Posted: Mon Dec 20, 2004 5:45 am Post subject: |
|
|
I've run into this problem a few times in my attempt to do a stage1 install on my Centrino notebook. So far I've run into this problem with app-admin/fam, media-libs/lcms, and now the latest is dev-db/unixODBC. I manged to get help from the forum on the first two, but with unixODBC I went out on a limb. I could not find in the ebuild for it, so I looked at the other ebuilds to see where I was putting: Code: | libtoolize --copy --force | and it worked for me to put it at the very end of Code: | src_unpack() {
#ebuild stuff here
#
#
libtoolize --copy --force #at the very end of the function
} |
I don't know if this just opened me up to some monster vulnerability, but it did successfully compile for me. |
|
Back to top |
|
|
soulwarrior Guru
Joined: 21 Oct 2002 Posts: 331
|
Posted: Mon Dec 20, 2004 4:56 pm Post subject: |
|
|
With the original ebuild I get the error :
Quote: |
Listener.o(.text+0xc45): In function `Listener::create_local_client(TCP_Client&, unsigned int)':
: warning: the use of `tempnam' is dangerous, better use `mkstemp'
Interest.o(.text+0x1164): In function `global constructors keyed to _ZN8Interest9hashtableE':
: undefined reference to `DNotify::DNotify(void (*)(unsigned long long, unsigned long, int))'
Interest.o(.text+0x114a): In function `__tcf_0':
: undefined reference to `DNotify::~DNotify()'
collect2: ld returned 1 exit status
make[2]: *** [famd] Error 1
make[2]: Leaving directory `/var/tmp/portage/fam-2.7.0-r2/work/fam-2.7.0/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/fam-2.7.0-r2/work/fam-2.7.0'
make: *** [all] Error 2
!!! ERROR: app-admin/fam-2.7.0-r2 failed.
!!! Function src_compile, Line 508, Exitcode 2
!!! emake failed
!!! If you need support, post the topmost build error, NOT this status message.
|
When I changed the ebuild following the suggestion from D1g1talS0ul's, I get the same "waiting loop" as dkaplowitz.
So I tried out the suggestion from dkaplowitz (export enable_libtool_lock="no"), but the same error as with the original ebuild shows up |
|
Back to top |
|
|
EricHsu Bodhisattva
Joined: 03 May 2004 Posts: 591 Location: Aragon Consulting Group, Beijing, China
|
Posted: Tue Dec 21, 2004 3:41 pm Post subject: |
|
|
evilshenaniganz wrote: | it worked for me to put it at the very end of Code: | src_unpack() {
#ebuild stuff here
#
#
libtoolize --copy --force #at the very end of the function
} |
|
Yes! It works for me to get totem 0.99.22 compiled too, big thanks! _________________ - http://nkbit.com
- http://twitter.com/xuyihua |
|
Back to top |
|
|
dose n00b
Joined: 01 Sep 2003 Posts: 19 Location: Belgium
|
Posted: Wed Dec 22, 2004 2:50 pm Post subject: |
|
|
evilshenaniganz wrote: | I've run into this problem a few times in my attempt to do a stage1 install on my Centrino notebook. So far I've run into this problem with app-admin/fam, media-libs/lcms, and now the latest is dev-db/unixODBC. I manged to get help from the forum on the first two, but with unixODBC I went out on a limb. I could not find in the ebuild for it, so I looked at the other ebuilds to see where I was putting: Code: | libtoolize --copy --force | and it worked for me to put it at the very end of Code: | src_unpack() {
#ebuild stuff here
#
#
libtoolize --copy --force #at the very end of the function
} |
I don't know if this just opened me up to some monster vulnerability, but it did successfully compile for me. |
worked for me as well!!
great |
|
Back to top |
|
|
bkunlimited l33t
Joined: 18 Jun 2004 Posts: 672
|
Posted: Thu Dec 23, 2004 5:29 pm Post subject: |
|
|
for me adding
Code: |
cd ${S}; libtoolize --copy --force
|
after
Code: |
cd ${S}; libtoolize --copy --force |
in /usr/portage/app-admin/fam/fam-2.7.0-r2.ebuild worked fine.
Thanks for the hint D1g1talS0ul!! |
|
Back to top |
|
|
Bob P Advocate
Joined: 20 Oct 2004 Posts: 3355 Location: Jackass! Development Labs
|
Posted: Fri Dec 24, 2004 10:04 pm Post subject: |
|
|
yep, this killed my emerge -e world, right after i had finished battening down the toolkit with emerge -e system && emerge -e system: Code: | >>> emerge (131 of 350) app-admin/fam-2.7.0-r2 to /
>>> md5 src_uri ;-) fam-2.7.0.tar.gz
>>> Unpacking source...
>>> Unpacking fam-2.7.0.tar.gz to /var/tmp/portage/fam-2.7.0-r2/work
* Applying fam-2.7.0-dnotify.patch ... [ ok ]
* Patching ${S}/ltmain.sh ...
* Applying portage-1.4.1.patch ...
* Applying relink-1.4.1.patch ...
* Applying sed-1.4.3.patch ...
* Applying uClibc/libtool patches ...
* Fixing ${S}/configure ... [ ok ]
* Using GNU config files from /usr/share/libtool
* Updating config.sub [ ok ]
* Updating config.guess [ ok ]
>>> Source unpacked.
* econf: updating /var/tmp/portage/fam-2.7.0-r2/work/fam-2.7.0/config.guess with /usr/share/gnuconfig/config.guess
* econf: updating /var/tmp/portage/fam-2.7.0-r2/work/fam-2.7.0/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for i686-pc-linux-gnu-strip... i686-pc-linux-gnu-strip
checking for i686-pc-linux-gnu-g++... i686-pc-linux-gnu-g++
checking for C++ compiler default output... a.out
checking whether the C++ compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether i686-pc-linux-gnu-g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of i686-pc-linux-gnu-g++... gcc3
checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
checking whether we are using the GNU C compiler... yes
checking whether i686-pc-linux-gnu-gcc accepts -g... yes
checking for i686-pc-linux-gnu-gcc option to accept ANSI C... none needed
checking dependency style of i686-pc-linux-gnu-gcc... gcc3
checking how to run the C preprocessor... i686-pc-linux-gnu-gcc -E
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for ld used by GCC... /usr/i686-pc-linux-gnu/bin/ld
checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes
checking for /usr/i686-pc-linux-gnu/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/i686-pc-linux-gnu-nm -B
checking for a sed that does not truncate output... /bin/sed
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking command to parse /usr/bin/i686-pc-linux-gnu-nm -B output... ok
checking how to run the C++ preprocessor... i686-pc-linux-gnu-g++ -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for i686-pc-linux-gnu-ranlib... i686-pc-linux-gnu-ranlib
checking for i686-pc-linux-gnu-strip... (cached) i686-pc-linux-gnu-strip
checking for objdir... .libs
checking for i686-pc-linux-gnu-gcc option to produce PIC... -fPIC
checking if i686-pc-linux-gnu-gcc PIC flag -fPIC works... yes
checking if i686-pc-linux-gnu-gcc static flag -static works... yes
checking if i686-pc-linux-gnu-gcc supports -c -o file.o... no
checking if we can lock with hard links... yes
checking if i686-pc-linux-gnu-gcc supports -fno-rtti -fno-exceptions... yes
checking whether the linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking whether -lc should be explicitly linked in... no
creating libtool
checking for a BSD-compatible install... /bin/install -c
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) yes
checking for pmap_set in -lrpcsvc... yes
checking for ANSI C header files... (cached) yes
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking linux/imon.h usability... no
checking linux/imon.h presence... no
checking for linux/imon.h... no
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking rpc/rpc.h usability... yes
checking rpc/rpc.h presence... yes
checking for rpc/rpc.h... yes
checking rpcsvc/mount.h usability... yes
checking rpcsvc/mount.h presence... yes
checking for rpcsvc/mount.h... yes
checking stddef.h usability... yes
checking stddef.h presence... yes
checking for stddef.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking sys/imon.h usability... no
checking sys/imon.h presence... no
checking for sys/imon.h... no
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking sys/select.h usability... yes
checking sys/select.h presence... yes
checking for sys/select.h... yes
checking sys/statvfs.h usability... yes
checking sys/statvfs.h presence... yes
checking for sys/statvfs.h... yes
checking sys/syssgi.h usability... no
checking sys/syssgi.h presence... no
checking for sys/syssgi.h... no
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking for sys/types.h... (cached) yes
checking sys/un.h usability... yes
checking sys/un.h presence... yes
checking for sys/un.h... yes
checking for unistd.h... (cached) yes
checking for stdbool.h that conforms to C99... yes
checking for _Bool... no
checking for bool... yes
checking for socklen_t... yes
checking for an ANSI C-conforming const... yes
checking for uid_t in sys/types.h... yes
checking for inline... inline
checking for pid_t... yes
checking for size_t... yes
checking whether time.h and sys/time.h may both be included... yes
checking for struct sockaddr.sa_len... no
checking for error_at_line... no
checking for sys/select.h... (cached) yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking types of arguments for select... int,fd_set *,struct timeval *
checking for bindresvport... yes
checking for _daemonize... no
checking for daemon... yes
checking for getgrmember... no
checking for select... no
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating include/Makefile
config.status: creating lib/Makefile
config.status: creating conf/Makefile
config.status: creating man/Makefile
config.status: creating test/Makefile
config.status: creating config.h
config.status: executing depfiles commands
cd . && /bin/sh /var/tmp/portage/fam-2.7.0-r2/work/fam-2.7.0/missing --run aclocal-1.6
cd . && \
/bin/sh /var/tmp/portage/fam-2.7.0-r2/work/fam-2.7.0/missing --run automake-1.6 --gnu Makefile
cd . && /bin/sh /var/tmp/portage/fam-2.7.0-r2/work/fam-2.7.0/missing --run autoconf
/bin/sh ./config.status --recheck
running /bin/sh ./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib CFLAGS=-march=pentium3 -O3 -pipe CXXFLAGS=-march=pentium3 -O3 -pipe host_alias=i686-pc-linux-gnu --no-create --no-recursion
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for i686-pc-linux-gnu-strip... i686-pc-linux-gnu-strip
checking for i686-pc-linux-gnu-g++... i686-pc-linux-gnu-g++
checking for C++ compiler default output file name... a.out
checking whether the C++ compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether i686-pc-linux-gnu-g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of i686-pc-linux-gnu-g++... gcc3
checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
checking whether we are using the GNU C compiler... yes
checking whether i686-pc-linux-gnu-gcc accepts -g... yes
checking for i686-pc-linux-gnu-gcc option to accept ANSI C... none needed
checking dependency style of i686-pc-linux-gnu-gcc... gcc3
checking how to run the C preprocessor... i686-pc-linux-gnu-gcc -E
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by i686-pc-linux-gnu-gcc... /usr/i686-pc-linux-gnu/bin/ld
checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes
checking for /usr/i686-pc-linux-gnu/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/i686-pc-linux-gnu-nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking for ANSI C header files... no
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... no
configure: WARNING: dlfcn.h: accepted by the compiler, rejected by the preprocessor!
configure: WARNING: dlfcn.h: proceeding with the compiler's result
checking for dlfcn.h... yes
checking how to run the C++ preprocessor... i686-pc-linux-gnu-g++ -E
checking for i686-pc-linux-gnu-g77... no
checking for i686-pc-linux-gnu-f77... no
checking for i686-pc-linux-gnu-xlf... no
checking for i686-pc-linux-gnu-frt... no
checking for i686-pc-linux-gnu-pgf77... no
checking for i686-pc-linux-gnu-fort77... no
checking for i686-pc-linux-gnu-fl32... no
checking for i686-pc-linux-gnu-af77... no
checking for i686-pc-linux-gnu-f90... no
checking for i686-pc-linux-gnu-xlf90... no
checking for i686-pc-linux-gnu-pgf90... no
checking for i686-pc-linux-gnu-epcf90... no
checking for i686-pc-linux-gnu-f95... no
checking for i686-pc-linux-gnu-fort... no
checking for i686-pc-linux-gnu-xlf95... no
checking for i686-pc-linux-gnu-ifc... no
checking for i686-pc-linux-gnu-efc... no
checking for i686-pc-linux-gnu-pgf95... no
checking for i686-pc-linux-gnu-lf95... no
checking for i686-pc-linux-gnu-gfortran... no
checking for g77... g77
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether g77 accepts -g... yes
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/i686-pc-linux-gnu-nm -B output from i686-pc-linux-gnu-gcc object... ok
checking for objdir... .libs
checking for i686-pc-linux-gnu-ar... i686-pc-linux-gnu-ar
checking for i686-pc-linux-gnu-ranlib... i686-pc-linux-gnu-ranlib
checking for i686-pc-linux-gnu-strip... (cached) i686-pc-linux-gnu-strip
checking for correct ltmain.sh version... no
*** Gentoo sanity check failed! ***
*** libtool.m4 and ltmain.sh have a version mismatch! ***
*** (libtool.m4 = 1.5.10, ltmain.sh = 1.4) ***
Please run:
libtoolize --copy --force
if appropriate, please contact the maintainer of this
package (or your distribution) for help.
make: *** [config.status] Error 1
!!! ERROR: app-admin/fam-2.7.0-r2 failed.
!!! Function src_compile, Line 508, Exitcode 2
!!! emake failed
!!! If you need support, post the topmost build error, NOT this status message. |
unfortunately, the solution recommended on-screen wasn't at all helpful: Code: |
gentoo etc # libtoolize --copy --force
libtoolize: `configure.ac' does not exist
Try `libtoolize --help' for more information.
gentoo etc # |
am i correct in the interpretation that this is a defective ebuild, and that this problem will go away when an update hits the portage tree? _________________ .
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks |
|
Back to top |
|
|
deian n00b
Joined: 03 Jan 2004 Posts: 12 Location: NY
|
Posted: Sun Dec 26, 2004 12:47 am Post subject: |
|
|
Thanks to whoever suggested just appending the libtoolize. I had the same problem with lcms when emerging firefox.
This solution worked for me:
original line: cd ${S}
new line:cd ${S};libtoolize --copy --force |
|
Back to top |
|
|
|