Re: compile error: c_lock assembler

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: compile error: c_lock assembler
Date: 2001-08-29 13:55:05
Message-ID: Pine.LNX.4.30.0108291554410.677-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Karel Zak writes:

> Hmm, I answer it oneself. A problem is in the file
> src/backend/storage/buffer/s_lock.c at line 231:
>
> #if defined(__mips__) || !defined(__sgi)
> ^^^^^
>
> this condition is true for all __mips__ or for *everythig* what is
> not __sgi__ (so i386 too). It's the typical 'OR' problem :-)

Yup. It's already fixed. Sorry.

--
Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2001-08-29 14:38:00 Re: getting the oid for a new tuple in a BEFORE trigger
Previous Message Karel Zak 2001-08-29 13:26:03 Re: compile error: c_lock assembler