Date: Fri, 8 Mar 2002 18:28:56 +0200 From: Peter Pentchev <roam@ringlet.net> To: Robert Watson <rwatson@FreeBSD.org>, "David W. Chapman Jr." <dwcjr@inethouston.net>, Murray Stokely <murray@FreeBSD.org>, developers@FreeBSD.org, current@FreeBSD.org, re@FreeBSD.org, portmgr@FreeBSD.org Subject: Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Message-ID: <20020308182856.C303@straylight.oblivion.bg> In-Reply-To: <20020308161716.GA65905@leviathan.inethouston.net>; from dwcjr@inethouston.net on Fri, Mar 08, 2002 at 10:17:16AM -0600 References: <20020308145953.GA62875@leviathan.inethouston.net> <Pine.NEB.3.96L.1020308105837.71766F-100000@fledge.watson.org> <20020308161716.GA65905@leviathan.inethouston.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--vtzGhvizbBRQ85DL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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.=20 [snip] > I'm not the only one that is experiencing it either, here is what I=20 > was told by Alan Eldridge <alane@geeksrus.net> >=20 >=20 > 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(...)' >=20 > 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,=20 > each > of these files must #include the other in order to work correctly. >=20 > As you might guess, this is a less than desirable situation. A=20 > #includes > B and B #includes A is a very bad arrangement. However, unless both=20 > files > are overhauled, that is what will have to happen. FWIW, Alan filed a PR about that - bin/35598. G'luck, Peter --=20 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? --vtzGhvizbBRQ85DL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjyI5sgACgkQ7Ri2jRYZRVPvcACeI3x+hLng/dRwOwBbi6iyoGro W+cAoK6F6kQysPBxtIg2LiouQ/V42x8+ =6S22 -----END PGP SIGNATURE----- --vtzGhvizbBRQ85DL-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020308182856.C303>