From owner-freebsd-current Fri Mar 8 8:43:48 2002 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 811D537B443; Fri, 8 Mar 2002 08:43:16 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id g28GgoD73719; Fri, 8 Mar 2002 11:42:50 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Fri, 8 Mar 2002 11:42:50 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Peter Pentchev Cc: "David W. Chapman Jr." , Murray Stokely , developers@FreeBSD.org, current@FreeBSD.org, re@FreeBSD.org, portmgr@FreeBSD.org Subject: Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) In-Reply-To: <20020308182856.C303@straylight.oblivion.bg> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sounds to me like there are fixes in the pipeline from Mike and Thomas. Hopefully they'll get that committed in the next day or two so that KDE can be happy on -CURRENT before the snapshot. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Fri, 8 Mar 2002, Peter Pentchev wrote: > On Fri, Mar 08, 2002 at 10:17:16AM -0600, David W. Chapman Jr. wrote: > > > > currently kde doesn't work due to binuntils update. It may work now > > > > after the most recent binutils update, but we have to recompile kde to > > > > see that I believe, andkdelibs cannot be compiled which builds > > > > kde-config which the rest of the kde meta-ports try to run. > [snip] > > I'm not the only one that is experiencing it either, here is what I > > was told by Alan Eldridge > > > > > > On Tue, Mar 05, 2002 at 05:26:27PM -0600, David W. Chapman Jr. wrote: > > >When I try to build kdelibs2 I get the following under recent > > >-current builds > > > > > >,.deps/kextsock.pp -c kextsock.cpp -fPIC -DPIC -o .libs/kextsock.o > > >kextsock.cpp: In method `struct kde_addrinfo * > > >KExtendedSocketLookup::results()' > > >: > > >kextsock.cpp:294: implicit declaration of function `int __htons(...)' > > >kextsock.cpp:353: implicit declaration of function `int __htonl(...)' > > > > Yes. Recent changes to netinet/in.h have made it require the inclusion > > of arpa/inet.h. As well, arpa/inet.h must include netinet/in.h. IOW, > > each > > of these files must #include the other in order to work correctly. > > > > As you might guess, this is a less than desirable situation. A > > #includes > > B and B #includes A is a very bad arrangement. However, unless both > > files > > are overhauled, that is what will have to happen. > > FWIW, Alan filed a PR about that - bin/35598. > > G'luck, > Peter > > -- > Peter Pentchev roam@ringlet.net roam@FreeBSD.org > PGP key: http://people.FreeBSD.org/~roam/roam.key.asc > Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 > What would this sentence be like if it weren't self-referential? > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message