Hi - I'm no further forward with this issue - can anyone let me know if they've managed to get it to build on 10.4.10 Server OS ? on intel hardware ? Having tried to build it on 2 powermacs, 3 imacs and 2 powerbooks, I'm clean out of hardware now :-) same problem with lipo... Any pointers greatly appreciated. Simon Begin forwarded message:

From: Simon McLean <simon.mclean@clicktravel.com> Date: 21 September 2007 21:11:37 BDT To: calendarserver-users@lists.macosforge.org Subject: Problem building on xserve

Hi -

I can build the source on my intel powerbook no problems, but when i try to build on an intel xserve i get this error:-

src/zope/interface/_zope_interface_coptimizations.c:1639: error: called object '&<erroneous-expression>' is not a function src/zope/interface/_zope_interface_coptimizations.c:1641: error: parse error before ')' token src/zope/interface/_zope_interface_coptimizations.c:1641: error: called object '&<erroneous-expression>' is not a function src/zope/interface/_zope_interface_coptimizations.c:1643: error: parse error before ')' token src/zope/interface/_zope_interface_coptimizations.c:1643: error: called object '&<erroneous-expression>' is not a function lipo: can't figure out the architecture type of: /var/tmp// ccXcO4kg.out error: command 'gcc' failed with exit status 1

If i run setup again i get this:-

extensions/pyexpat.c:2037: error: array type has incomplete element type extensions/pyexpat.c:2032: error: request for member 'setter' in something not a structure or union extensions/pyexpat.c:2032: error: request for member 'itself' in something not a structure or union extensions/pyexpat.c:2032: error: called object '&<erroneous- expression>' is not a function extensions/pyexpat.c: At top level: extensions/pyexpat.c:2037: error: array type has incomplete element type lipo: can't figure out the architecture type of: /var/tmp// ccwH0Wxk.out error: command 'gcc' failed with exit status 1

And if i run it again it stops in the same place.

The xserve is running 10.4.10 (Build 8R2218b).

CalenderServer revision number 1895.

Any ideas ?

Thanks, Simon