Re: Re: LOCK Fixes/Break on FreeBSD 4.2-STABLE - Mailing list pgsql-hackers

From Alfred Perlstein
Subject Re: Re: LOCK Fixes/Break on FreeBSD 4.2-STABLE
Date
Msg-id 20001128204643.X8051@fw.wintelcom.net
Whole thread Raw
In response to Re: LOCK Fixes/Break on FreeBSD 4.2-STABLE  (Larry Rosenman <ler@lerctr.org>)
Responses Re: Re: LOCK Fixes/Break on FreeBSD 4.2-STABLE
List pgsql-hackers
* Larry Rosenman <ler@lerctr.org> [001128 20:44] wrote:
> * Tom Lane <tgl@sss.pgh.pa.us> [001128 22:31]:
> > Larry Rosenman <ler@lerctr.org> writes:
> > > The last batch of commits break on FreeBSD 4.2-STABLE. 
> > > /usr/include/machine/lock.h:148: conflicting types for `s_lock'
> > > ../../../src/include/storage/s_lock.h:402: previous declaration of `s_lock'
> > 
> > That's odd.  s_lock has been declared the same way right along in our
> > code; I didn't change it.  Can you see what's changed to cause a
> > conflict where there was none before?
> > 
> >             regards, tom lane
> Other things that may be an issue:
> 
> 1) BINUTILS 2.10.1
> 2) OPENSSL 0.9.6 
> 
> both just MFC'd into FreeBSD recently, but I believe we built until
> tonite. 
> 
> I can make you an account on the box if you'd like....

My signifigant other just installed a fresh copy of 4.2 last night,
unfortunetly the poor box is only a 233mhz, it'll be a while before
we build -stable on it.

However I'm confident I can have a fix within a couple of days.

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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Initdb not running on beos
Next
From: Larry Rosenman
Date:
Subject: Re: Re: LOCK Fixes/Break on FreeBSD 4.2-STABLE