[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-zile] Lua Zile & its libraries

From: Reuben Thomas
Subject: Re: [Bug-zile] Lua Zile & its libraries
Date: Thu, 8 Sep 2011 13:35:37 +0100

On 8 September 2011 11:51, Gary V. Vaughan <address@hidden> wrote:
> * luaposix
>  I've sent you a bunch of pull-requests at github for luaposix, which
>  get me almost to compiling on darwin.  The sticking point is that I
>  need to manually pass CPPFLAGS=-DSIGPOLL=7 to get a working module.

I think for now this should be kludged into configure.ac. This is a
Darwin bug (or at least, it's supporting an earlier version of  POSIX
than 2001): signal.h(P) says: "The following signals shall be
supported on all implementations...SIGPOLL".

Can you report this problem to bug-gnulib, please?

>  Another wart is that if you are not very intimately aware of what
>  files are in the lua package directories, then the name-change from
>  posix.so to posix_c.so leaves the old posix.so behind,

This is regrettable, but I'm standardizing on this format with
luaposix, lcurses &c.

> * lcurses
>  Just waiting on a mutually satisfactory solution to the curses API
>  warnings.

I have now taken your pull request.

>  /usr/local/share/lua/5.1/posix.lua:11: bad argument #2 to 'open' (bad flags)

Can you look into this? I really don't understand how this could go
wrong for you and not for me, since it's not platform dependent. The
only thing I can think of is that you are somehow getting a bad
version of the (Lua) posix.creat (i.e. an old std.lua which still
contains posix_ext.lua), because the error means that posix.open
doesn't understand one of the oflags passed by posix.creat, which

  return open (file, {"creat", "wronly", "trunc"}, mode)

> Agreed. It would be nicer still to have an ax_lua_module.m4 in the
> autoconf-archive ;)

I think I have found the closest thing to a standard way of Lua
modules reporting their versions (and it's not pretty, sadly, just
widely-used by the Lua authors' own modules), so I'll write up
something for that.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]