Your message dated Sat, 13 Jan 2007 22:15:37 +0100
with message-id <[EMAIL PROTECTED]>
has caused the Debian Bug report #406754,
regarding portaudio19: FTBFS: #error Memory barriers are not defined on this
system.
to be marked as having been forwarded to the upstream software
author(s) [EMAIL PROTECTED]
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Bjorn Roche wrote:
Now, it should work on Linux x86, Linux PPC, Mac OS X
and FreeBSD. On other systems (I don't know what else uses these
ring-buffers, other than Jack/Linux and CoreAudio) it should fail to
compile, but give the user enough info to compile without SMP safety if
they want (by defining ALLOW_SMP_DANGERS, which should probably have a
better name).
Any feedback before I commit (especially from someone familiar with
x86)?
What about other architectures? The Debian portaudio19 package I'm
maintaining together with the Debian VoIP team fails to build on most
architectures. (Reported in Debian BTS #406754[1])
error:
src/common/pa_ringbuffer.c:100:11: error: #error Memory barriers are not
define d on this system. You can still compile by defining
ALLOW_SMP_DANGERS, but SMP safety will not be guaranteed.
PortAudio V19 used to build on all architectures: alpha, amd64, arm,
hppa ,i386, ia64, m68k, mips, mipsel, powerpc, s390 and sparc.
Any solution?
Please, keep CC to [EMAIL PROTECTED] in replies.
Mikael
[1]http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=406754
--- End Message ---
