Hi Fathi,
this bug (see below or #549757 to refresh your memory) might actually a
problem in upstream libical-dev (according to my very limited
understanding of C):
1)
the osmo source contains #include libical/icalss.h
2)
looking at /usr/include/libical/icalss.h from libical-dev:
line 37:
Hi Fathi,
thanks for the answer and the investigation. I'd also be interested in
feedback from libical upstream and how they recommend applications
using libical should handle this...
Cheers,
Eike
On Sun, 11 Oct 2009 11:39:26 +0200 Fathi Boudra wrote:
Hi,
the issue is caused by this
Hi,
the issue is caused by this changes:
http://freeassociation.svn.sourceforge.net/viewvc/freeassociation/trunk/libical/libical.pc.in?r1=842r2=916
cc'ed upstream to get a feedback.
IMHO, we could revert the changes or update the include files to use
libical/ prefix as expected.
cheers,
Fathi
Thanks for reporting this. I reproduced the FTBFS on i386 with
libical-dev 0.44-1, it does not occur with 0.43-3.
Fathi, I am cc-ing you since you're maintaining libical. Do you know of
any changes, in 0.44 that might cause such a problem (see below)? Thanks
for your help!
In the osmo sources,
Source: osmo
Version: 0.2.8-1
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20091005 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
gcc -DHAVE_CONFIG_H -I. -I..
5 matches
Mail list logo
