Skip site navigation (1) Skip section navigation (2)

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

From: Alfred Perlstein <bright(at)wintelcom(dot)net>
To: Larry Rosenman <ler(at)lerctr(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers List <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: LOCK Fixes/Break on FreeBSD 4.2-STABLE
Date: 2000-11-29 04:46:43
Message-ID: 20001128204643.X8051@fw.wintelcom.net (view raw or flat)
Thread:
Lists: pgsql-hackers
* Larry Rosenman <ler(at)lerctr(dot)org> [001128 20:44] wrote:
> * Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> [001128 22:31]:
> > Larry Rosenman <ler(at)lerctr(dot)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(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."

In response to

Responses

pgsql-hackers by date

Next:From: Larry RosenmanDate: 2000-11-29 04:48:51
Subject: Re: Re: LOCK Fixes/Break on FreeBSD 4.2-STABLE
Previous:From: Tom LaneDate: 2000-11-29 04:44:37
Subject: Re: Initdb not running on beos

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group