Re: OS X Compile Bug

[David Sugar]

The first we already seem to already have in the current and/or for the next 
release.  I think there has always been some confusion about the role of 
UCOMMON_EXTENDED and what we were doing for facilitating special case builds 
for deeply embedded services, such as putting sipwitch onto routers.

The second one I need to think about and test on different compiler/platform 
combinations some, particularly to make sure it doesn't break our mingw builds 
or other strange places we have used ucommon.  But I am also very interested 
to see that sflphone works and succeeds on all platforms it can be built for.

On Monday, September 01, 2014 04:55:19 PM Tristan Matthews wrote:
> Hi,
> 
> ----- Original Message -----
> 
> > From: "Dominyk Tiller" <address@hidden>
> > To: address@hidden
> > Sent: Sunday, August 31, 2014 8:24:24 AM
> > Subject: OS X Compile Bug
> > 
> > Hey guys,
> > 
> > I'm hitting some issues compiling ucommon-6.1.10 on OS X. I'm running
> > 10.10, but the build fails even when I use gcc rather than the
> > Apple-supplied clang. The build fails both with and without the
> > autotooling process.
> > 
> > I've attached the two build logs. It's inside Homebrew format,
> > because
> > I started work on getting sipwitch to work for Homebrew and
> > immediately ran into trouble with ucommon, but I've tested it outside
> > of Homebrew as well and encountered the same build errors.
> > 
> > Any advice?
> 
> You can try these two patches, we (sflphone.org) are able to build ucommon
> on OS X with them:
> https://projects.savoirfairelinux.com/projects/sflphone/repository/revision
> s/master/entry/daemon/contrib/src/ucommon/extended.patch
> https://projects.savoirfairelinux.com/projects/sflphone/repository/revision
> s/master/entry/daemon/contrib/src/ucommon/usedefines.patch
> 
> Best,
> Tristan