Gentoo Archives: gentoo-dev

From: Dan Armak <ermak@×××××××××××××.il>
To: gentoo-dev@××××××××××.org
Subject: Re: [gentoo-dev] Problems compiling gv
Date: Wed, 08 Aug 2001 13:48:32
Message-Id: 0108082249360B.00611@localhost
In Reply to: Re: [gentoo-dev] Problems compiling gv by Dan Armak
1 On Wednesday 08 August 2001 16:09, you wrote:
2 > On Wednesday 08 August 2001 16:06, you wrote:
3 > > On Wednesday 08 August 2001 15:31, you wrote:
4 > > > On Wednesday 08 August 2001 17:32, you wrote:
5 > > > > Dan Armak escreveu (Wed, Aug 08, 2001 at 10:45:57AM +0300):
6 > > > > > OK, I've changed the gv ebuild, though it's rather a guess, but
7 > > > > > it's the only thing I can think of.
8 > > > > > If that doesn't help after rsync, could you try to extract and
9 > > > > > install the gv sources yourself, and see if that works?
10 > > > > > A final question: after the make error, emerge shuold say it failed
11 > > > > > to run something - what's that something? I want to know if it
12 > > > > > failed to compile or to install.
13 > > > >
14 > > > > How do I do a clean rsync?
15 > > >
16 > > > There's no such thing. Did I mention such a thing?
17 > > >
18 > > > > bash-2.04# emerge --clean rsync
19 > > > > !!! Error: --clean is an invalid option.
20 > > > >
21 > > > > bash-2.04# emerge rsync clean
22 > > > > !!! Error: clean does not exist or is an invalid command-line
23 > > > > option.
24 > > > >
25 > > > > Ok, I did a simple emerge rsync. Same error when emerging gv:
26 > > > >
27 > > > > make[1]: *** No rule to make target `gv.man', needed by `gv._man'.
28 > > > > Stop. make[1]: Leaving directory
29 > > > > `/usr/portage/tmp/portage/gv-3.5.8/work/gv-3.5.8/source' make: ***
30 > > > > [all] Error 2
31 > > > >
32 > > > > !!! ERROR: the make command did not complete successfully.
33 > > > > !!! ("make")
34 > > > > !!! Since this is a critical task, ebuild will be stopped.
35 > > > >
36 > > > > !!! emerge aborting on /usr/portage/app-text/gv/gv-3.5.8.ebuild .
37 > > > >
38 > > > > I downloaded the sources with ebuild gv fetch, and got the same error
39 > > > > when compiling.
40 > > >
41 > > > I didn't really expect the problem to be in the ebuild anyway.
42 > > > This all seems very strange, and I can't do much because I can't
43 > > > recreate the problem. If you could send me the entire compile output it
44 > > > might help, and then again it might not. I just don't know what to say
45 > > > :-(
46 > > >
47 > > > One thing I *can* do is simply disable the makefile's operation on the
48 > > > manpage. The manpage is actually distibuted pre-compiled (not latex
49 > > > source or something), so all the makefile does is add a .1 extension
50 > > > and install it. So I'll do that now. Wait a couple of hours after this
51 > > > post, emerge rsync and try again.
52 > >
53 > > I'm committing to cvs now and it *should* do it. Make sure emerge rsync
54 > > updates the gv ebuild, I don't know how much time it may take for the new
55 > > version to be available via rsync.
56 > >
57 > > In case even this fails, I think there's a slightly newer version of gv
58 > > and I'm going to make an ebuild for that now.
59 >
60 > Turns out there isn't a newer version - only rumours. Oh well. But my last
61 > cvs update might work :-)
62 >
63 Did it work?