Date: Mon, 14 May 2001 09:01:55 -0700 From: John Merryweather Cooper <jmcoopr@webmail.bmi.net> To: Dave Uhring <duhring@charter.net> Cc: Andrew Reilly <areilly@bigpond.net.au>, freebsd-stable@FreeBSD.ORG Subject: Re: make world still broken around krb4_version bug--when will the patch reach stable? Message-ID: <3B000173.493E7D67@webmail.bmi.net> References: <auto-000002964244@dc-mx03.cluster1.charter.net> <01051405115300.00357@dave>
next in thread | previous in thread | raw e-mail | index | archive | help
Dave Uhring wrote: > > On Monday 14 May 2001 01:26, Andrew Reilly wrote: > > On 13 May, Dave Uhring wrote: > > > On Sunday 13 May 2001 07:03 pm, Andrew Reilly wrote: > > >> On Fri, May 11, 2001 at 08:52:25PM -0700, John Merryweather Cooper > wrote: > > >> > I've been cvsuping all day and repeatedly trying to make world but > > >> > no dice--things collapse around the krb4_version bug (char *, const > > >> > char * clash). I know a patch was supposed to have been committed, > > >> > but to date I haven't seen it--at least on cvsup8.FreeBSD.org. > > >> > > >> Me too. Now the 14th. cvsup.au.FreeBSD.org. > > > > > > Nothing wrong with the repositories at cvsup2 and cvsup5 WRT subject > > > problem. I updated this afternoon 4_STABLE and buildworld proceeded > > > without error. The fxp and miibus drivers seem to have a problem, > > > however. > > > > I just tried cvsup2.au.freebsd.org, and that didn't help either. > > There isn't a cvsup?.au.freebsd.org for ?>3. > > > > What are the usual propagation times to the Australian mirrors? I > > would have thought that it would be much shorter than three days. > > That kind of argues for a mis-configuration on my system > > somewhere. I can't think where, though. I haven't touched my > > make.conf recently. I've just done a make clean (in /usr/src), so > > I don't think that it's a clash with something left behind. Could > > it be a clash with an installed header file? If it is, how can I > > work around that? > > > > FWIW, here's the end of the make buildworld output: > > > > cc -O -pipe -march=pentiumpro > > -I/usr/src/kerberos5/lib/libasn1/../../../crypto/heimdal/include > > -I/usr/src/kerberos5/lib/libasn1/../../../crypto/heimdal/lib/asn1 > > -I/usr/src/kerberos5/lib/libasn1/../../../crypto/heimdal/lib/roken > > -I/usr/src/kerberos5/lib/libasn1/../../include > > -I/usr/obj/usr/src/kerberos5/lib/libasn1 -Wall > > -I/usr/src/kerberos5/lib/libasn1/../../include > > -I/usr/src/kerberos5/lib/libasn1/../../include -DHAVE_CONFIG_H > > -DKRB5_KRB4_COMPAT -DKRB4 -DINET6 -static -o make-print-version /usr/src/ > > erberos5/lib/libasn1/../../../crypto/heimdal/lib/roken/make-print-version > >.c In file included from > > /usr/src/kerberos5/lib/libasn1/../../../crypto/heimdal/lib/roken/make-pri > >nt-version.c:49: /usr/src/kerberos5/lib/libasn1/../../include/version.h:3: > > conflicting types for `krb4_version' > > /usr/src/kerberos5/lib/libasn1/../../../crypto/heimdal/lib/roken/make-pri > >nt-version.c:47: previous declaration of `krb4_version' *** Error code 1 > > > > Stop in /usr/src/kerberos5/lib/libasn1. > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > Stop in /usr/src. > > The only way I have found that works is to rm -rf /usr/src and re-install > the source tree from my latest CD, then cvsup to stable. Are you sure that > your tag line is correct and that you haven't accidently installed the > current source tree? Do you have src all and crypto all in your cvsupfile? > Can't put a copy of mine up right now, my NIC driver is fouled up and I'm > running Solaris. > I don't know about AR, but my stable cvsup file is bog-stock. For some reason, it appears that cvsup has not propogated the K4/K5 patch to my system. Like AR, I'd rather not delete my /usr/src tree if at all possible as the re-download is likely to be painful--and 4.3-RELEASE CD-ROM doesn't even exist yet. Three possibilities seem to suggest themselves: 1) bug in the way patch was committed causing some cvsup sites to pick it up and some not to; 2) bug in some cvsup sites' configuration that causes them to not propagate some commits properly; 3) bug in cvsup client. I'm open to other suggestions, and I'll do the rm -rfd /usr/src if I absolutely have to, but I'd rather avoid it. jmc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B000173.493E7D67>