On Sun, 2010-10-24 at 11:26 +0200, Tejas Guruswamy wrote:
> On 22/10/10 08:14, Mark Ellis wrote:
> > On Tue, 2010-10-19 at 17:04 +0200, Tejas Guruswamy wrote:
> >
> > I'd feel more comfortable doing something to undef it in the wrapper
> > source rather than the general headers, but that should
On 22/10/10 08:14, Mark Ellis wrote:
> On Tue, 2010-10-19 at 17:04 +0200, Tejas Guruswamy wrote:
>
> I'd feel more comfortable doing something to undef it in the wrapper
> source rather than the general headers, but that should be easy enough,
> I think.
>> Found it, here's the context:
>>
>> /u
On Fri, Oct 22, 2010 at 09:14, Mark Ellis wrote:
> On Tue, 2010-10-19 at 17:04 +0200, Tejas Guruswamy wrote:
>> >> Luckily, the python declaration was just a #define, so it can be #undef'd.
>> >> This isn't an issue with python2.6 or before, even with gcc 4.5.1, btw.
>> >>
>> >> Here's a patch for
On Tue, 2010-10-19 at 17:04 +0200, Tejas Guruswamy wrote:
> On 19/10/10 15:51, Mark Ellis wrote:
> > On Tue, 2010-10-19 at 14:02 +0200, Tejas Guruswamy wrote:
> >
> >> On 19/10/10 10:06, David Eriksson wrote:
> >>
> >>> If I remember correctly, DATE is one of the types in synce_types.h,
> >
On 19/10/10 15:51, Mark Ellis wrote:
> On Tue, 2010-10-19 at 14:02 +0200, Tejas Guruswamy wrote:
>
>> On 19/10/10 10:06, David Eriksson wrote:
>>
>>> If I remember correctly, DATE is one of the types in synce_types.h,
>>> which are meant to have the same name and declaration as in Microsoft
On Tue, 2010-10-19 at 14:02 +0200, Tejas Guruswamy wrote:
> On 19/10/10 10:06, David Eriksson wrote:
> > If I remember correctly, DATE is one of the types in synce_types.h,
> > which are meant to have the same name and declaration as in Microsoft
> > Windows. Changing it in libsynce will diverge fr
On 19/10/10 10:06, David Eriksson wrote:
> If I remember correctly, DATE is one of the types in synce_types.h,
> which are meant to have the same name and declaration as in Microsoft
> Windows. Changing it in libsynce will diverge from that and also means
> changing librapi2 and many tools and appl
If I remember correctly, DATE is one of the types in synce_types.h,
which are meant to have the same name and declaration as in Microsoft
Windows. Changing it in libsynce will diverge from that and also means
changing librapi2 and many tools and applications that depend on that
library.
It would p
On 18/10/10 00:03, Tejas Guruswamy wrote:
> On 17/10/10 20:52, Mark Ellis wrote:
>
>> On Sat, 2010-10-16 at 21:59 +0200, Tejas Guruswamy wrote:
>>
>>> librapi2 / librra python bindings fail to build on openSUSE Factory, and
>>> the only recent relevant change I can find is python2.7 .
>>> g
On 17/10/10 20:52, Mark Ellis wrote:
> On Sat, 2010-10-16 at 21:59 +0200, Tejas Guruswamy wrote:
>
>> librapi2 / librra python bindings fail to build on openSUSE Factory, and
>> the only recent relevant change I can find is python2.7 .
>> gcc is 4.5, pyrex is 0.9.8.5.
>>
>> So does anyone have S
On Sat, 2010-10-16 at 21:59 +0200, Tejas Guruswamy wrote:
> All,
>
> librapi2 / librra python bindings fail to build on openSUSE Factory, and
> the only recent relevant change I can find is python2.7 .
> gcc is 4.5, pyrex is 0.9.8.5.
>
> So does anyone have SynCE successfully building against pyt
All,
librapi2 / librra python bindings fail to build on openSUSE Factory, and
the only recent relevant change I can find is python2.7 .
gcc is 4.5, pyrex is 0.9.8.5.
So does anyone have SynCE successfully building against python2.7?
It's a rather unhelpful error it's spitting out:
make[3]: Ente
12 matches
Mail list logo