Gentoo Archives: gentoo-dev

From: Michael Rash <mbr@××××××××××.org>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] cvs ebuild problem?
Date: Mon, 16 Feb 2004 22:12:04
Message-Id: 20040216221159.GA17837@orthanc.gambrl01.md.comcast.net
In Reply to: Re: [gentoo-dev] cvs ebuild problem? by Jeremy Huddleston
1 Ok, I'll try putting this on bugs.gentoo.org. BTW, I unmerged
2 app-crypt/kth-krb and then tried emerging cvs again to no avail.
3
4 --Mike
5
6
7
8 On Feb 16, 2004, Jeremy Huddleston wrote:
9
10 > This should prolly go over o bugzilla... you'll have abetter chance of
11 > getting it taken care of there... http://bugs.gentoo.org
12 >
13 > On Tue, 2004-02-17 at 02:25, Chris Smith wrote:
14 > > On Monday 16 February 2004 20:51, Michael Rash wrote:
15 > > > client.c: In function `start_tcp_server':
16 > > > client.c:4028: warning: passing arg 6 of `krb_sendauth' discards qualifiers
17 > > > from pointer target type client.c:4028: error: incompatible type for
18 > > > argument 10 of `krb_sendauth' make[2]: *** [client.o] Error 1
19 > > > make[2]: *** Waiting for unfinished jobs....
20 > > > make[2]: Leaving directory
21 > > > `/usr/local/tmp/portage/cvs-1.11.11/work/cvs-1.11.11/src' make[1]: ***
22 > > > [all-recursive] Error 1
23 > > > make[1]: Leaving directory
24 > > > `/usr/local/tmp/portage/cvs-1.11.11/work/cvs-1.11.11' make: *** [all] Error
25 > > > 2
26 > >
27 > > Hey Michael,
28 > >
29 > > Looks like it's a problem with CVS's kerberos support. Do you have the
30 > > "kerberos" use flag set? If you don't need kerberos support, try this:
31 > >
32 > > USE="-kerberos" emerge cvs
33 > >
34 > > Which will build cvs without kerberos support.
35 > >
36 > > Hope that helps,
37 > > Cheers,
38 > > Chris.
39 > >
40 > >
41 > > --
42 > > gentoo-dev@g.o mailing list
43 > >
44
45
46 --Mike
47
48 Michael Rash
49 http://www.cipherdyne.org/
50 Key fingerprint = 53EA 13EA 472E 3771 894F AC69 95D8 5D6B A742 839F
51
52 --
53 gentoo-dev@g.o mailing list

Replies

Subject Author
Re: [gentoo-dev] cvs ebuild problem? Michael Rash <mbr@××××××××××.org>