* Larry Rosenman <[EMAIL PROTECTED]> [001128 20:44] wrote:
> * Tom Lane <[EMAIL PROTECTED]> [001128 22:31]:
> > Larry Rosenman <[EMAIL PROTECTED]> writes:
> > > The last batch of commits break on FreeBSD 4.2-STABLE.
> > > /usr/include/machine/lock.h:148: conflicting types for `s_lock'
> > > ../..
My offer stands for you as well, if you'd like an account
on this P-III 600E, you are welcome to one...
LER
* Alfred Perlstein <[EMAIL PROTECTED]> [001128 22:46]:
> * Larry Rosenman <[EMAIL PROTECTED]> [001128 20:44] wrote:
> > * Tom Lane <[EMAIL PROTECTED]> [001128 22:31]:
> > > Larry Rosenman <
* Larry Rosenman <[EMAIL PROTECTED]> [001128 20:52] wrote:
> My offer stands for you as well, if you'd like an account
> on this P-III 600E, you are welcome to one...
I just remebered my laptop in the other room, it's a pretty recent 4.2.
I'll give it shot.
Yes, it's possible to forget about a
* Tom Lane <[EMAIL PROTECTED]> [001128 23:03]:
> Larry Rosenman <[EMAIL PROTECTED]> writes:
> >> We've called that routine s_lock for a *long* time, so it seems
> >> like there must be some factor involved that I don't see just yet...
>
> > Didn't your commit message say something about the TAS a
* Alfred Perlstein <[EMAIL PROTECTED]> [001128 22:55]:
> * Larry Rosenman <[EMAIL PROTECTED]> [001128 20:52] wrote:
> > My offer stands for you as well, if you'd like an account
> > on this P-III 600E, you are welcome to one...
>
> I just remebered my laptop in the other room, it's a pretty recen
* Tom Lane <[EMAIL PROTECTED]> [001128 23:03]:
> Larry Rosenman <[EMAIL PROTECTED]> writes:
> >> We've called that routine s_lock for a *long* time, so it seems
> >> like there must be some factor involved that I don't see just yet...
>
> > Didn't your commit message say something about the TAS a
* Larry Rosenman <[EMAIL PROTECTED]> [001129 19:54]:
> * Tom Lane <[EMAIL PROTECTED]> [001128 23:03]:
> > Larry Rosenman <[EMAIL PROTECTED]> writes:
> > >> We've called that routine s_lock for a *long* time, so it seems
> > >> like there must be some factor involved that I don't see just yet...
>
* Larry Rosenman <[EMAIL PROTECTED]> [001128 20:44] wrote:
> * Tom Lane <[EMAIL PROTECTED]> [001128 22:31]:
> > Larry Rosenman <[EMAIL PROTECTED]> writes:
> > > The last batch of commits break on FreeBSD 4.2-STABLE.
> > > /usr/include/machine/lock.h:148: conflicting types for `s_lock'
> > > ../..
* Alfred Perlstein <[EMAIL PROTECTED]> [001205 04:00]:
> * Larry Rosenman <[EMAIL PROTECTED]> [001128 20:44] wrote:
> > * Tom Lane <[EMAIL PROTECTED]> [001128 22:31]:
> > > Larry Rosenman <[EMAIL PROTECTED]> writes:
> > > > The last batch of commits break on FreeBSD 4.2-STABLE.
> > > > /usr/inclu
Alfred Perlstein <[EMAIL PROTECTED]> 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 :-
* Tom Lane <[EMAIL PROTECTED]> [001205 07:14] wrote:
> Alfred Perlstein <[EMAIL PROTECTED]> 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 c
enman; PostgreSQL Hackers List
Subject: Re: [HACKERS] Re: LOCK Fixes/Break on FreeBSD 4.2-STABLE
Alfred Perlstein <[EMAIL PROTECTED]> writes:
> Anyhow, to address the problem I've removed struct mount from
> userland visibility in both FreeBSD 5.x (current) and FreeBSD 4.x
>
12 matches
Mail list logo
