View previous topic :: View next topic |
Author |
Message |
Dalrain Tux's lil' helper
Joined: 02 Jul 2002 Posts: 136 Location: Wooster, OH USA
|
Posted: Mon Feb 10, 2003 5:39 pm Post subject: fam-oss e-build broken? |
|
|
Hello,
Started out with an update this morning to my system and another system of mine that are building on the stable tree, and I'm getting this same error consistently:
Code: |
/usr/sbin/ebuild.sh: line 28: /usr/portage/app-admin/fam-oss/files/fam-oss-2.6.9-r1-gcc3.patch: No such file or directory
!!! ERROR: app-admin/fam-oss-2.6.9-r1 failed.
!!! Function src_unpack, Line 28, Exitcode 1
!!! (no error message)
|
Anyone else seeing this? |
|
Back to top |
|
|
jjames n00b
Joined: 25 Oct 2002 Posts: 2 Location: Los Angeles
|
|
Back to top |
|
|
Morto n00b
Joined: 02 Feb 2003 Posts: 27
|
Posted: Mon Feb 10, 2003 7:53 pm Post subject: |
|
|
>>> Unpacking fam-2.6.9.tar.gz
* Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is:
*
* /var/tmp/portage/fam-oss-2.6.9-r1/work/patch
!!! ERROR: app-admin/fam-oss-2.6.9-r1 failed.
!!! Function epatch, Line 163, Exitcode 0
!!! Cannot find $EPATCH_SOURCE!
|
|
Back to top |
|
|
Dalrain Tux's lil' helper
Joined: 02 Jul 2002 Posts: 136 Location: Wooster, OH USA
|
Posted: Mon Feb 10, 2003 8:20 pm Post subject: |
|
|
It appears to have been a temporary problem, it's been fixed now.
Not sure for you there Morto though...rsync and try again? |
|
Back to top |
|
|
MIT_Service Guru
Joined: 29 Nov 2002 Posts: 355
|
Posted: Mon Feb 10, 2003 9:37 pm Post subject: |
|
|
same as Morto here...
rsynced several times - different mirrors
even deleted the whole fam-oss dir and rsynced again |
|
Back to top |
|
|
Kurk n00b
Joined: 29 Jan 2003 Posts: 14 Location: Utrecht, Netherlands
|
Posted: Mon Feb 10, 2003 9:45 pm Post subject: |
|
|
I have the same problem as Morto. This is not fixed yet
Last edited by Kurk on Mon Feb 10, 2003 9:51 pm; edited 1 time in total |
|
Back to top |
|
|
Silhouette n00b
Joined: 23 Aug 2002 Posts: 46
|
Posted: Mon Feb 10, 2003 9:51 pm Post subject: |
|
|
This is not good. A things depend on this (like gnome 2.2). I've tried rsyncing over and over, but to no avail. Hopefully this is figured out soon or otherwise a lot of people are going to be disappointed (me included) |
|
Back to top |
|
|
Woland Apprentice
Joined: 02 Aug 2002 Posts: 248 Location: Russian Jack, Alaska
|
Posted: Mon Feb 10, 2003 9:54 pm Post subject: |
|
|
Same problem as well, but just now, rsyncing worked. So ya'll might want to give it another go. |
|
Back to top |
|
|
Kurk n00b
Joined: 29 Jan 2003 Posts: 14 Location: Utrecht, Netherlands
|
Posted: Mon Feb 10, 2003 10:20 pm Post subject: |
|
|
It worked when i first renamed the old ebuild (without -r1) to the new ebuild, then tried to emerge it (which, of course, failed), ran and tried to emerge the new ebuild. Seems like a file is missing... |
|
Back to top |
|
|
qwkbrnfox Apprentice
Joined: 05 Nov 2002 Posts: 231 Location: Vancouver, BC, Canada
|
Posted: Mon Feb 10, 2003 10:43 pm Post subject: |
|
|
Wow, that's irritating. I choose today to install gentoo to my laptop. Could someone who successfully built fam-oss post the ebuild? It'd be interesting to know if the problem is the ebuild or the package.
Thanks,
qbf |
|
Back to top |
|
|
Woland Apprentice
Joined: 02 Aug 2002 Posts: 248 Location: Russian Jack, Alaska
|
Posted: Mon Feb 10, 2003 11:15 pm Post subject: |
|
|
Here you go, and best of luck:
Code: |
# Copyright 1999-2002 Gentoo Technologies, Inc.
# Distributed under the terms of the GNU General Public License v2
# $Header: /home/cvsroot/gentoo-x86/app-admin/fam-oss/fam-oss-2.6.9-r1.ebuild,v 1.6 2003/02/10 17:22:54 foser Exp $
IUSE=""
inherit libtool eutils
MY_P="${P/-oss/}"
S="${WORKDIR}/${MY_P}"
DESCRIPTION="FAM, the File Alteration Monitor."
SRC_URI="ftp://oss.sgi.com/projects/fam/download/${MY_P}.tar.gz"
HOMEPAGE="http://oss.sgi.com/projects/fam/"
KEYWORDS="x86 ~ppc ~alpha ~sparc"
SLOT="0"
LICENSE="GPL-2 LGPL-2.1"
DEPEND=">=sys-devel/perl-5.6.1"
RDEPEND=">=net-nds/portmap-5b-r6"
src_unpack() {
unpack ${MY_P}.tar.gz
cd ${S}
epatch ${DISTDIR}/dnotify.patch || die
epatch ${FILESDIR}/${P}-gcc3.patch || die
# should fix the sigqueue overflow problems
cd ${S}/fam
mv Makefile.am Makefile.am.old
sed -e "s:fam_LDADD =:fam_LDADD = -lrt -lpthread:" Makefile.am.old > Makefile.am
elibtoolize
export WANT_AUTOCONF_2_5=1
export WANT_AUTOMAKE_1_5=1
automake --add-missing
aclocal
autoconf
autoheader
}
src_install() {
cp fam/fam.conf fam/fam.conf.old
sed s:"local_only = false":"local_only = true":g fam/fam.conf.old >fam/fam.conf
make DESTDIR=${D} \
install || die
exeinto /etc/init.d
doexe ${FILESDIR}/fam
dodoc AUTHORS COPYING ChangeLog INSTALL NEWS TODO README*
}
|
Built sucessfully about 40 min. ago as part of Gnome 2.2 upgrade. |
|
Back to top |
|
|
qwkbrnfox Apprentice
Joined: 05 Nov 2002 Posts: 231 Location: Vancouver, BC, Canada
|
Posted: Mon Feb 10, 2003 11:24 pm Post subject: |
|
|
Thanks Woland. The ebuilds seem to be the same. So much for an easy fix! I suppose the problem is with the actual package. Any idea which mirror you pulled the sources from? |
|
Back to top |
|
|
Woland Apprentice
Joined: 02 Aug 2002 Posts: 248 Location: Russian Jack, Alaska
|
|
Back to top |
|
|
qwkbrnfox Apprentice
Joined: 05 Nov 2002 Posts: 231 Location: Vancouver, BC, Canada
|
Posted: Tue Feb 11, 2003 12:17 am Post subject: |
|
|
Thanks to Woland, the damned thing compiled. For some reason, I had to put http://gentoo.oregonstate.edu/distfiles/dnotify.patch in /usr/portage/distfiles/dnotify.patch
Then emerge fam-oss. I can't imagine why it wasn't fetching the dnotify patch. Maybe it was already there for some people? Maybe another package would fetch it...who knows.
qbf |
|
Back to top |
|
|
jda n00b
Joined: 11 Feb 2003 Posts: 5
|
Posted: Tue Feb 11, 2003 1:25 am Post subject: |
|
|
I was also having problems with this package as a dependency for KDE (and others) and got around it thusly. After a failed install (where the files had been untar'd but not successfully installed) I found "dnotify.patch" with
Code: | / # find . -name dnotify.patch
./usr/portage/app-admin/fam-oss/files/dnotify.patch
/ # |
I then edited the ebuild file /usr/portage/app-admin/fam-oss/fam-oss-2.6.9-r1.ebuild, at line 27 to be:
Code: | epatch /usr/portage/app-admin/fam-oss/files/dnotify.patch || die |
The package emerged fine then. I'm sure the next 'emerge sync' will undo the changes, but it worked and emerged without errors for now. So umm, where do I submit bugs again? <--- new to gentoo |
|
Back to top |
|
|
TripKnot Apprentice
Joined: 29 May 2002 Posts: 213
|
Posted: Tue Feb 11, 2003 1:26 am Post subject: |
|
|
This is a real easy fix.
Change:
Code: | epatch ${DISTDIR}/dnotify.patch || die
epatch ${FILESDIR}/${P}-gcc3.patch || die |
To:
Code: | epatch ${FILESDIR}/dnotify.patch || die
epatch ${FILESDIR}/${P}-gcc3.patch || die
|
|
|
Back to top |
|
|
Silhouette n00b
Joined: 23 Aug 2002 Posts: 46
|
Posted: Tue Feb 11, 2003 1:33 am Post subject: |
|
|
qwkbrnfox wrote: | Thanks to Woland, the damned thing compiled. For some reason, I had to put http://gentoo.oregonstate.edu/distfiles/dnotify.patch in /usr/portage/distfiles/dnotify.patch
Then emerge fam-oss. I can't imagine why it wasn't fetching the dnotify patch. Maybe it was already there for some people? Maybe another package would fetch it...who knows.
qbf |
I can verify. That's all that was needed. I have no idea why they would do a thing like that. |
|
Back to top |
|
|
Dalrain Tux's lil' helper
Joined: 02 Jul 2002 Posts: 136 Location: Wooster, OH USA
|
Posted: Tue Feb 11, 2003 1:37 am Post subject: |
|
|
I'll also verify from my end that everything must hav ebeen fetched, as it didn't requireany additional work from me. I guess it was a mirror syncing issue. Hope everyone gets this sorted out...it does hold off some upgrading when it doesn't work. |
|
Back to top |
|
|
qwkbrnfox Apprentice
Joined: 05 Nov 2002 Posts: 231 Location: Vancouver, BC, Canada
|
Posted: Tue Feb 11, 2003 1:59 am Post subject: |
|
|
jda wrote: |
The package emerged fine then. I'm sure the next 'emerge sync' will undo the changes, but it worked and emerged without errors for now. So umm, where do I submit bugs again? <--- new to gentoo |
Sorry, jda, I've already done it. Check it out, and modify if you want.
qbf |
|
Back to top |
|
|
jda n00b
Joined: 11 Feb 2003 Posts: 5
|
Posted: Tue Feb 11, 2003 2:16 am Post subject: Tree supposedly fixed... |
|
|
This bug notice claims it is fixed in the tree, but I guess it's taking a while to propagate to portage mirrors. |
|
Back to top |
|
|
MIT_Service Guru
Joined: 29 Nov 2002 Posts: 355
|
Posted: Tue Feb 11, 2003 10:00 am Post subject: |
|
|
It's fixed for me now (simple rsync and compile).
Now I've got only one broken ebuild to fix before i can compile Gnome 2.2 |
|
Back to top |
|
|
Inf7 n00b
Joined: 12 Feb 2003 Posts: 16
|
Posted: Sun Mar 23, 2003 10:51 am Post subject: |
|
|
Well I keep getting this error and it really is stoping all progress of emerging gnome to my 2 computers. What is the real fix for this? I have tried editing files to make it work and it still fails |
|
Back to top |
|
|
Inf7 n00b
Joined: 12 Feb 2003 Posts: 16
|
Posted: Mon Mar 24, 2003 12:34 am Post subject: |
|
|
The people on the #gentoo irc chan told me to recompile gcc with USE=-static and that worked
viva gentoo! |
|
Back to top |
|
|
|