Date: Fri, 8 Mar 2002 16:26:33 -0600 From: "David W. Chapman Jr." <dwcjr@inethouston.net> To: "Mike Barcroft" <mike@FreeBSD.org> Cc: "Robert Watson" <rwatson@FreeBSD.org>, "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: <02b901c1c6f0$4d911910$d800a8c0@dwcjr> References: <20020308145953.GA62875@leviathan.inethouston.net> <Pine.NEB.3.96L.1020308105837.71766F-100000@fledge.watson.org> <20020308161716.GA65905@leviathan.inethouston.net> <20020308171721.Q81803@espresso.q9media.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Hmm. This should be non-fatal in any event, but which header does it > include to get it's htons() and htonl() prototypes? <netinet/in.h>, > <arpa/inet.h>, or <sys/param.h>? > > > 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. From reading all the posts, I believe the solution has been to manually modify the kde port to do this. > > This is almost completely bogus. I recently saw a PR of similar > bogusness. > This was most likely quoted from the same person who submitted the pr you read. I'm not sure how I can help you because I'm not a programmer, but I'd be happy to boot into -current and give you any information you need if there is actually a problem(I don't totally understand what it is at the moment). 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?02b901c1c6f0$4d911910$d800a8c0>