Package: iaxclient
Version: 2.0.2-2
Severity: serious

There was an error while trying to autobuild your package:

> Automatic build of iaxclient_2.0.2-2 on lebrun by sbuild/sparc 98
> Build started at 20080413-0622

[...]

> ** Using build dependencies supplied by package:
> Build-Depends: autotools-dev, debhelper (>= 4.0.0), dpatch, libgsm1-dev, 
> libgtk2.0-dev, libogg-dev, libspeex-dev, libspeexdsp-dev, libtheora-dev, 
> libwxgtk2.6-dev, portaudio19-dev

[...]

>       mv -f $depbase.Tpo $depbase.Plo
>  sparc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I../../lib 
> -I../../lib/portmixer/px_common -pthread -I../../lib/libiax2/src -DLIBIAX 
> -pthread -Wall -Wextra -Wno-unused-parameter -Wpointer-arith 
> -DLIBVER=\"2.0.2\" -I/usr/include -Wall -g -D_REENTRANT --std=gnu99 -O2 -MT 
> ringbuffer.lo -MD -MP -MF .deps/ringbuffer.Tpo -c ../../lib/ringbuffer.c  
> -fPIC -DPIC -o .libs/ringbuffer.o
> ../../lib/ringbuffer.c:124:11: error: #error Memory barriers are not defined 
> on this system. You can still compile by defining ALLOW_SMP_DANGERS, but SMP 
> safety will not be guaranteed.
> ../../lib/ringbuffer.c: In function 'rb_GetRingBufferReadAvailable':
> ../../lib/ringbuffer.c:191: warning: implicit declaration of function 
> 'rb_ReadMemoryBarrier'
> ../../lib/ringbuffer.c: In function 'rb_AdvanceRingBufferWriteIndex':
> ../../lib/ringbuffer.c:249: warning: implicit declaration of function 
> 'rb_WriteMemoryBarrier'
> make[3]: *** [ringbuffer.lo] Error 1
> make[3]: Leaving directory `/build/buildd/iaxclient-2.0.2/objs/lib'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/build/buildd/iaxclient-2.0.2/objs'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/build/buildd/iaxclient-2.0.2/objs'
> make: *** [build-arch-stamp] Error 2
> dpkg-buildpackage: failure: debian/rules build gave error exit status 2

A full build log can be found at:
http://buildd.debian.org/build.php?arch=sparc&pkg=iaxclient&ver=2.0.2-2




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to