Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 8 Mar 2002 13:45:13 -0500
From:      Garance A Drosihn <drosih@rpi.edu>
To:        "David W. Chapman Jr." <dwcjr@inethouston.net>, Robert Watson <rwatson@FreeBSD.ORG>
Cc:        "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:  <p05101524b8aeb37beadf@[128.113.24.47]>
In-Reply-To: <20020308161716.GA65905@leviathan.inethouston.net>
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
At 10:17 AM -0600 3/8/02, David W. Chapman Jr. wrote:
>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.
>
>To say that this sucks is an understatement. [...]

>Since the problem is a large one, and any change will not
>happen without a reasonable amount of deliberation, I suggest
>you submit a PR with a patch for kdelibs source tree.

Mike Barcroft, Bruce Evans, and maybe a few others are working
on an update to about eight different include files which should
clear up many of these issues.  I think it would be very desirable
to get this include-file-cleanup patch committed before the snapshot
is done.  The present version of this patch clears up a lot of the
compile-time warnings that come up when doing a buildworld of
current, but it still isn't quite right.

If this current snapshot means more people will be running current,
then I'd hate to see them chasing after compile-time warnings which
are due to the present state of the system include files...

-- 
Garance Alistair Drosehn            =   gad@eclipse.acs.rpi.edu
Senior Systems Programmer           or  gad@freebsd.org
Rensselaer Polytechnic Institute    or  drosih@rpi.edu

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?p05101524b8aeb37beadf>