Date: Tue, 11 Oct 2011 14:36:11 -0400 From: Arnaud Lacombe <lacombar@gmail.com> To: Dimitry Andric <dim@freebsd.org> Cc: =?ISO-8859-1?Q?Ren=E9_Ladan?= <rene@freebsd.org>, freebsd-current@freebsd.org, Larry Rosenman <ler@lerctr.org> Subject: Re: System headers with clang? Message-ID: <CACqU3MV9vP%2BVUR%2B2Qpzc4mCS1w3R17yvMGNPT%2BxnsGUiYr8VFQ@mail.gmail.com> In-Reply-To: <4E942FF1.9000805@FreeBSD.org> References: <alpine.BSF.2.00.1110091229550.43656@lrosenman.dyndns.org> <4E942FF1.9000805@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Tue, Oct 11, 2011 at 8:00 AM, Dimitry Andric <dim@freebsd.org> wrote: > On 2011-10-09 19:32, Larry Rosenman wrote: >> >> I had gotten a PR about sysutils/lsof not compiling with clang. =A0I had >> Vic Abell check it out, and the problem is NOT with lsof per se, but >> with the system headers. >> >> Is there a project afoot to update the system headers to make them clang >> compilable? > > The problem isn't that clang can't compile the system headers, but > normally these don't get included from userspace. =A0And they certainly > won't work as expected when you define _KERNEL in userspace, as the lsof > port foolishly does. =A0It probably can't be avoided in such a tool, thou= gh. > #ifdef _KERNEL/#endif protected part of system headers shall NEVER be accessed by userland. It is a fault to have them present in /usr/include. Linux got it right there, all those part are removed upon headers' installation. - Arnaud
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACqU3MV9vP%2BVUR%2B2Qpzc4mCS1w3R17yvMGNPT%2BxnsGUiYr8VFQ>