Re: Build failure on m68k and ia64: inconsistent operand constraints in an `asm' - Mailing list pgsql-ports

From Peter Eisentraut
Subject Re: Build failure on m68k and ia64: inconsistent operand constraints in an `asm'
Date
Msg-id 200406101204.20605.peter_e@gmx.net
Whole thread Raw
In response to Build failure on m68k and ia64: inconsistent operand constraints in an `asm'  (Martin Pitt <martin@piware.de>)
Responses Re: Build failure on m68k and ia64: inconsistent operand constraints in an `asm'  (Martin Pitt <martin@piware.de>)
List pgsql-ports
Martin Pitt wrote:
> A Debian porter suggested that "1"(*lock) is an obsolete syntax and
> should be replaced by "m"(*lock) in both cases; however, I would like
> to get a second opinion about this.

If it were obsolete syntax, then it would still work.  As it is, they
are treating it as invalid syntax, which is really a bad move on their
part.


pgsql-ports by date:

Previous
From: Martin Pitt
Date:
Subject: Re: Build failure on m68k and ia64: inconsistent operand constraints in an `asm'
Next
From: Martin Pitt
Date:
Subject: Re: Build failure on m68k and ia64: inconsistent operand constraints in an `asm'