Re: [Monotone-devel] nvm.stripped failing check for lua
On Tue, Oct 14, 2008 at 10:54:40AM -0700, Zack Weinberg wrote: > Aside to Jack Lloyd: It would be nice if botan provided a .pc file as > well as the botan-config executable. OK. Would it make sense to name the pkg-config based on the major and minor versions? pkg-config botan-1.7 --libs pkg-config botan-1.8 --cflags etc I'm guessing probably so, but I don't know pkg-config etiquette. -Jack ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] nvm.stripped failing check for lua
On Mon, Oct 13, 2008 at 9:51 PM, Zack Weinberg <[EMAIL PROTECTED]> wrote: > I remember writing a bunch of m4 to deal with [varying names of .pc files] > but it > doesn't seem to be on this computer; I'll look on the other one tomorrow. Found it. The attached file goes in the m4/ directory, and is used like so: # All of these libraries can be probed for by some combination of # pkg-config and foobar-config, but it's not as simple as it ought to # be, hence the macros. PKG_PROG_PKG_CONFIG MTN_3RDPARTY_LIB(botan) MTN_3RDPARTY_LIB(idn) MTN_3RDPARTY_LIB(lua) MTN_3RDPARTY_LIB(netxx) MTN_3RDPARTY_LIB(pcre) MTN_3RDPARTY_LIB(sqlite) MTN_REMOVE_REDUNDANT_LIB_SWITCHES Some of the logic in the file is specific to the setup on the library-build branch; in particular, it probably makes more sense in the .stripped context to make the minimum version requirement for each library be a second argument to MTN_3RDPARTY_LIB rather than digging it out of the metadata of the bundled copy. Aside to Jack Lloyd: It would be nice if botan provided a .pc file as well as the botan-config executable. zw thirdparty.m4 Description: Binary data ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] nvm.stripped failing check for lua
Hi, Alex Sandro Queiroz e Silva wrote: > The Lua authors have had no problems with breaking API and ABI > compatibility with each new version so far. So programs usually work > with just one version of Lua only. Between 5.0 and 5.1, yes. But I've so far thought that 5.1.x are bugfix releases only. See: http://www.lua.org/bugs.html. That's why I made nvm.stripped require lua 5.1.x (and not 5.0.x). Regards Markus Wanner ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] nvm.stripped failing check for lua
Hallo, Richard Levitte wrote: > > Yes. However, it seems like some packages make the library version > part of the library *name*, to make sure that you link against exactly > that version and none else. > > Why they do so for lua, I've no idea... > The Lua authors have had no problems with breaking API and ABI compatibility with each new version so far. So programs usually work with just one version of Lua only. Cheers, -alex http://www.ventonegro.org/ ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] nvm.stripped failing check for lua
Richard Levitte wrote: Yes. However, it seems like some packages make the library version part of the library *name*, to make sure that you link against exactly that version and none else. In general, this is a real pain in Debian, it means any updates to the library may require all clients to be rebuilt. Unless the library is really unstable and prone to change its API it really isn't required, you just use the library soname. Brian May ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] nvm.stripped failing check for lua
In message <[EMAIL PROTECTED]> on Mon, 13 Oct 2008 23:06:59 -0600, "Derek Scherger" <[EMAIL PROTECTED]> said: derek> On Mon, Oct 13, 2008 at 10:51 PM, Zack Weinberg <[EMAIL PROTECTED]> wrote: derek> derek> > Debian: derek> > derek> > $ (cd /usr/lib && ls -l liblua*) derek> > -rw-r--r-- 1 root root 324860 2008-01-26 08:12 liblua5.1.a derek> > -rw-r--r-- 1 root root825 2008-01-26 08:12 liblua5.1.la derek> > lrwxrwxrwx 1 root root 18 2008-04-01 11:39 liblua5.1.so -> derek> > liblua5.1.so.0.0.0 derek> > lrwxrwxrwx 1 root root 18 2008-03-31 07:09 liblua5.1.so.0 -> derek> > liblua5.1.so.0.0.0 derek> > -rw-r--r-- 1 root root 171696 2008-01-26 08:12 liblua5.1.so.0.0.0 derek> > $ (cd /usr/lib/pkgconfig && ls -l *lua*) derek> > -rw-r--r-- 1 root root 857 2008-01-26 08:12 lua5.1.pc derek> > derek> derek> Wow, that's odd. I thought the version numbers were supposed to come *after* derek> the .so, where all those, um, numbers are? Yes. However, it seems like some packages make the library version part of the library *name*, to make sure that you link against exactly that version and none else. Why they do so for lua, I've no idea... -- Richard Levitte [EMAIL PROTECTED] http://richard.levitte.org/ "Life is a tremendous celebration - and I'm invited!" -- from a friend's blog, translated from Swedish ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] nvm.stripped failing check for lua
On Mon, Oct 13, 2008 at 10:06 PM, Derek Scherger <[EMAIL PROTECTED]> wrote: > On Mon, Oct 13, 2008 at 10:51 PM, Zack Weinberg <[EMAIL PROTECTED]> wrote: >> >> lrwxrwxrwx 1 root root 18 2008-04-01 11:39 liblua5.1.so -> >> liblua5.1.so.0.0.0 >> lrwxrwxrwx 1 root root 18 2008-03-31 07:09 liblua5.1.so.0 -> >> liblua5.1.so.0.0.0 > > Wow, that's odd. I thought the version numbers were supposed to come *after* > the .so, where all those, um, numbers are? yeah, it's bizarre to me too. It *might* have to do with there also being 4.0 and 5.0 iterations of this library in the archive, but that oughta only affect the package names, not the .so names. More likely, it's something that was done a long time ago by someone who didn't know any better and now they're stuck with it. Bleah. zw ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] nvm.stripped failing check for lua
On Mon, Oct 13, 2008 at 10:51 PM, Zack Weinberg <[EMAIL PROTECTED]> wrote: > Debian: > > $ (cd /usr/lib && ls -l liblua*) > -rw-r--r-- 1 root root 324860 2008-01-26 08:12 liblua5.1.a > -rw-r--r-- 1 root root825 2008-01-26 08:12 liblua5.1.la > lrwxrwxrwx 1 root root 18 2008-04-01 11:39 liblua5.1.so -> > liblua5.1.so.0.0.0 > lrwxrwxrwx 1 root root 18 2008-03-31 07:09 liblua5.1.so.0 -> > liblua5.1.so.0.0.0 > -rw-r--r-- 1 root root 171696 2008-01-26 08:12 liblua5.1.so.0.0.0 > $ (cd /usr/lib/pkgconfig && ls -l *lua*) > -rw-r--r-- 1 root root 857 2008-01-26 08:12 lua5.1.pc > Wow, that's odd. I thought the version numbers were supposed to come *after* the .so, where all those, um, numbers are? so, no. I was afraid of that. ;) > I remember writing a bunch of m4 to deal with this problem but it > doesn't seem to be on this computer; I'll look on the other one > tomorrow. > Great, thanks. Cheers, Derek ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] nvm.stripped failing check for lua
On Mon, Oct 13, 2008 at 7:55 PM, Derek Scherger <[EMAIL PROTECTED]> wrote: > - PKG_CHECK_MODULES([LUA], [lua5.1], > + PKG_CHECK_MODULES([LUA], [lua], > > Is this a reasonable change on other systems? Debian: $ (cd /usr/lib && ls -l liblua*) -rw-r--r-- 1 root root 324860 2008-01-26 08:12 liblua5.1.a -rw-r--r-- 1 root root825 2008-01-26 08:12 liblua5.1.la lrwxrwxrwx 1 root root 18 2008-04-01 11:39 liblua5.1.so -> liblua5.1.so.0.0.0 lrwxrwxrwx 1 root root 18 2008-03-31 07:09 liblua5.1.so.0 -> liblua5.1.so.0.0.0 -rw-r--r-- 1 root root 171696 2008-01-26 08:12 liblua5.1.so.0.0.0 $ (cd /usr/lib/pkgconfig && ls -l *lua*) -rw-r--r-- 1 root root 857 2008-01-26 08:12 lua5.1.pc so, no. I remember writing a bunch of m4 to deal with this problem but it doesn't seem to be on this computer; I'll look on the other one tomorrow. zw ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] nvm.stripped failing check for lua
On my system (gentoo) the pkg-config check for lua fails with:
checking for LUA... no
checking for lua 5.1... no; guessing
checking for lua_load in -llua5.1... no
checking whether the lua library is usable... yes
Applying the following patch to patch m4/lua.m4 seems to make it happy:
#
# old_revision [6c5a8fa3d0437be28f59b448a5f72c90267df149]
#
# patch "m4/lua.m4"
# from [1253a38c8df4cb482c3588d3d11e6478952f2b8c]
#to [18918826ac2f2eafefabe1c0038df4b1ab7a881c]
#
--- m4/lua.m41253a38c8df4cb482c3588d3d11e6478952f2b8c
+++ m4/lua.m418918826ac2f2eafefabe1c0038df4b1ab7a881c
@@ -10,7 +10,7 @@ AC_DEFUN([MTN_FIND_LUA],
if test -n "${LUA_CFLAGS+set}" || test -n "${LUA_LIBS+set}"; then
found_liblua=yes
else
- PKG_CHECK_MODULES([LUA], [lua5.1],
+ PKG_CHECK_MODULES([LUA], [lua],
[found_liblua=yes], [found_liblua=no])
fi
checking for LUA... yes
checking whether the lua library is usable... yes
Is this a reasonable change on other systems?
Cheers,
Derek
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/monotone-devel
