From: <ma...@go...> - 2008-01-14 01:28:41
|
> On 2007-12-08, William S Fulton <ws...@fu...> > wrote: > > What I'd like to do to help getting developers > setup quickly on Linux is > > to list all the commands to install the > dependent packages. For this I'd > > suggest targeting Ubuntu because apt makes > installing packages so easy > > to document and execute. I've included the > commands below to get up and > > running on Ubuntu Gutsy Gibbon. > > This list is also likely to be suitable for Debian testing and unstable. > > > BTW, Is Lua-5.1 meant to call the shared library > liblua.so as indicated > > in configure.in or liblua5.1.so as it really is > called in Ubuntu? > > I brought this up a month or so ago, and it seems the "5.1" is added > by > the Debian/Ubuntu packaging to allow parallel installation of different > Lua versions. Hello William, Sorry it took so long, but the configure.in is updated to look for lua, lua51 or lua5.1. That should work for Ubuntu. Please verify and let me know if there is any issues. Regards, Mark |
From: William S F. <ws...@fu...> - 2008-01-23 21:14:46
|
mark gossage wrote: >> On 2007-12-08, William S Fulton <ws...@fu...> >> wrote: >>> What I'd like to do to help getting developers >> setup quickly on Linux is >>> to list all the commands to install the >> dependent packages. For this I'd >>> suggest targeting Ubuntu because apt makes >> installing packages so easy >>> to document and execute. I've included the >> commands below to get up and >>> running on Ubuntu Gutsy Gibbon. >> This list is also likely to be suitable for Debian testing and unstable. >> >>> BTW, Is Lua-5.1 meant to call the shared library >> liblua.so as indicated >>> in configure.in or liblua5.1.so as it really is >> called in Ubuntu? >> >> I brought this up a month or so ago, and it seems the "5.1" is added >> by >> the Debian/Ubuntu packaging to allow parallel installation of different >> Lua versions. > > Hello William, > Sorry it took so long, but the configure.in is updated to look for lua, lua51 or lua5.1. That should work for Ubuntu. > Please verify and let me know if there is any issues. Hi Mark The library detection works fine, but it doesn't find lua.h, which is in the /usr/include/lua5.1 directory. You could do something like for java which goes around looking for possible directories to find the headers. Adding /usr/include/lua* into the search path plus some others could work if AC_CHECK_HEADER doesn't find it. I'd have thought autoconf offers a better approach though, but I don't know what it is. William |
From: William S F. <ws...@fu...> - 2008-01-24 22:01:57
|
William S Fulton wrote: > mark gossage wrote: >>> On 2007-12-08, William S Fulton <ws...@fu...> >>> wrote: >>>> What I'd like to do to help getting developers >>> setup quickly on Linux is >>>> to list all the commands to install the >>> dependent packages. For this I'd >>>> suggest targeting Ubuntu because apt makes >>> installing packages so easy >>>> to document and execute. I've included the >>> commands below to get up and >>>> running on Ubuntu Gutsy Gibbon. >>> This list is also likely to be suitable for Debian testing and unstable. >>> >>>> BTW, Is Lua-5.1 meant to call the shared library >>> liblua.so as indicated >>>> in configure.in or liblua5.1.so as it really is >>> called in Ubuntu? >>> >>> I brought this up a month or so ago, and it seems the "5.1" is added >>> by >>> the Debian/Ubuntu packaging to allow parallel installation of different >>> Lua versions. >> >> Hello William, >> Sorry it took so long, but the configure.in is updated to look for >> lua, lua51 or lua5.1. That should work for Ubuntu. >> Please verify and let me know if there is any issues. > > Hi Mark > > The library detection works fine, but it doesn't find lua.h, which is in > the /usr/include/lua5.1 directory. You could do something like for java > which goes around looking for possible directories to find the headers. > Adding /usr/include/lua* into the search path plus some others could > work if AC_CHECK_HEADER doesn't find it. I'd have thought autoconf > offers a better approach though, but I don't know what it is. > Your latest mods work a treat, thanks. Barring a couple of warnings, the test-suite looks to be in perfect shape which is superb. William |