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