Re: Re: LOCK Fixes/Break on FreeBSD 4.2-STABLE

* Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> [001205 07:14] wrote:
> Alfred Perlstein <bright(at)wintelcom(dot)net> writes:
> > Anyhow, to address the problem I've removed struct mount from
> > userland visibility in both FreeBSD 5.x (current) and FreeBSD 4.x
> > (stable).
>
> That might fix things on your box, but we can hardly rely on it as an
> answer for everyone running FreeBSD :-(.
>
> Anyway, I've already worked around the problem by rearranging the PG
> headers so that plperl doesn't need to import s_lock.h ...

Well I didn't say it was completely our fault, it's just that we
try pretty hard not to let those types of structs leak into userland
and for us to "steal" something called s_lock from userland, well
that's no good. :)

--
-Alfred Perlstein - [bright(at)wintelcom(dot)net|alfred(at)freebsd(dot)org]
"I have the heart of a child; I keep it in a jar on my desk."