From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: * X-Spam-Status: No, score=1.1 required=5.0 tests=DATE_IN_PAST_12_24,DMARC_NONE, INVALID_DATE,MAILING_LIST_MULTI autolearn=no autolearn_force=no version=4.0.0 Received: from mailgw2.netvision.net.il ([194.90.1.9]) by cvs.gentoo.org with esmtp (Exim 3.30 #1) id 15UZJf-0003e8-00 for gentoo-dev@cvs.gentoo.org; Wed, 08 Aug 2001 13:48:32 -0600 Received: from localhost (ras5-p67.rlz.netvision.net.il [62.0.86.67]) by mailgw2.netvision.net.il (8.9.3/8.9.3) with SMTP id WAA29907 for ; Wed, 8 Aug 2001 22:50:47 +0300 (IDT) Content-Type: text/plain; charset="iso-8859-1" From: Dan Armak To: gentoo-dev@cvs.gentoo.org Subject: Re: [gentoo-dev] Problems compiling gv X-Mailer: KMail [version 1.2] References: <01080723384200.01072@rei> <01080816061303.00611@localhost> <01080816090204.00611@localhost> In-Reply-To: <01080816090204.00611@localhost> MIME-Version: 1.0 Message-Id: <0108082249360B.00611@localhost> Content-Transfer-Encoding: 8bit Sender: gentoo-dev-admin@cvs.gentoo.org Errors-To: gentoo-dev-admin@cvs.gentoo.org X-BeenThere: gentoo-dev@cvs.gentoo.org X-Mailman-Version: 2.0 Precedence: bulk Reply-To: gentoo-dev@cvs.gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux development list List-Unsubscribe: , List-Archive: Date: Wed Aug 8 13:49:02 2001 X-Original-Date: Wed, 8 Aug 2001 22:49:36 +0300 X-Archives-Salt: 3f1c1801-518a-4a9e-8f80-94e3c534e434 X-Archives-Hash: 6347e0462ba0ea8bc70b733d35fe6cb3 On Wednesday 08 August 2001 16:09, you wrote: > On Wednesday 08 August 2001 16:06, you wrote: > > On Wednesday 08 August 2001 15:31, you wrote: > > > On Wednesday 08 August 2001 17:32, you wrote: > > > > Dan Armak escreveu (Wed, Aug 08, 2001 at 10:45:57AM +0300): > > > > > OK, I've changed the gv ebuild, though it's rather a guess, but > > > > > it's the only thing I can think of. > > > > > If that doesn't help after rsync, could you try to extract and > > > > > install the gv sources yourself, and see if that works? > > > > > A final question: after the make error, emerge shuold say it failed > > > > > to run something - what's that something? I want to know if it > > > > > failed to compile or to install. > > > > > > > > How do I do a clean rsync? > > > > > > There's no such thing. Did I mention such a thing? > > > > > > > bash-2.04# emerge --clean rsync > > > > !!! Error: --clean is an invalid option. > > > > > > > > bash-2.04# emerge rsync clean > > > > !!! Error: clean does not exist or is an invalid command-line > > > > option. > > > > > > > > Ok, I did a simple emerge rsync. Same error when emerging gv: > > > > > > > > make[1]: *** No rule to make target `gv.man', needed by `gv._man'. > > > > Stop. make[1]: Leaving directory > > > > `/usr/portage/tmp/portage/gv-3.5.8/work/gv-3.5.8/source' make: *** > > > > [all] Error 2 > > > > > > > > !!! ERROR: the make command did not complete successfully. > > > > !!! ("make") > > > > !!! Since this is a critical task, ebuild will be stopped. > > > > > > > > !!! emerge aborting on /usr/portage/app-text/gv/gv-3.5.8.ebuild . > > > > > > > > I downloaded the sources with ebuild gv fetch, and got the same error > > > > when compiling. > > > > > > I didn't really expect the problem to be in the ebuild anyway. > > > This all seems very strange, and I can't do much because I can't > > > recreate the problem. If you could send me the entire compile output it > > > might help, and then again it might not. I just don't know what to say > > > :-( > > > > > > One thing I *can* do is simply disable the makefile's operation on the > > > manpage. The manpage is actually distibuted pre-compiled (not latex > > > source or something), so all the makefile does is add a .1 extension > > > and install it. So I'll do that now. Wait a couple of hours after this > > > post, emerge rsync and try again. > > > > I'm committing to cvs now and it *should* do it. Make sure emerge rsync > > updates the gv ebuild, I don't know how much time it may take for the new > > version to be available via rsync. > > > > In case even this fails, I think there's a slightly newer version of gv > > and I'm going to make an ebuild for that now. > > Turns out there isn't a newer version - only rumours. Oh well. But my last > cvs update might work :-) > Did it work?