Re: Build problem in luaposix 5.1.7

[Axel Kittenberger <axkibe@...>]

I recently ran into the same issue. I just commented away the two
realtime clock functions from the library, no further dependencies,
didn't need em anyway, and was interested in the rest of luaposix,
would be nice if this could be a configure-like switch. IMHO the blame
is on apple tough that isn't fully POSIX.

On Thu, Dec 9, 2010 at 7:35 PM, Zed Shaw <zed.shaw@gmail.com> wrote:
> Hi,
>
> I couldn't find contact information for any of the authors of
> luaposix, so I figured I'd report it here and see if people have a
> solution.  In Tir I use luaposix, but folks on OSX have this build
> failure:
>
> sudo luarocks install luaposix
> Installing http://luarocks.org/repositories/rocks/luaposix-5.1.7-2.src.rock…;
> Archive:  /private/tmp/luarocks_luarocks-rock-luaposix-5.1.7-2-8760/luaposix-5.1.7-2.src.rock
>  inflating: luaposix-5.1.7-2.rockspec
>  inflating: luaposix-5.1.7.tar.bz2
> export MACOSX_DEPLOYMENT_TARGET=10.3; gcc -O2 -I/usr/local/include -c
> lposix.c -o lposix.o
> lposix.c: In function ‘get_clk_id_const’:
> lposix.c:1214: error: ‘CLOCK_REALTIME’ undeclared (first use in this function)
> lposix.c:1214: error: (Each undeclared identifier is reported only once
> lposix.c:1214: error: for each function it appears in.)
> lposix.c:1216: error: ‘CLOCK_MONOTONIC’ undeclared (first use in this function)
> lposix.c:1218: error: ‘CLOCK_PROCESS_CPUTIME_ID’ undeclared (first use
> in this function)
> lposix.c:1220: error: ‘CLOCK_THREAD_CPUTIME_ID’ undeclared (first use
> in this function)
>
> Error: Build error: Failed compiling object lposix.o
>
> This isn't a problem in luaposix 5.1.2, so I'm rolling back the
> dependency to then.
>
> Zed
>
>