Date: Thu, 2 Jun 2005 16:38:11 -0400 (EDT) From: Daniel Eischen <deischen@freebsd.org> To: Hajimu UMEMOTO <ume@freebsd.org> Cc: nectar@freebsd.org, des@des.no, standards@freebsd.org, current@freebsd.org, freebsd-arch@freebsd.org Subject: Re: [CFR] correct type of addrinfo.ai_addrlen and netent.n_net Message-ID: <Pine.GSO.4.43.0506021634470.15736-100000@sea.ntplx.net> In-Reply-To: <ygey89s8pzp.wl%ume@mahoroba.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 3 Jun 2005, Hajimu UMEMOTO wrote: > Hi, > > >>>>> On Thu, 2 Jun 2005 15:59:07 -0400 (EDT) > >>>>> Daniel Eischen <deischen@freebsd.org> said: > > > Ultimately, I wish to correct struct addrinfo, too. Since correcting > > getnetbyaddr(3) breaks ABI compatibility after all, it seems storange > > to me to leave struct addrinfo alone as is. It is better to take this > > occasion to correct struct addrinfo as well. > > This breakage is only on 64 bit arch. The influence will grow as 64 > > bit arch spreads. So, I believe it should be done as soon as > > possible. > > deischen> Just leave it alone for now. > > Please clarify what you mean for `it'. Which are you mean only struct > addrinfo issue or both? struct addrinfo. I am under the assumption that getnetbyaddr() only breaks libc compat which has already been bumped. Changing that has no effect on other libraries, right? > > deischen> When symbol versioning comes, you should be able to remove > deischen> the padding without bumping library versions and producing > deischen> imcompatibilities. > > It's curious. Is there any plan to provide symbol versioning? I recall seeing some mention of it (by kan@ ?) on some site or posting talking about the recent BSDCan. -- DE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.43.0506021634470.15736-100000>