Re: darcs snapshot building error with lua 5.1
On Thu, 18 May 2006 01:04:25 +0200, Matthieu Moy <[EMAIL PROTECTED]>
wrote:
csant <[EMAIL PROTECTED]> writes:
configure:5794: checking for lua_call in -llua
configure:5824: gcc -o conftest -g -O2 conftest.c -llua >&5
/usr/lib/gcc-lib/i586-suse-linux/3.3.5/../../../liblua.a(lvm.o)(.text+0xab5):
In function `Arith':
lvm.c: undefined reference to `pow'
/usr/lib/gcc-lib/i586-suse-linux/3.3.5/../../../liblua.a(lvm.o)(.text+0x1d82):
In function `luaV_execute':
lvm.c: undefined reference to `pow'
/usr/lib/gcc-lib/i586-suse-linux/3.3.5/../../../liblua.a(lcode.o)(.text+0x108d):
In function `codearith':
lcode.c: undefined reference to `pow'
collect2: ld returned 1 exit status
Can you try this patch ?
--- old-ion-3/configure.ac 2006-05-18 04:32:21.846862632 +0200
+++ new-ion-3/configure.ac 2006-05-18 04:32:22.063829648 +0200
@@ -244,14 +244,14 @@
elif test "x$with_lua_prefix" != x; then
LUA_LIBS="-L$with_lua_prefix/lib"
fi
+AC_CHECK_LIB([m], [exp], [lua_extra_libs="$lua_extra_libs -lm"], [])
AC_CHECK_LIB([lua$with_lua_suffix],
[lua_call],
- [LUA_LIBS="$LUA_LIBS -llua$with_lua_suffix"],
+ [LUA_LIBS="$LUA_LIBS -llua$with_lua_suffix -lm"],
[AC_MSG_ERROR([*** Can't find lua_call in
lua$with_lua_suffix.
*** Check for liblua installation or
--with-lua-libraries or --with-lua-suffix options])],
[$LUA_LIBS])
AC_CHECK_LIB([dl], [dlopen], [lua_extra_libs="$lua_extra_libs -ldl"],
[])
-AC_CHECK_LIB([m], [exp], [lua_extra_libs="$lua_extra_libs -lm"], [])
dnl }}}
dnl liblua_version {{{
Still failing with the same error after applying the patch to a clean tree
before running autoreconf.
/c
Re: darcs snapshot building error with lua 5.1
On Thu, 18 May 2006 00:40:38 +0200, Matthieu Moy <[EMAIL PROTECTED]>
wrote:
csant <[EMAIL PROTECTED]> writes:
configure: error: *** Can't find lua_call in lua.
*** Check for liblua installation or
--with-lua-libraries or --with-lua-suffix options
Where is liblua installed and how is it called?
I installed lua 5.1 from source with
$ make linux
# make install
after modifying the Makefile to install to /usr instead of /usr/local
, and liblua is /usr/lib/liblua.a
Ah, this is actually where it is supposed to be, so there's a problem
here ...
you should have the exact error message in the generated config.log
file. Can you post it here please?
configure:5526: found /usr/bin/lua
configure:5538: result: /usr/bin/lua
configure:5550: checking for lua version >= 5.1
configure:5562: result: yes (found 5.1)
configure:5570: checking for luac
configure:5588: found /usr/bin/luac
configure:5600: result: /usr/bin/luac
configure:5610: checking for lua version = luac version
configure:5614: result: yes (found 5.1)
configure:5644: checking lua.h usability
configure:5656: gcc -c -g -O2 conftest.c >&5
configure:5662: $? = 0
configure:5666: test -z
|| test ! -s conftest.err
configure:5669: $? = 0
configure:5672: test -s conftest.o
configure:5675: $? = 0
configure:5685: result: yes
configure:5689: checking lua.h presence
configure:5699: gcc -E conftest.c
configure:5705: $? = 0
configure:5725: result: yes
configure:5760: checking for lua.h
configure:5767: result: yes
configure:5644: checking lualib.h usability
configure:5656: gcc -c -g -O2 conftest.c >&5
configure:5662: $? = 0
configure:5666: test -z
|| test ! -s conftest.err
configure:5669: $? = 0
configure:5672: test -s conftest.o
configure:5675: $? = 0
configure:5685: result: yes
configure:5689: checking lualib.h presence
configure:5699: gcc -E conftest.c
configure:5705: $? = 0
configure:5725: result: yes
configure:5760: checking for lualib.h
configure:5767: result: yes
configure:5794: checking for lua_call in -llua
configure:5824: gcc -o conftest -g -O2 conftest.c -llua >&5
/usr/lib/gcc-lib/i586-suse-linux/3.3.5/../../../liblua.a(lvm.o)(.text+0xab5):
In function `Arith':
lvm.c: undefined reference to `pow'
/usr/lib/gcc-lib/i586-suse-linux/3.3.5/../../../liblua.a(lvm.o)(.text+0x1d82):
In function `luaV_execute':
lvm.c: undefined reference to `pow'
/usr/lib/gcc-lib/i586-suse-linux/3.3.5/../../../liblua.a(lcode.o)(.text+0x108d):
In function `codearith':
lcode.c: undefined reference to `pow'
collect2: ld returned 1 exit status
configure:5830: $? = 1
configure: failed program was:
| /* confdefs.h. */
|
| #define PACKAGE_NAME "Ion Window Manager"
| #define PACKAGE_TARNAME "ion3"
| #define PACKAGE_VERSION "ION_VERSION"
| #define PACKAGE_STRING "Ion Window Manager ION_VERSION"
| #define PACKAGE_BUGREPORT "[EMAIL PROTECTED]"
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_LUA_H 1
| #define HAVE_LUALIB_H 1
| /* end confdefs.h. */
|
| /* Override any gcc2 internal prototype to avoid an error. */
| #ifdef __cplusplus
| extern "C"
| #endif
| /* We use char because int might match the return type of a gcc2
|builtin and then its argument prototype would still apply. */
| char lua_call ();
| int
| main ()
| {
| lua_call ();
| ;
| return 0;
| }
configure:5856: result: no
configure:5862: error: *** Can't find lua_call in lua.
*** Check for liblua installation or
--with-lua-libraries or --with-lua-suffix options
Hope this is enough info from the config.log - please ask if you need more.
/c
Re: darcs snapshot building error with lua 5.1
csant <[EMAIL PROTECTED]> writes:
> configure:5794: checking for lua_call in -llua
> configure:5824: gcc -o conftest -g -O2 conftest.c -llua >&5
> /usr/lib/gcc-lib/i586-suse-linux/3.3.5/../../../liblua.a(lvm.o)(.text+0xab5):
> In function `Arith':
> lvm.c: undefined reference to `pow'
> /usr/lib/gcc-lib/i586-suse-linux/3.3.5/../../../liblua.a(lvm.o)(.text+0x1d82):
> In function `luaV_execute':
> lvm.c: undefined reference to `pow'
> /usr/lib/gcc-lib/i586-suse-linux/3.3.5/../../../liblua.a(lcode.o)(.text+0x108d):
> In function `codearith':
> lcode.c: undefined reference to `pow'
> collect2: ld returned 1 exit status
Can you try this patch ?
--- old-ion-3/configure.ac 2006-05-18 04:32:21.846862632 +0200
+++ new-ion-3/configure.ac 2006-05-18 04:32:22.063829648 +0200
@@ -244,14 +244,14 @@
elif test "x$with_lua_prefix" != x; then
LUA_LIBS="-L$with_lua_prefix/lib"
fi
+AC_CHECK_LIB([m], [exp], [lua_extra_libs="$lua_extra_libs -lm"], [])
AC_CHECK_LIB([lua$with_lua_suffix],
[lua_call],
- [LUA_LIBS="$LUA_LIBS -llua$with_lua_suffix"],
+ [LUA_LIBS="$LUA_LIBS -llua$with_lua_suffix -lm"],
[AC_MSG_ERROR([*** Can't find lua_call in lua$with_lua_suffix.
*** Check for liblua installation or --with-lua-libraries or
--with-lua-suffix options])],
[$LUA_LIBS])
AC_CHECK_LIB([dl], [dlopen], [lua_extra_libs="$lua_extra_libs -ldl"], [])
-AC_CHECK_LIB([m], [exp], [lua_extra_libs="$lua_extra_libs -lm"], [])
dnl }}}
dnl liblua_version {{{
--
Matthieu
Re: darcs snapshot building error with lua 5.1
csant <[EMAIL PROTECTED]> writes: >>> configure: error: *** Can't find lua_call in lua. >>> *** Check for liblua installation or >>> --with-lua-libraries or --with-lua-suffix options >> >> Where is liblua installed and how is it called? >> > > I installed lua 5.1 from source with > $ make linux > # make install > after modifying the Makefile to install to /usr instead of /usr/local > , and liblua is /usr/lib/liblua.a Ah, this is actually where it is supposed to be, so there's a problem here ... you should have the exact error message in the generated config.log file. Can you post it here please? Thanks, -- Matthieu
Re: darcs snapshot building error with lua 5.1
On Thu, 18 May 2006 03:22:37 +0200, Matthieu Moy <[EMAIL PROTECTED]> wrote: csant wrote: On Wed, 17 May 2006 20:06:00 +0200, Matthieu Moy <[EMAIL PROTECTED]> wrote: That should be fixed now, but testers (in particular, non-debian users) on a system that once-upon-a-time was SUSE 9.3, mostly with packages built on the system now. To test: [ install darcs ] darcs get --partial http://iki.fi/tuomov/repos/ion-3/ cd ion-3 sh predist.sh -snapshot autoreconf ./configure configure: error: *** Can't find lua_call in lua. *** Check for liblua installation or --with-lua-libraries or --with-lua-suffix options Where is liblua installed and how is it called? I installed lua 5.1 from source with $ make linux # make install after modifying the Makefile to install to /usr instead of /usr/local , and liblua is /usr/lib/liblua.a /c
Re: darcs snapshot building error with lua 5.1
csant wrote: > On Wed, 17 May 2006 20:06:00 +0200, Matthieu Moy <[EMAIL PROTECTED]> > wrote: > >> That should be fixed now, but testers (in particular, non-debian users) > on a system that once-upon-a-time was SUSE 9.3, mostly with packages > built on the system now. > >> To test: >> >> [ install darcs ] >> darcs get --partial http://iki.fi/tuomov/repos/ion-3/ >> cd ion-3 >> sh predist.sh -snapshot > autoreconf >> ./configure > > configure: error: *** Can't find lua_call in lua. > *** Check for liblua installation or > --with-lua-libraries or --with-lua-suffix options Where is liblua installed and how is it called? -- Matthieu
Re: Can't compile ion
On Wed, May 17, 2006 at 11:15:29PM +0200, Clemence Magnien wrote: > Hello, > > I hope this is the right place to ask my question. > > I'm trying to compile Ion2 or Ion3, and both fail with similar errors > linked to lua. So I guess I'm doing something wrong, but I can't figure > why, and I did not find something relating while browsing through > the archives of this mailing list. > > Compiling ion-2-20040729 fails with the following: > /usr/bin/lua ../mkexports.lua -module ioncore -o exports.c binding.c > conf-bindings.c cursor.c event.c exec.c focus.c strings.c key.c modules.c > mwmhints.c obj.c pointer.c property.c readconfig.c screen.c signal.c > sizehint.c window.c ioncore.c xic.c selection.c symlist.c clientwin.c > colormap.c region.c eventh.c attach.c resize.c defer.c grab.c manage.c > readfds.c regbind.c rootwin.c tags.c names.c saveload.c genws.c genframe.c > genframe-pointer.c conf.c reginfo.c errorlog.c stacking.c extlconv.c > fullscreen.c mplex.c bindmaps.c gr.c infowin.c activity.c netwm.c objlist.c > /usr/bin/lua: ../mkexports.lua:57: attempt to call a table value > stack traceback: > ../mkexports.lua:57: in main chunk > [C]: ? > make[1]: *** [exports.c] Error 1 > make[1]: Leaving directory `/home/magnien/ion-2-20040729/ioncore' > make: *** [subdirs] Error 2 There is deprecated lua code in mkexports.lua. In the case above: "for d, t in desc2ct do" is deprecated since lua 5.0 and has been removed in 5.1, you habe to use an iterator function on tables: "for d, t in pairs(desc2ct) do" Jürgen
Re: Can't compile ion
lua 5.1 is new, ion only got support for it yesterday/today in the darcs repository. To use the released versions you need a lua 5.0.x version. -Etan
Can't compile ion
Hello, I hope this is the right place to ask my question. I'm trying to compile Ion2 or Ion3, and both fail with similar errors linked to lua. So I guess I'm doing something wrong, but I can't figure why, and I did not find something relating while browsing through the archives of this mailing list. Compiling ion-2-20040729 fails with the following: /usr/bin/lua ../mkexports.lua -module ioncore -o exports.c binding.c conf-bindings.c cursor.c event.c exec.c focus.c strings.c key.c modules.c mwmhints.c obj.c pointer.c property.c readconfig.c screen.c signal.c sizehint.c window.c ioncore.c xic.c selection.c symlist.c clientwin.c colormap.c region.c eventh.c attach.c resize.c defer.c grab.c manage.c readfds.c regbind.c rootwin.c tags.c names.c saveload.c genws.c genframe.c genframe-pointer.c conf.c reginfo.c errorlog.c stacking.c extlconv.c fullscreen.c mplex.c bindmaps.c gr.c infowin.c activity.c netwm.c objlist.c /usr/bin/lua: ../mkexports.lua:57: attempt to call a table value stack traceback: ../mkexports.lua:57: in main chunk [C]: ? make[1]: *** [exports.c] Error 1 make[1]: Leaving directory `/home/magnien/ion-2-20040729/ioncore' make: *** [subdirs] Error 2 and compiling ion-3ds-20060326 fails with: make[1]: Entering directory `/home/magnien/ion-3ds-20060326/mod_ionws' /usr/bin/lua ../libextl/libextl-mkexports -module mod_ionws -o exports.c -h exports.h \ main.c ionws.c placement.c split.c split-stdisp.c splitfloat.c panehandle.c /usr/bin/lua: ../libextl/libextl-mkexports:58: attempt to call a table value stack traceback: ../libextl/libextl-mkexports:58: in main chunk [C]: ? make[1]: *** [exports.c] Error 1 make[1]: Leaving directory `/home/magnien/ion-3ds-20060326/mod_ionws' make: *** [subdirs] Error 2 I'm running Fedora core 5, with lua 5.1. I think I have set the correct values for everything concerning lua in system.mk (this consisted in setting LUA_DIR to /usr). Any help would be greatly appreciated. Cheers, Clemence -- Ce qui se concoit bien s'exprime clairement. - http://clemence.magnien.free.fr/ Tel : 01 55 55 86 27
Re: changing default bindings
On 2006-05-17, Bruce Stephens <[EMAIL PROTECTED]> wrote:
> Yeah, I'm not expecting things to be effort-free---I guess the
> sections may change now and again, but that's OK. Much better than
> copying the whole file just to modify a couple of bindings.
I'm not actually perfectly happy how the bindings are currently
defined. Perhaps there should simply be a top-level
bindkey("WMPlex.toplevel", ALTMETA.."F5", nil)
and
bindkeys("Foo", { ["X"] = whatever } )
-- Can't unbind with this, however
and similarly for mouse stuff. The contexts/sections must, however, stay,
and may change until the release of Ion. The only way around them is to
introduce a separate set of "commands" with a context associated to them,
and I don't want to maintain them and the additional documentation.
--
Tuomo
Re: changing default bindings
Etan Reisner <[EMAIL PROTECTED]> writes:
[...]
> Bind the key to nil.
Ah, that's the trick. Thanks. I had tried using things like:
defbindings("WMPlex.toplevel", {
kpress(ALTMETA.."F5",),
})
and so on. But
defbindings("WMPlex.toplevel", {
kpress(ALTMETA.."F5",
nil),
})
works.
> (Note: If you are making your own file you need to get the right
> defbindings section to remove the binding.)
Yeah, I'm not expecting things to be effort-free---I guess the
sections may change now and again, but that's OK. Much better than
copying the whole file just to modify a couple of bindings.
Re: changing default bindings
On Wed, 17 May 2006, Bruce Stephens wrote: What's the approved way of doing this, now? I guess if I want to replace an existing binding, I can just redefine it in cfg_ion.lua, but I'd like to remove a binding or two. Specifically, I never use ion's "edit file" F5 binding, so I'd like to remove it (there's an emacs mode that suggests F5, and that seems OK to me, except that ion grabs it). Previously I just copied cfg_bindings.lua and edited it, but that never felt right, and I don't want to copy and edit cfg_ioncore.lua and keep that up to date. Bind the key to nil. (Note: If you are making your own file you need to get the right defbindings section to remove the binding.) -Etan
changing default bindings
What's the approved way of doing this, now? I guess if I want to replace an existing binding, I can just redefine it in cfg_ion.lua, but I'd like to remove a binding or two. Specifically, I never use ion's "edit file" F5 binding, so I'd like to remove it (there's an emacs mode that suggests F5, and that seems OK to me, except that ion grabs it). Previously I just copied cfg_bindings.lua and edited it, but that never felt right, and I don't want to copy and edit cfg_ioncore.lua and keep that up to date.
Re: darcs snapshot building error with lua 5.1
On Wed, 17 May 2006 20:06:00 +0200, Matthieu Moy <[EMAIL PROTECTED]> wrote: That should be fixed now, but testers (in particular, non-debian users) on a system that once-upon-a-time was SUSE 9.3, mostly with packages built on the system now. To test: [ install darcs ] darcs get --partial http://iki.fi/tuomov/repos/ion-3/ cd ion-3 sh predist.sh -snapshot autoreconf ./configure configure: error: *** Can't find lua_call in lua. *** Check for liblua installation or --with-lua-libraries or --with-lua-suffix options Note that: 1.) $ autoreconf $ ./configure was working until requiring lua 5.1, and 2.) I can simply conpile by modifying the path to lua in system.mk. /c -- [Quote] I have measured out my life with coffee spoons; ~~~ T.S. Eliot
Re: darcs snapshot building error with lua 5.1
Tuomo Valkonen wrote: > On 2006-05-17, Matthieu Moy <[EMAIL PROTECTED]> wrote: >> I've hacked a bit, and it seems I have a working configure.ac. > > BTW, there are a few other autoconf issues in the TODO list (included in > the repository), in case anyone cares to fix them. That should be fixed now, but testers (in particular, non-debian users) are welcome. To test: [ install darcs ] darcs get --partial http://iki.fi/tuomov/repos/ion-3/ cd ion-3 sh predist.sh -snapshot ./configure make Normally, any problem should be reported by "./configure", and if configure ends without error, make should work. (BTW, you can update the TODO.riot, which I didn't do because I don't know riot). -- Matthieu
Re: darcs snapshot building error with lua 5.1
On 2006-05-17, Matthieu Moy <[EMAIL PROTECTED]> wrote: > I've hacked a bit, and it seems I have a working configure.ac. BTW, there are a few other autoconf issues in the TODO list (included in the repository), in case anyone cares to fix them. -- Tuomo
Re: darcs snapshot building error with lua 5.1
"Vladimir Chizhov" <[EMAIL PROTECTED]> writes:
> The current darcs snapshot fails on ./configure with the following message:
>
> checking for lua_open in -llua... no
> configure: error: *** Can't find lua_open in lua.
> *** Check for liblua installation or
> --with-lua-libraries or --with-lua-suffix options
I've hacked a bit, and it seems I have a working configure.ac.
Tuomo, I've sent a patch (two, indeed) to you with darcs, but I'm
afraid I mixed up everything (the predist.sh script seems to modify
source files too).
My version of configure.ac is available here:
http://www-verimag.imag.fr/~moy/tmp/configure.ac
And, here's the patch again:
--- old-ion-3/configure.ac 2006-05-17 14:21:55.847203744 +0200
+++ new-ion-3/configure.ac 2006-05-17 14:21:55.852202984 +0200
@@ -176,11 +176,11 @@
dnl }}}
dnl lua_version {{{
-AC_MSG_CHECKING([for lua version >= 5.0])
+AC_MSG_CHECKING([for lua version >= 5.1])
lua_version=$($LUA -v 2>&1 | head -n 1 | cut -d' ' -f2)
dnl lua_version=$($LUA -v 2>&1 >/dev/null | head -n 1 | $EGREP -o
'[0-9]+(\.[0-9]+)+')
case $lua_version in
-0.* | 1.* | 2.* | 3.* | 4.*)
+0.* | 1.* | 2.* | 3.* | 4.* | 5.0)
AC_MSG_RESULT([no (found $lua_version)])
AC_MSG_ERROR([*** can't build ion with this version of lua])
;;
@@ -229,22 +229,17 @@
LUA_LIBS="-L$with_lua_prefix/lib"
fi
AC_CHECK_LIB([lua$with_lua_suffix],
- [lua_open],
+ [lua_call],
[LUA_LIBS="$LUA_LIBS -llua$with_lua_suffix"],
- [AC_MSG_ERROR([*** Can't find lua_open in lua$with_lua_suffix.
+ [AC_MSG_ERROR([*** Can't find lua_call in lua$with_lua_suffix.
*** Check for liblua installation or
--with-lua-libraries or --with-lua-suffix
options])],
[$LUA_LIBS])
AC_CHECK_LIB([dl], [dlopen], [lua_extra_libs="$lua_extra_libs -ldl"],
[])
AC_CHECK_LIB([m], [exp], [lua_extra_libs="$lua_extra_libs -lm"], [])
-AC_CHECK_LIB([lualib$with_lua_suffix],
- [luaopen_loadlib],
- [LUA_LIBS="$LUA_LIBS $lua_extra_libs
-llualib$with_lua_suffix"],
- [exit 1],
- [$LUA_LIBS $lua_extra_libs])
dnl }}}
dnl liblua_version {{{
-AC_MSG_CHECKING([for liblua version >= 5.0])
+AC_MSG_CHECKING([for liblua version >= 5.1])
save_CFLAGS="$CFLAGS"
save_LIBS="$LIBS"
CFLAGS="$CFLAGS $LUA_INCLUDES"
@@ -257,12 +252,8 @@
int main()
{
-if(strcmp(lua_version(), LUA_VERSION)!=0){
-printf("Error: lua_version() does not match LUA_VERSION. ");
-exit(EXIT_FAILURE);
-}
-printf("(found %s)... ", lua_version());
-if(strcmp(lua_version(), "Lua 5.0")<0)
+printf("(found %s)... ", LUA_VERSION);
+if(LUA_VERSION_NUM >= 501)
exit(EXIT_FAILURE);
exit(EXIT_SUCCESS);
}
--
Matthieu
Re: VIS (Vapourware Interface Synthesiser) questions
On 2006-05-16, Geoffrey Alan Washburn <[EMAIL PROTECTED]> wrote: > Looking at your Vis paper again, I guess it really depends upon what > you mean by "framework". I can imagine that there could really be > several different ways of realizing Vis: > > (1) Vis as a "display" daemon. > (2) Vis as a library API (many different implementations, dynamically > linkable) > (3) Vis as an interface compiler (stylesheets -> linkable code) > > > I think as far as I can tell from the document you seemed to be > intending (2). In which, case I expect that there will be many > different implementations, and it wouldn't really matter what language > it was written in as long as it follows the system dynamic linking > conventions. Well, almost, but not exactly. The UI backend should be swappable while the program is running, so the Vis core provides the API, tracks state of things (or provides means to access and exchange/store it), and another API for the UI backends to connect to. > For things like rendering, etc. I agree the best > performance/portability would be obtained from C, but depending upon how > rich the stylesheet language becomes (and I can imagine that a > declarative constraint language would make a lot of sense here) it seems > like there would be a significant benefit to implementing that kind of > code in a statically typed functional language. The interpretation of the stylesheets should be entirely up to the UI backends, althoug the core can of course provide many commonly-used functions. I'm not exactly sure what a "declarative constraint language" is, but if you're intending that the stylesheets are written in a "real" programming language, I must disagree. The stylesheets must be understandable by external programs for designing them. If, however, you mean something less than this, but more complicated than a simple configuration file format (for which a parser isn't much work, and even Lua can function as one), then perhaps that part would be best implemented in something like Haskell. One would hope for something a bit lighter than GHC output, however. > Which I guess raises > the question of whether it makes sense to define the stylesheet language > alongside the Vis API, or whether to just have per UI stylesheet > languages (ui-ion's stylesheet language would be Lua, and ui-html's > stylesheet language could be CSS+JavaScript). Well, I've envisioned that there's the generic stylesheet for giving "labels" to things and such stuff that could be useful in a wide variety of backends, but the rest should be entirely up to the UI backends. Of course the core can provide parsers and so on for some common recommended format. -- Tuomo
Re: darcs snapshot building error with lua 5.1
On 2006-05-17, Vladimir Chizhov <[EMAIL PROTECTED]> wrote: > The current darcs snapshot fails on ./configure with the following message: > > checking for lua_open in -llua... no > configure: error: *** Can't find lua_open in lua. > *** Check for liblua installation or > --with-lua-libraries or --with-lua-suffix options > > It's sad :`( I don't like autoconf, and therefore you will not find me updating the scripts. -- Tuomo
