[notmuch] Mac OS X/Darwin compatibility issues

2009-11-19 Thread Stewart Smith
On Wed, Nov 18, 2009 at 04:24:42PM -0800, Alexander Botero-Lowry wrote: > On Thu, 19 Nov 2009 10:45:28 +1100, Stewart Smith flamingspork.com> wrote: > > On Wed, Nov 18, 2009 at 11:27:20PM +0100, Carl Worth wrote: > > > Yes. I knew I was "cheating" by using some GNU extensions here. I'm > > >

[notmuch] Mac OS X/Darwin compatibility issues

2009-11-19 Thread Carl Worth
On Thu, 19 Nov 2009 16:42:42 +1100, Stewart Smith wrote: > > The idea with gnulib (at least what we've done with drizzle) is to > just copy the bits you need into the tree. Does work pretty well for > those small things that you just don't need to depend on a giant like > glib for. Looks like

[notmuch] Mac OS X/Darwin compatibility issues

2009-11-19 Thread Stewart Smith
On Wed, Nov 18, 2009 at 11:27:20PM +0100, Carl Worth wrote: > Yes. I knew I was "cheating" by using some GNU extensions here. I'm > happy to accept portability patches for these things, but it's hard for > me to get excited about writing them myself. > > Care to take a whack at these?

[notmuch] Mac OS X/Darwin compatibility issues

2009-11-18 Thread Carl Worth
On Wed, 18 Nov 2009 11:50:17 +0800, Jjgod Jiang wrote: > 1. g++ reports 'warning: command line option "-Wmissing-declarations" > is valid for C/ObjC but not for C++' In cairo, what we do is have a huge list of desired warnings and then test each one in turn with a test-compile in the configure

[notmuch] Mac OS X/Darwin compatibility issues

2009-11-18 Thread Alexander Botero-Lowry
On Thu, 19 Nov 2009 10:45:28 +1100, Stewart Smith wrote: > On Wed, Nov 18, 2009 at 11:27:20PM +0100, Carl Worth wrote: > > Yes. I knew I was "cheating" by using some GNU extensions here. I'm > > happy to accept portability patches for these things, but it's hard for > > me to get excited about

[notmuch] Mac OS X/Darwin compatibility issues

2009-11-18 Thread Jjgod Jiang
Hi, On Wed, Nov 18, 2009 at 1:45 PM, Alexander Botero-Lowry wrote: > for getline do you mind trying #define _GNU_SOURCE 1 > before #include in the offending files? The FreeBSD man pages > mentions that as a way of enabling the GNU version of getline(). It seems even _GNU_SOURCE is defined,

[notmuch] Mac OS X/Darwin compatibility issues

2009-11-18 Thread Jjgod Jiang
Hi, When I tried to compile notmuch under Mac OS X 10.6, several issues arisen: 1. g++ reports 'warning: command line option "-Wmissing-declarations" is valid for C/ObjC but not for C++' 2. notmuch-reply.c: In function ?address_is_users?: notmuch-reply.c:87: warning: passing argument 2 of

[notmuch] Mac OS X/Darwin compatibility issues

2009-11-17 Thread Alexander Botero-Lowry
On Wed, 18 Nov 2009 14:14:27 +0800, Jjgod Jiang wrote: > Hi, > > On Wed, Nov 18, 2009 at 1:45 PM, Alexander Botero-Lowry > wrote: > > for getline do you mind trying #define _GNU_SOURCE 1 > > before #include in the offending files? The FreeBSD man pages > > mentions that as a way of enabling

[notmuch] Mac OS X/Darwin compatibility issues

2009-11-17 Thread Alexander Botero-Lowry
On Wed, 18 Nov 2009 11:50:17 +0800, Jjgod Jiang wrote: > Hi, > > When I tried to compile notmuch under Mac OS X 10.6, several issues > arisen: > > 1. g++ reports 'warning: command line option "-Wmissing-declarations" > is valid for C/ObjC but not for C++' > I got that too. I presume it's newly