Re: [Bug-zile] Building Zile master head

[Reuben Thomas]

On 5 January 2014 06:49, Gary V. Vaughan <address@hidden> wrote:

I pushed an ugly fix just now, which I'll clean up as I modularize the various source files properly and isolate them from each other except along interface boundaries - right now almost everything happens in the global name space, and each file can see the status of code from other files (by design, carried over from C Zile).

$ luarocks make zile-git-1.rockspec
./bootstrap && ./configure LUA='/home/rrt/local/bin/x86_64-linux-gnu/lua5.2' LUA_INCLUDE='-I/home/rrt/local/include/lua5.2' --prefix='/home/rrt/local/lib/luarocks/5.2/rocks/zile/git-1' --libdir='/home/rrt/local/lib/luarocks/5.2/rocks/zile/git-1/lib' --datadir='/home/rrt/local/lib/luarocks/5.2/rocks/zile/git-1/lua' && make clean all
make: Entering directory `/home/rrt/repo/zile/slingshot'
make: `build-aux/mkrockspecs' is up to date.
make: Leaving directory `/home/rrt/repo/zile/slingshot'
linking file './README-release'
bootstrap: running: autoreconf --symlink --install
local.mk:105: warning: wildcard $(srcdir: non-POSIX variable name
local.mk:105: (probably a GNU make extension)
Makefile.am:58:   'local.mk' included from here
local.mk:106: warning: wildcard $(srcdir: non-POSIX variable name
local.mk:106: (probably a GNU make extension)
Makefile.am:58:   'local.mk' included from here
bootstrap: Done.  Now you can run './configure'.
## -------------------- ##
## Configuring zile 3.1 ##
## -------------------- ##

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking if /home/rrt/local/bin/x86_64-linux-gnu/lua5.2 is a Lua interpreter... yes
checking whether /home/rrt/local/bin/x86_64-linux-gnu/lua5.2 version >= 5.2... yes
checking for /home/rrt/local/bin/x86_64-linux-gnu/lua5.2 version... 5.2
checking for /home/rrt/local/bin/x86_64-linux-gnu/lua5.2 platform... unknown
checking for /home/rrt/local/bin/x86_64-linux-gnu/lua5.2 script directory... ${prefix}/share/lua/5.2
checking for /home/rrt/local/bin/x86_64-linux-gnu/lua5.2 module directory... ${exec_prefix}/lib/lua/5.2
checking for ldoc... /home/rrt/local/bin/x86_64-linux-gnu/ldoc
checking for help2man... /usr/bin/help2man
checking for emacs... /home/rrt/bin/emacs
checking Emacs version 24.3.1 >= 23.1... yes
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating .travis.yml
config.status: creating Makefile
config.status: creating lib/zile/version.lua
config.status: creating lib/zmacs/zmacs
config.status: creating lib/zz/zz
test -z "doc/zmacs.1  doc/zz.1 " || rm -f doc/zmacs.1  doc/zz.1
test -z "" || rm -f
  GEN      doc/zmacs.1
  GEN      doc/zz.1
cd . && /home/rrt/local/bin/x86_64-linux-gnu/ldoc -c doc/config.ld .
reading configuration from doc/config.ld
this config file field/function is unrecognized: sort
make: *** [doc/index.html] Error 255

Error: Build error: Failed building.

I have the latest ldoc from luarocks.org: 1.3.12-1.

By the way, I also see another problem:

$ make rockspecs
make[1]: Entering directory `/home/rrt/repo/zile'
  GEN      build-aux/luarocks-config.lua
/bin/bash: line 6: cd: /home/rrt/local/bin/x86_64-linux-gnu/../include: No such file or directory
/bin/bash: line 7: cd: /home/rrt/local/bin/x86_64-linux-gnu/../lib: No such file or directory
  GEN      zile-3.1-1.rockspec
  GEN      zile-git-1.rockspec
make[1]: Leaving directory `/home/rrt/repo/zile'

I don't know of any better or "more official" multi-arch bin solution. luarocks, FWIW, can't cope either without manual configuration, but the build system of the above-mentioned cw can, and might be worth referring to (it's a small and simple project, so shouldn't have project-specific confusion getting in the way).

--
http://rrt.sc3d.org