View previous topic :: View next topic |
Author |
Message |
embobo Guru
Joined: 19 May 2003 Posts: 311
|
Posted: Mon Dec 08, 2003 6:24 pm Post subject: fam-2.7.0 emake error |
|
|
cd . && /bin/sh /var/tmp/portage/fam-2.7.0/work/fam-2.7.0/missing --run autoconfautom4te-2.58: cannot open configure: Permission denied
make: *** [configure] Error 1
!!! ERROR: app-admin/fam-2.7.0 failed.
!!! Function src_compile, Line 391, Exitcode 2
!!! emake failed
Sorry, no time to file a bug report.
Solution:
ebuild /usr/portage/app-admin/fam/fam-2.7.0.ebuild compile
...wait for error...
chmod ug+w /var/tmp/portage/fam-2.7.0/work/fam-2.7.0/configure
ebuild /usr/portage/app-admin/fam/fam-2.7.0.ebuild compile
...should compile cleanly...
ebuild /usr/portage/app-admin/fam/fam-2.7.0.ebuild merge |
|
Back to top |
|
|
embobo Guru
Joined: 19 May 2003 Posts: 311
|
Posted: Mon Dec 08, 2003 6:26 pm Post subject: |
|
|
You may wish to unmerge older versions of fam too, e.g.,
emerge fam-2.6.10-r1 unmerge |
|
Back to top |
|
|
twisted_steel n00b
Joined: 17 Jul 2003 Posts: 40 Location: Maine
|
Posted: Tue Feb 10, 2004 6:58 am Post subject: |
|
|
I tried your methods but am unable to emerge fam-2.7.
Code: | ...
rm -fr .libs/libfam.la .libs/libfam.* .libs/libfam.*
g++ "{ global:" > .libs/libfam.ver
g++: { global:: No such file or directory
g++: no input files
make[2]: *** [libfam.la] Error 1
make[2]: Leaving directory `/var/tmp/portage/fam-2.7.0/work/fam-2.7.0/lib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/fam-2.7.0/work/fam-2.7.0'
make: *** [all] Error 2
!!! ERROR: app-admin/fam-2.7.0 failed.
!!! Function src_compile, Line 418, Exitcode 2
!!! emake failed |
This happened as a side effect of running Quote: | emerge -U epiphany | . _________________ "For every sprinkle I find, I shall kill you!" - Stewie |
|
Back to top |
|
|
DyeDrin n00b
Joined: 10 Feb 2004 Posts: 2
|
Posted: Tue Feb 10, 2004 7:15 am Post subject: |
|
|
I'm getting the same error message as twisted_steel is about
Code: | rm -fr .libs/libfam.la .libs/libfam.* .libs/libfam.*
g++ "{ global:" > .libs/libfam.ver
g++: { global:: No such file or directory
g++: no input files
make[2]: *** [libfam.la] Error 1
make[2]: Leaving directory `/var/tmp/portage/fam-2.7.0/work/fam-2.7.0/lib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/fam-2.7.0/work/fam-2.7.0'
make: *** [all] Error 2
!!! ERROR: app-admin/fam-2.7.0 failed.
!!! Function src_compile, Line 418, Exitcode 2
!!! emake failed |
It's giving me the message when I try and emerge kde. There's no follow-up so I was wondering how i can fix this. Thanks. |
|
Back to top |
|
|
junco n00b
Joined: 09 Jun 2003 Posts: 41
|
Posted: Tue Feb 10, 2004 7:27 am Post subject: Also... |
|
|
Me three on that line 418 error. |
|
Back to top |
|
|
batang_gentoo n00b
Joined: 20 Oct 2003 Posts: 9
|
Posted: Tue Feb 10, 2004 7:31 am Post subject: |
|
|
I am having the same problem here, I think the following lines in the ebuild are causing the problem:
Code: |
libtoolize -c -f || die "libtoolize failed"
aclocal || die "aclocal failed"
autoconf || die "autoconf failed"
|
This is in fam-2.7.0.ebuild
In fam-2.6.10-r1.ebuild it has this:
Code: |
export WANT_AUTOCONF=2.5
export WANT_AUTOMAKE=1.5
aclocal
autoconf
automake --add-missing
|
I am guessing that fam-2.7.0 has the same WANT_AUTO* settings as 2.6.10 because when I unpack the tarball and do the ./configure && make ritual, it compiles without any problems.
Is it really necessary to update the autotools files in the package using the above lines prior to building? That sort of defeats the purpose of the autotools. |
|
Back to top |
|
|
grug n00b
Joined: 10 Feb 2004 Posts: 5
|
Posted: Tue Feb 10, 2004 9:50 am Post subject: |
|
|
Having the same problem too...trying to install xfce4 |
|
Back to top |
|
|
copeja n00b
Joined: 16 Jul 2003 Posts: 3
|
Posted: Tue Feb 10, 2004 10:40 am Post subject: |
|
|
I had an ebuild from 02-09-04 replaced the newer ebuild with it and fam compiled no complaints. I have posted the the file. The newer ebuild doesn't have the part about
fix permissions. I don't know if that is the problem but this ebuild works
# Copyright 1999-2004 Gentoo Technologies, Inc.
# Distributed under the terms of the GNU General Public License v2
# $Header: /home/cvsroot/gentoo-x86/app-admin/fam/fam-2.7.0.ebuild,v 1.7 2004/02/09 15:38:26 gustavoz Exp $
inherit libtool eutils
DESCRIPTION="FAM, the File Alteration Monitor"
HOMEPAGE="http://oss.sgi.com/projects/fam/"
SRC_URI="ftp://oss.sgi.com/projects/fam/download/stable/${P}.tar.gz"
LICENSE="GPL-2 LGPL-2.1"
SLOT="0"
KEYWORDS="x86 ppc ~alpha sparc hppa ~amd64 ~ia64"
DEPEND=">=net-nds/portmap-5b-r6"
src_unpack() {
unpack ${A}
# fix permission problems with user* in FEATURES (#35307)
chmod u+w ${S}/configure
}
src_install() {
einstall || die
dosed "s:local_only = false:local_only = true:g" conf/fam.conf
exeinto /etc/init.d
doexe ${FILESDIR}/famd
dodoc AUTHORS COPYING ChangeLog INSTALL NEWS TODO README
}
pkg_postinst() {
einfo "To enable fam on boot you will have to add it to the"
einfo "default profile, issue the following command as root to do so."
echo
einfo "rc-update add famd default"
# temporary warning for people upgrading
# 6-12-03 foser <foser@gentoo.org>
echo
echo
ewarn "IMPORTANT INFO FOR USERS UPGRADING FROM OLDER (<2.7.0) FAM VERSIONS :"
echo
einfo "With the 2.7.0 version the fam daemon moved to sbin and was"
einfo "renamed from 'fam' to 'famd'. These changes are for consistency"
einfo "reasons also applied to the Gentoo init script. This means you"
einfo "will have to remove fam from the default runlevel and add famd."
einfo "This can be done by issueing the following commands :"
echo
einfo "rc-update del fam"
einfo "rc-update add famd default"
einfo "rm /etc/init.d/fam"
echo
einfo "The last command removes the old init script.
}
copeja _________________ Better is the worst enemy of good enough.
In a world without fences who needs gates?
Avoid the gates of hell. Use Linux.!
Registered Linux User # 251131
Gentoo Linux-2004 2.6.3- i686 |
|
Back to top |
|
|
brainsaw66 n00b
Joined: 27 Jan 2004 Posts: 8
|
Posted: Tue Feb 10, 2004 11:20 am Post subject: |
|
|
Code: | chmod ug+w /var/tmp/portage/fam-2.7.0/work/fam-2.7.0/configure
rm /usr/portage/app-admin/fam/fam-2.7.0.ebuild |
and then emerged it again. That did it!
But don't ask me why
BTW copeja's ebuilt didn't work for me. |
|
Back to top |
|
|
ageb n00b
Joined: 20 Sep 2003 Posts: 48
|
Posted: Tue Feb 10, 2004 1:28 pm Post subject: |
|
|
Quote: |
and then emerged it again. That did it!
But don't ask me why
BTW copeja's ebuilt didn't work for me.
|
Just guessing here but I think may doing this prevents fam-2.7.0 from being emerged.In my case when I followed these instructions it was the previous version of fam that was emerged. Presumably this is to be expected if you delete the current ebuild - or maybe I just did something wrong...
Cheers
Age |
|
Back to top |
|
|
thenapalm n00b
Joined: 14 Jul 2003 Posts: 17
|
Posted: Tue Feb 10, 2004 1:31 pm Post subject: |
|
|
brainsaw66 wrote: | Code: | chmod ug+w /var/tmp/portage/fam-2.7.0/work/fam-2.7.0/configure
rm /usr/portage/app-admin/fam/fam-2.7.0.ebuild |
and then emerged it again. That did it!
But don't ask me why
BTW copeja's ebuilt didn't work for me. |
I just did this on my system, but running "fam --version" still says 2.6.10.
Also, running "emerge sync" followed by "emerge -Up fam" still says it wants to upgrade to 2.7.0.
edit: heh, looks like ageb and I found this out around the same time! _________________ demux_viv.c:308:2: warning: #warning "Calculate PTS from picture header!" OH NO!!!!! |
|
Back to top |
|
|
praioz n00b
Joined: 28 Apr 2003 Posts: 20 Location: germany
|
Posted: Tue Feb 10, 2004 1:34 pm Post subject: |
|
|
brainsaw's option helped on mine as well
gladly |
|
Back to top |
|
|
brainsaw66 n00b
Joined: 27 Jan 2004 Posts: 8
|
Posted: Tue Feb 10, 2004 3:42 pm Post subject: |
|
|
ageb and thenapalm you are right! I didn't notice that because it worked without errors (and I don't use fam...)
But to help some others around I looked at the ebuilt and I don't know why copeja's modifications didn't work for me (because it seems to be the same)
If you need fam, version 2.7.0 try editing the ebuilt and change the method src_unpack() to:
Code: |
nano -w /usr/portage/app-admin/fam/fam-2.7.0.ebuild
src_unpack() {
unpack ${A}
# cd ${S}
# libtoolize -c -f || die "libtoolize failed"
# aclocal || die "aclocal failed"
# autoconf || die "autoconf failed"
} |
But again, don't ask me why. I now have fam, version 2.7.0 compiled, but I don't know if I will ever use this and if it functions properly. |
|
Back to top |
|
|
thenapalm n00b
Joined: 14 Jul 2003 Posts: 17
|
Posted: Tue Feb 10, 2004 3:47 pm Post subject: |
|
|
brainsaw66 wrote: | ageb and thenapalm you are right! I didn't notice that because it worked without errors (and I don't use fam...)
|
Yep, this solution was posted in another thread and it worked for me. I don't use fam either, but it was a dependency for about 8 other packages, so something must be needin' it. Problem solved. _________________ demux_viv.c:308:2: warning: #warning "Calculate PTS from picture header!" OH NO!!!!! |
|
Back to top |
|
|
Barkotron Apprentice
Joined: 05 Aug 2003 Posts: 253 Location: location, location.
|
Posted: Tue Feb 10, 2004 4:11 pm Post subject: |
|
|
copeja wrote: | I had an ebuild from 02-09-04 replaced the newer ebuild with it and fam compiled no complaints. I have posted the the file. The newer ebuild doesn't have the part about
fix permissions. I don't know if that is the problem but this ebuild works
# Copyright 1999-2004 Gentoo Technologies, Inc.
# Distributed under the terms of the GNU General Public License v2
# $Header: /home/cvsroot/gentoo-x86/app-admin/fam/fam-2.7.0.ebuild,v 1.7 2004/02/09 15:38:26 gustavoz Exp $
inherit libtool eutils
DESCRIPTION="FAM, the File Alteration Monitor"
HOMEPAGE="http://oss.sgi.com/projects/fam/"
SRC_URI="ftp://oss.sgi.com/projects/fam/download/stable/${P}.tar.gz"
LICENSE="GPL-2 LGPL-2.1"
SLOT="0"
KEYWORDS="x86 ppc ~alpha sparc hppa ~amd64 ~ia64"
DEPEND=">=net-nds/portmap-5b-r6"
src_unpack() {
unpack ${A}
# fix permission problems with user* in FEATURES (#35307)
chmod u+w ${S}/configure
}
src_install() {
einstall || die
dosed "s:local_only = false:local_only = true:g" conf/fam.conf
exeinto /etc/init.d
doexe ${FILESDIR}/famd
dodoc AUTHORS COPYING ChangeLog INSTALL NEWS TODO README
}
pkg_postinst() {
einfo "To enable fam on boot you will have to add it to the"
einfo "default profile, issue the following command as root to do so."
echo
einfo "rc-update add famd default"
# temporary warning for people upgrading
# 6-12-03 foser <foser@gentoo.org>
echo
echo
ewarn "IMPORTANT INFO FOR USERS UPGRADING FROM OLDER (<2.7.0) FAM VERSIONS :"
echo
einfo "With the 2.7.0 version the fam daemon moved to sbin and was"
einfo "renamed from 'fam' to 'famd'. These changes are for consistency"
einfo "reasons also applied to the Gentoo init script. This means you"
einfo "will have to remove fam from the default runlevel and add famd."
einfo "This can be done by issueing the following commands :"
echo
einfo "rc-update del fam"
einfo "rc-update add famd default"
einfo "rm /etc/init.d/fam"
echo
einfo "The last command removes the old init script.
}
|
Nice one copeja!
Just one thing, that last line needed to be: Code: | einfo "The last command removes the old init script." |
Once I'd changed that, everything nice and smooth _________________ Give a man a fire and he'll be warm for a day: set fire to him and he'll be warm for the rest of his life. |
|
Back to top |
|
|
toe-star n00b
Joined: 10 Feb 2004 Posts: 1
|
Posted: Tue Feb 10, 2004 4:12 pm Post subject: Another work-around |
|
|
I also found a work-around:
Code: |
emerge app-admin/fam-2.7.0
<error occurs>
cd /var/tmp/portage/fam-2.7.0/work/fam-2.7.0/lib
../libtool g++ -g -O2 -o libfam.la -rpath /usr/local/lib -export-symbols fam.sym Client.lo fam.lo -lstdc++ -lrpcsvc
ebuild /usr/portage/app-admin/fam/fam-2.7.0.ebuild compile
ebuild /usr/portage/app-admin/fam/fam-2.7.0.ebuild merge
|
Quote: | You may wish to unmerge older versions of fam too, e.g.,
emerge fam-2.6.10-r1 unmerge
|
I don't know which workaround is better but this one worked for me |
|
Back to top |
|
|
twisted_steel n00b
Joined: 17 Jul 2003 Posts: 40 Location: Maine
|
Posted: Tue Feb 10, 2004 4:55 pm Post subject: |
|
|
copeja's ebuild + Barkotron's slight modification = success
Thanks _________________ "For every sprinkle I find, I shall kill you!" - Stewie |
|
Back to top |
|
|
batang_gentoo n00b
Joined: 20 Oct 2003 Posts: 9
|
Posted: Tue Feb 10, 2004 5:27 pm Post subject: |
|
|
brainsaw66 wrote: | ageb and thenapalm you are right! I didn't notice that because it worked without errors (and I don't use fam...)
But to help some others around I looked at the ebuilt and I don't know why copeja's modifications didn't work for me (because it seems to be the same)
If you need fam, version 2.7.0 try editing the ebuilt and change the method src_unpack() to:
Code: |
nano -w /usr/portage/app-admin/fam/fam-2.7.0.ebuild
src_unpack() {
unpack ${A}
# cd ${S}
# libtoolize -c -f || die "libtoolize failed"
# aclocal || die "aclocal failed"
# autoconf || die "autoconf failed"
} |
But again, don't ask me why. I now have fam, version 2.7.0 compiled, but I don't know if I will ever use this and if it functions properly. |
If you are using gnome, kde and I think XFCE4 you are using FAM without even knowing about it, which is the whole point to it being a daemon.
FAM stands for File Alteration Monitor, which pretty much summarizes what it does: it monitors your filesystem for any changes and notifies client apps (such as nautilus) which files have changed and if it's concered with that file, client app will do some stuff with it such as update the window displaying the file and somesuch.
The following:
Code: | # cd ${S}
# libtoolize -c -f || die "libtoolize failed"
# aclocal || die "aclocal failed"
# autoconf || die "autoconf failed"
|
works because this was the cause of the problem as I have pointed out above in my previous post. But the question is, why did the ebuild author find it necessary to update the autotools files in the FAM package when they are working just fine as they are?
I think there is a bug in the aclocal.m4 file that comes with the libtool-1.4.3-r3 package which is causing the compile error.
EDIT:
This is a confirmed bug in libtool-1.4.3 that causes this. I already filed a bug report #41140.
See here for references:
http://mail.gnome.org/archives/garnome-list/2003-August/msg00070.html
http://mail.gnome.org/archives/garnome-list/2003-August/msg00073.html |
|
Back to top |
|
|
xijo n00b
Joined: 20 Sep 2003 Posts: 14
|
Posted: Tue Feb 10, 2004 9:16 pm Post subject: Re: Another work-around |
|
|
toe-star wrote: | I also found a work-around:
Code: |
emerge app-admin/fam-2.7.0
<error occurs>
cd /var/tmp/portage/fam-2.7.0/work/fam-2.7.0/lib
../libtool g++ -g -O2 -o libfam.la -rpath /usr/local/lib -export-symbols fam.sym Client.lo fam.lo -lstdc++ -lrpcsvc
ebuild /usr/portage/app-admin/fam/fam-2.7.0.ebuild compile
ebuild /usr/portage/app-admin/fam/fam-2.7.0.ebuild merge
|
Quote: | You may wish to unmerge older versions of fam too, e.g.,
emerge fam-2.6.10-r1 unmerge
|
I don't know which workaround is better but this one worked for me |
worked for me ² perfectly - thx - nice solution.
greetz
xijo |
|
Back to top |
|
|
lagitus n00b
Joined: 04 Jan 2004 Posts: 17
|
Posted: Tue Feb 10, 2004 9:54 pm Post subject: |
|
|
I had the same problem and fixed it the same way. What is wrong with the ebuild and when will it be fixed? |
|
Back to top |
|
|
grug n00b
Joined: 10 Feb 2004 Posts: 5
|
Posted: Tue Feb 10, 2004 11:26 pm Post subject: |
|
|
Thanks toe-star. Works great. |
|
Back to top |
|
|
batang_gentoo n00b
Joined: 20 Oct 2003 Posts: 9
|
Posted: Wed Feb 11, 2004 3:43 am Post subject: |
|
|
lagitus wrote: | I had the same problem and fixed it the same way. What is wrong with the ebuild and when will it be fixed? |
These lines are what's wrong with the ebuild:
Code: | src_unpack() {
unpack ${A}
cd ${S}
libtoolize -c -f || die "libtoolize failed"
aclocal || die "aclocal failed"
autoconf || die "autoconf failed"
}
|
the lines after the
I really don't see the point to updating the libtool and autotools files. Unless you are a developer and make changes to configure.ac and friends, you really don't need to run libtoolize, aclocal, autoconf (and in some cases automake).
Plus the fact that libtool itself has a bug that causes this problem. |
|
Back to top |
|
|
///M5 n00b
Joined: 10 Sep 2002 Posts: 3
|
Posted: Wed Feb 11, 2004 5:27 am Post subject: |
|
|
two methods worked for me:
on my work machine I commented out the lines that were messing up the ebuild (as described above by batang_gentoo).
on my home machine I just emerged the latest libtool (1.5.2-r1):
Code: | ACCEPT_KEYWORDS="~x86" emerge libtool |
I'm not sure if the newer libtool will cause any other problems but so far so good. |
|
Back to top |
|
|
bertvv n00b
Joined: 15 Jun 2003 Posts: 46 Location: Pamel, Flanders
|
Posted: Wed Feb 11, 2004 8:00 am Post subject: |
|
|
This thread helped me getting fam emerged. However, now emerging kdebase crashes:
Code: | ...
/bin/sh ../../libtool --silent --mode=link --tag=CXX g++ -Wnon-virtual-dtor -Wno-long-long -Wundef -Wall -W -Wpointer-arith -Wwrite-strings -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -DNDEBUG -DNO_DEBUG -O2 -O2 -mcpu=i686 -pipe -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -D_GNU_SOURCE -o kded_favicons.la -rpath /usr/kde/3.2/lib/kde3 -L/usr/X11R6/lib -L/usr/qt/3/lib -L/usr/kde/3.2/lib -module -avoid-version favicons.lo favicons_skel.lo -lkio
grep: /usr/local/lib/libfam.la: No such file or directory
/bin/sed: can't read /usr/local/lib/libfam.la: No such file or directory
libtool: link: `/usr/local/lib/libfam.la' is not a valid libtool archive
make[3]: *** [kded_favicons.la] Error 1
make[3]: Leaving directory `/var/tmp/portage/kdebase-3.2.0/work/kdebase-3.2.0/libkonq/favicons'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/kdebase-3.2.0/work/kdebase-3.2.0/libkonq'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/kdebase-3.2.0/work/kdebase-3.2.0'
make: *** [all] Error 2
!!! ERROR: kde-base/kdebase-3.2.0 failed.
!!! Function kde_src_compile, Line 127, Exitcode 2
!!! died running emake, kde_src_compile:make
|
According to the error message, libfam.la doesn't exist. But:
Code: | jethro root 09:02:24 # ls -l /usr/lib/libfam*
-rw-r--r-- 1 root root 39706 Feb 11 02:38 /usr/lib/libfam.a
-rwxr-xr-x 1 root root 717 Feb 11 02:38 /usr/lib/libfam.la
lrwxrwxrwx 1 root root 15 Feb 11 02:38 /usr/lib/libfam.so -> libfam.so.0.0.0
lrwxrwxrwx 1 root root 15 Feb 11 02:38 /usr/lib/libfam.so.0 -> libfam.so.0.0.0
-rwxr-xr-x 1 root root 27632 Feb 11 02:38 /usr/lib/libfam.so.0.0.0
|
Any bright ideas? _________________ If Bill Gates had a penny for each time Windows crashed...
Wait a minute! He does! |
|
Back to top |
|
|
sethleon Guru
Joined: 14 Dec 2003 Posts: 398 Location: Germany
|
Posted: Wed Feb 11, 2004 8:41 am Post subject: |
|
|
finally in your error it said "...libfam.la' is not a valid libtool archiv"
so i remembered a similar error while emergin' a KDE part concerning libGL.la,
i just moved the file libGL.la into /root
then tried to emerge the KDE part again, it succeeded,
then i re-moved, moved libGL.la again to /usr/lib/
so just give a try to the following:
first look that libfam.la it is not used by anyone
Code: | fuser -v /usr/local/lib/libfam.la |
if no one is using it, go on as follows:
Code: | cp /usr/local/lib/libfam.la /root
rm /usr/local/lib/libfam.la
emerge kdebase
cp /root/libfam.la /usr/local/lib/libfam.la |
if it worked you still could leave the libfam.la in your root folder,
if the error occurs again _________________ Mess with the best, die like the rest. |
|
Back to top |
|
|
|