Hello,

On 9/4/11 9:59 PM, Henning Westerholt wrote:

Juha wrote:

...

this looks pretty serious to me:

CC (cc) [L libsrdb1.so.1.0] db_ut.o db_ut.c: In function ‘db_str2time’: db_ut.c:186: warning: implicit declaration of function ‘strptime’ db_ut.c:186: warning: comparison between pointer and integer

Hi Juha,

i saw this as well. It was caused from a recent commit:

commit 0a8e9ea74191e1231abf431f87212f7508b8cc92 Author: Daniel-Constantin Mierlamiconda@gmail.com Date: Sat Aug 20 13:37:27 2011 +0200

 srdb1: fixed compilation on Mac OS X

Probably this needs to be reverted or improved.

Actually this commit broke compilation on mac os x, so just reverting will get back to broken stage:

commit ed78c0967b69abc6e8333924460641de08b73e8f Author: Alex Hermann alex@speakup.nl Date: Sat Aug 20 09:48:00 2011 +0200

lib/srdb1: introduce helper to convert db_val to pv_spec

Cheers, Daniel

On 9/5/11 9:11 AM, Juha Heinanen wrote:

Daniel-Constantin Mierla writes:

...

Actually this commit broke compilation on mac os x, so just reverting will get back to broken stage:

broken state on which os? i would put presence on getting compilation to work on open operating systems.

I guess each can use the best of his resources at a moment to make the project work. So if somebody has one that does not compile, he can work on fixing it. mac os x is freebsd at the core, thus compiling on it makes it very likely to stay clean on all *bsds. Be sure when I will get to a linux, i fix any compile issues I discover, but when out of the office, I work on what I have at a hand. In the recent history I was doing cross compilation on many linux flavours, to generate the rpms, but that does not come handy always.

So, what I said in my previous email is that reverting does not solve completely the issue introduced by the other commit on all os-es we used to support.

Cheers, Daniel