[test-results] [Bamboo] Asterisk - 1.6.2 > Mac OS X Tiger (10.4) > #22 > Power PC has FAILED. Change made by Paul Belanger.

[Bamboo]

-------------- next part --------------
----------------------------------------------------------------------------
Asterisk - 1.6.2 > Mac OS X Tiger (10.4) > #22 > Power PC failed.
----------------------------------------------------------------------------
Code has been updated by Paul Belanger.
No failed tests found, a possible compilation error.

http://bamboo.asterisk.org/browse/AST162-TIGER-PPC-22/        


--------------
Code Changes
--------------
Paul Belanger (297405):

>Merged revisions 297404 via svnmerge from 
>https://origsvn.digium.com/svn/asterisk/branches/1.4
>
>........
>  r297404 | pabelanger | 2010-12-02 15:01:08 -0500 (Thu, 02 Dec 2010) | 7 lines
>  
>  Resolve compile error under FreeBSD
>  
>  We now set _ASTCFLAGS+=-march=i686 for i386 processors, still allowing ASTCFLAGS
>  to override the setting.
>  
>  Review: https://reviewboard.asterisk.org/r/1043/
>........
>


--------------
Error Summary
--------------
   Package gmime-2.0 was not found in the pkg-config search path.
   Perhaps you should add the directory containing `gmime-2.0.pc'
   to the PKG_CONFIG_PATH environment variable
   No package 'gmime-2.0' found
   Package gmime-2.2 was not found in the pkg-config search path.
   Perhaps you should add the directory containing `gmime-2.2.pc'
   to the PKG_CONFIG_PATH environment variable
   No package 'gmime-2.2' found
   Package gtk+-2.0 was not found in the pkg-config search path.
   Perhaps you should add the directory containing `gtk+-2.0.pc'
   to the PKG_CONFIG_PATH environment variable
   No package 'gtk+-2.0' found
   Package gtk+-2.0 was not found in the pkg-config search path.
   Perhaps you should add the directory containing `gtk+-2.0.pc'
   to the PKG_CONFIG_PATH environment variable
   No package 'gtk+-2.0' found
   No such process
   asterisk.c line 315 (ast_register_file_version): Error obtaining write lock: Invalid argument
   asterisk.c line 317 (ast_register_file_version): Error releasing rwlock: Invalid argument
   asterisk.c line 315 (ast_register_file_version): Error obtaining write lock: Invalid argument
   asterisk.c line 317 (ast_register_file_version): Error releasing rwlock: Invalid argument
   asterisk.c line 315 (ast_register_file_version): Error obtaining write lock: Invalid argument
   asterisk.c line 317 (ast_register_file_version): Error releasing rwlock: Invalid argument
   asterisk.c line 315 (ast_register_file_version): Error obtaining write lock: Invalid argument
   asterisk.c line 317 (ast_register_file_version): Error releasing rwlock: Invalid argument
   asterisk.c line 315 (ast_register_file_version): Error obtaining write lock: Invalid argument
   asterisk.c line 317 (ast_register_file_version): Error releasing rwlock: Invalid argument
   asterisk.c line 315 (ast_register_file_version): Error obtaining write lock: Invalid argument
   asterisk.c line 317 (ast_register_file_version): Error releasing rwlock: Invalid argument
   asterisk.c line 315 (ast_register_file_version): Error obtaining write lock: Invalid argument
   asterisk.c line 317 (ast_register_file_version): Error releasing rwlock: Invalid argument
   asterisk.c line 315 (ast_register_file_version): Error obtaining write lock: Invalid argument
   asterisk.c line 317 (ast_register_file_version): Error releasing rwlock: Invalid argument
   Workaround Bonjour: Unknown error: 0


--
This message is automatically generated by Atlassian Bamboo

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/test-results/attachments/20101202/b5ba8465/attachment.htm