Agreed. Fix could either be in the c_macro function or in find_header which 
calls it. And, a graceful exit could solve a lot of documentation and 
configuration confusion as well.

 

From: d...@apple.com [mailto:d...@apple.com] 
Sent: Friday, February 17, 2017 4:54 PM
To: Rob Archibald
Cc: calendarserver-users@lists.macosforge.org
Subject: Re: [CalendarServer-users] Error on bin/develop

 

Hi,

 

Yes, installing that ldap package is the right thing to do, however this 
probably also indicates a bug (or at least, 'opportunity for enhancement') in 
the bin/develop flow... If you don't actually use LDAP (instead using local xml 
files for directory service data), then it probably won't affect you either way.

 

-dre

 

On Feb 17, 2017, at 4:50 PM, Rob Archibald <r...@robarchibald.com> wrote:

 

Nevermind. After tracking it down deep enough to be able to ask the question, 
the answer wasn’t far away. Turns out that after a bit more digging, I found 
that my system didn’t have ldap.h available. After a simple apt-get install 
libldap2-dev, it finished with no errors.

 

From: Rob Archibald [mailto:r...@robarchibald.com] 
Sent: Friday, February 17, 2017 4:38 PM
To: 'calendarserver-users@lists.macosforge.org'
Subject: Error on bin/develop

 

I’m running Calendar Server 9.0 on Ubuntu 16.04.1. It seems to be working fine, 
but I have this nagging error in the back of my mind that makes me worry that 
something still isn’t quite right. When I run bin/develop, I receive the 
following error: 

 

.../ccs-calendarserver-CalendarServer-9.0/bin/_py.sh: line 104: [: # 1 
"<stdin>": integer expression expected

.../ccs-calendarserver-CalendarServer-9.0/bin/_py.sh: line 109: [: # 1 
"<stdin>": integer expression expected

 

It works even though I receive this error, so I’m trying to understand it to 
see if it matters. This is in the middle of a function called cmp_version which 
is expecting numeric arguments. It receives these 2 values:

 

1.       20428 – seems OK

2.       # 1 "<stdin>" – looks bad to me

 

It looks like the c_macro function is the source of the bad 2nd value. >From 
what I can tell, the function is being called on ldap.h and trying to get 
LDAP_VENDOR_VERSION, but instead gets back the bogus value.  I’m guessing this 
means LDAP won’t work for me?

 

 

Blessings,

Rob Archibald, M.M.

CTO, EndFirst LLC

Founder and Music Director, Ensign Symphony & Chorus

 <mailto:r...@robarchibald.com> r...@robarchibald.com

 

_______________________________________________
calendarserver-users mailing list
calendarserver-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/calendarserver-users

 

_______________________________________________
calendarserver-users mailing list
calendarserver-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/calendarserver-users

Reply via email to