is it lua 5.1 really required for Prosody .9.8?

[b...@cogs.com]

I working through installing Prosody and I really like it so far. I have a set-up that seems to be installed but when I try launch prosody I receive the message that I have lua 5.2 installed and lua 5.1 is required.

My question is can I just the ./confiugre to use 5.2 and see what happens?

The system is already running a pre-reales os x 10.11 and Xcode-beta so I'm not risking stability.

Thanks,

Ben

[Thijs Alkemade]

> On 14 aug. 2015, at 00:16, b...@cogs.com wrote:
>
> I working through installing Prosody and I really like it so far. I have a set-up that seems to be installed but when I try launch prosody I receive the message that I have lua 5.2 installed and lua 5.1 is required.
> My question is can I just the ./confiugre to use 5.2 and see what happens?

You really need Lua 5.1. Lua 5.2/5.3 are different languages that are not backwards-compatible with 5.1.

Thijs

[Matthew Wild]

Hi Ben,

Lua 5.2 has major changes that are not backwards-compatible with Lua
5.1. In particular for example, the module() function was removed
which Prosody uses in almost every file in the project :)

We're working on 5.2 support for future releases, but the 0.9.x series
will remain compatible with 5.1 only. This also keeps us compatible
with LuaJIT, which is primarily 5.1-based and doesn't support some of
Lua 5.2's features (yet?).

Regards,
Matthew

> --
> You received this message because you are subscribed to the Google Groups
> "prosody-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to prosody-dev...@googlegroups.com.
> To post to this group, send email to proso...@googlegroups.com.
> Visit this group at http://groups.google.com/group/prosody-dev.
> For more options, visit https://groups.google.com/d/optout.

[Vadim A. Misbakh-Soloviov]

> You really need Lua 5.1. Lua 5.2/5.3 are different languages that are not
> backwards-compatible with 5.1.

Not exactly. They are compatible, if they were built with compatibility CFLAGS
(not sure, if macos maintainers do that).


Anyway, TS (ben), it is nothing that can stop you from try to run ./configure
with lua52/53

--
Best regards,
mva

[b...@cogs.com]

On Friday, August 14, 2015 at 6:35:41 AM UTC-4, Вадим Мисбах-Соловьёв wrote:

> You really need Lua 5.1. Lua 5.2/5.3 are different languages that are not
> backwards-compatible with 5.1.

Not exactly. They are compatible, if they were built with compatibility CFLAGS
(not sure, if macos maintainers do that).

I'm currently updating my local portfile from macports to try to build and install prosody.

The existing file was for .9.1 but it failed to install. I updated it to grab .9.8 source and used the 

port install lua lua-luasocket lua-luasec lua-luaexpat

From the installing prosody page for the macports.  I have a file that now installs prosody but it won't run due to 5.1 dependencies.

 

Anyway, TS (ben), it is nothing that can stop you from try to run ./configure
with lua52/53

I work on this change and see if I can launch prosody. Otherwise I will want to try and get a MacPorts install of 5.1 to work. It currently fails with lua-luaexpat problems.

Thanks for your help.

 

--
Best regards,
mva

[b...@cogs.com]

On Friday, August 14, 2015 at 6:32:49 AM UTC-4, Matthew Wild wrote:

Hi Ben,

Lua 5.2 has major changes that are not backwards-compatible with Lua
5.1. In particular for example, the module() function was removed
which Prosody uses in almost every file in the project :)

We're working on 5.2 support for future releases, but the 0.9.x series
will remain compatible with 5.1 only.

Is there a branch available that is compatible ?

Currently build repeatability is a higher priority then stability. 

 

This also keeps us compatible
with LuaJIT, which is primarily 5.1-based and doesn't support some of

The LuaJit in macports is version 2.0.4 is that what I should be targeting?

 

Thanks, 

Ben

[Matthew Wild]

On 14 August 2015 at 12:39, <b...@cogs.com> wrote:
>
>
>
> On Friday, August 14, 2015 at 6:32:49 AM UTC-4, Matthew Wild wrote:
>>
>> Hi Ben,
>>
>> Lua 5.2 has major changes that are not backwards-compatible with Lua
>> 5.1. In particular for example, the module() function was removed
>> which Prosody uses in almost every file in the project :)
>>
>> We're working on 5.2 support for future releases, but the 0.9.x series
>> will remain compatible with 5.1 only.
>
>
> Is there a branch available that is compatible ?
>
> Currently build repeatability is a higher priority then stability.

Only our 'timber' branch, which is definitely not stable, as it is a
playground for various experiments: https://hg.prosody.im/timber

And by unstable I don't mean it's likely to crash, though you might
experience errors or even incorrect behaviour (messages being routed
incorrectly). But if you use it and find any issues, please let us
know!

>> This also keeps us compatible
>> with LuaJIT, which is primarily 5.1-based and doesn't support some of
>
>
> The LuaJit in macports is version 2.0.4 is that what I should be targeting?

Any current version of LuaJIT should work with 0.9.x, as they are all
5.1-compatible.

Regards,
Matthew

[b...@cogs.com]

On Friday, August 14, 2015 at 8:30:09 AM UTC-4, Matthew Wild wrote:

On 14 August 2015 at 12:39, <b...@cogs.com> wrote:
>
>
>
> On Friday, August 14, 2015 at 6:32:49 AM UTC-4, Matthew Wild wrote:
>>
>> Hi Ben,
>>
>> Lua 5.2 has major changes that are not backwards-compatible with Lua
>> 5.1. In particular for example, the module() function was removed
>> which Prosody uses in almost every file in the project :)
>>
>> We're working on 5.2 support for future releases, but the 0.9.x series
>> will remain compatible with 5.1 only.
>
>
> Is there a branch available that is compatible ?
>
> Currently build repeatability is a higher priority then stability.

Only our 'timber' branch, which is definitely not stable, as it is a
playground for various experiments: https://hg.prosody.im/timber

And by unstable I don't mean it's likely to crash, though you might
experience errors or even incorrect behaviour (messages being routed
incorrectly). But if you use it and find any issues, please let us
know!

Sounds good.

I have downloaded the timber trunk and I'm working through getting it build.

currently it's failing with this linker error. Which I isolated to util-src Makefile.

slim# pwd                      

/Users/Shared/prosody/timber-trunk/util-src

slim# make       

MACOSX_DEPLOYMENT_TARGET="10.3"; export MACOSX_DEPLOYMENT_TARGET;

gcc -o encodings.so encodings.o -bundle -undefined dynamic_lookup -lidn

ld: library not found for -lidn

clang: error: linker command failed with exit code 1 (use -v to see invocation)

make: *** [encodings.so] Error 1

I have been using the paths of my macports lua installation with the intent that I will turn the manual installation into a macports portfile for at least my own local use.

Any ideas appreciated.

Ben

[Matthew Wild]

On 14 August 2015 at 16:57, <b...@cogs.com> wrote:
> I have downloaded the timber trunk and I'm working through getting it build.
> currently it's failing with this linker error. Which I isolated to util-src
> Makefile.
>
> slim# pwd
> /Users/Shared/prosody/timber-trunk/util-src
> slim# make
> MACOSX_DEPLOYMENT_TARGET="10.3"; export MACOSX_DEPLOYMENT_TARGET;
> gcc -o encodings.so encodings.o -bundle -undefined dynamic_lookup -lidn
> ld: library not found for -lidn
> clang: error: linker command failed with exit code 1 (use -v to see
> invocation)
> make: *** [encodings.so] Error 1
>
> I have been using the paths of my macports lua installation with the intent
> that I will turn the manual installation into a macports portfile for at
> least my own local use.
> Any ideas appreciated.

I'm not an OS X user, but this error indicates that you do not have
(or the linker cannot find) the libidn library, which is one of
Prosody's build dependencies:
https://prosody.im/doc/installing_from_source#dependencies

Hope this helps a bit.

Regards,
Matthew

[b...@cogs.com]

Thank you that was a big help. I looked at the linker and found that the 

timber-trunk/util-src/Makefile

IDN_LIB?=idn

in later code referred to in the plural IDNA_LIBS which I changed to the singular IDNA_LIB.

I also found that the existing macports Portfile for for prosody version .9.1 included an extra dependency libidn not listed 

https://prosody.im/doc/install#source

This page lists this command to install dependencies using macports and OS X

port install lua lua-luasocket lua-luasec lua-luaexpat 

this should be

port install lua lua-luasocket lua-luasec lua-luaexpat libidn

That command successfully installs all the dependencies and I can build either .9.8 or timber.

Once those are installed I'm still faced with the original problem that neither prosody version will run on lua 5.2.

My question is now focused on what configure args should I use to get timber to use lua version 5.2.

Thanks for all the help so far.

Ben

Regards,
Matthew

[Matthew Wild]

On 14 August 2015 at 20:02, <b...@cogs.com> wrote:
> My question is now focused on what configure args should I use to get timber
> to use lua version 5.2.

./configure --runwith=lua5.2

Change 'lua5.2' to whatever the path is to your Lua 5.2 interpreter.

Regards,
Matthew

[b...@cogs.com]

I have tried it a few ways but below is a transcript starting from the removal of prosody timber until the launching of the fresh binary that displays the message.

Thanks for your help.

Ben

slim# rm /opt/local/bin/prosody

slim# ./configure --ostype=macosx  --with-lua=/opt/local/bin/lua

-n Checking Lua includes... 

lua.h found in /opt/local/include/lua.h

Writing configuration...

Installation prefix: /opt/local

Prosody configuration directory: /opt/local/etc/prosody

Using Lua from: /opt/local/bin/lua

Done. You can now run 'make' to build.

slim# make

sed "1s| lua$| lua|; \

s|^CFG_SOURCEDIR=.*;$|CFG_SOURCEDIR='/opt/local/lib/prosody';|; \

s|^CFG_CONFIGDIR=.*;$|CFG_CONFIGDIR='/opt/local/etc/prosody';|; \

s|^CFG_DATADIR=.*;$|CFG_DATADIR='/opt/local/var/lib/prosody';|; \

s|^CFG_PLUGINDIR=.*;$|CFG_PLUGINDIR='/opt/local/lib/prosody/modules/';|;" < prosody > prosody.install

sed "1s| lua$| lua|; \

s|^CFG_SOURCEDIR=.*;$|CFG_SOURCEDIR='/opt/local/lib/prosody';|; \

s|^CFG_CONFIGDIR=.*;$|CFG_CONFIGDIR='/opt/local/etc/prosody';|; \

s|^CFG_DATADIR=.*;$|CFG_DATADIR='/opt/local/var/lib/prosody';|; \

s|^CFG_PLUGINDIR=.*;$|CFG_PLUGINDIR='/opt/local/lib/prosody/modules/';|;" < prosodyctl > prosodyctl.install

sed 's|certs/|/opt/local/etc/prosody/certs/|' prosody.cfg.lua.dist > prosody.cfg.lua.install

test -e .hg/dirstate && \

hexdump -n6 -e'6/1 "%02x"' .hg/dirstate > prosody.version || true

test -f prosody.release && \

cp prosody.release prosody.version || true

/Applications/Xcode-beta.app/Contents/Developer/usr/bin/make -C util-src install

gcc -fPIC -Wall -ggdb -I/opt/local/include -c -o encodings.o encodings.c

MACOSX_DEPLOYMENT_TARGET="10.3"; export MACOSX_DEPLOYMENT_TARGET;

gcc -o encodings.so encodings.o -bundle -undefined dynamic_lookup 

gcc -fPIC -Wall -ggdb -I/opt/local/include -c -o hashes.o hashes.c

MACOSX_DEPLOYMENT_TARGET="10.3"; export MACOSX_DEPLOYMENT_TARGET;

gcc -o hashes.so hashes.o -bundle -undefined dynamic_lookup -lcrypto

gcc -fPIC -Wall -ggdb -I/opt/local/include -c -o net.o net.c

MACOSX_DEPLOYMENT_TARGET="10.3"; export MACOSX_DEPLOYMENT_TARGET;

gcc -o net.so net.o -bundle -undefined dynamic_lookup

gcc -fPIC -Wall -ggdb -I/opt/local/include -c -o pposix.o pposix.c

MACOSX_DEPLOYMENT_TARGET="10.3"; export MACOSX_DEPLOYMENT_TARGET;

gcc -o pposix.so pposix.o -bundle -undefined dynamic_lookup

gcc -fPIC -Wall -ggdb -I/opt/local/include -c -o signal.o signal.c

MACOSX_DEPLOYMENT_TARGET="10.3"; export MACOSX_DEPLOYMENT_TARGET;

gcc -o signal.so signal.o -bundle -undefined dynamic_lookup

gcc -fPIC -Wall -ggdb -I/opt/local/include -c -o table.o table.c

MACOSX_DEPLOYMENT_TARGET="10.3"; export MACOSX_DEPLOYMENT_TARGET;

gcc -o table.so table.o -bundle -undefined dynamic_lookup

install *.so ../util/

rm table.o net.o pposix.o signal.o

/Applications/Xcode-beta.app/Contents/Developer/usr/bin/make -C certs localhost.crt example.com.crt || true

make[1]: `localhost.crt' is up to date.

make[1]: `example.com.crt' is up to date.

slim# make install

install -d /opt/local/bin /opt/local/etc/prosody /opt/local/lib/prosody/modules /opt/local/lib/prosody

install -m750 -d /opt/local/var/lib/prosody

install -d /opt/local/share/man/man1

install -d /opt/local/etc/prosody/certs

install -d /opt/local/lib/prosody/core /opt/local/lib/prosody/net /opt/local/lib/prosody/util

install -m755 ./prosody.install /opt/local/bin/prosody

install -m755 ./prosodyctl.install /opt/local/bin/prosodyctl

install -m644 core/* /opt/local/lib/prosody/core

install -m644 net/*.lua /opt/local/lib/prosody/net

install -d /opt/local/lib/prosody/net/http /opt/local/lib/prosody/net/websocket

install -m644 net/http/*.lua /opt/local/lib/prosody/net/http

install -m644 net/websocket/*.lua /opt/local/lib/prosody/net/websocket

install -m644 util/*.lua /opt/local/lib/prosody/util

install -m644 util/*.so /opt/local/lib/prosody/util

install -d /opt/local/lib/prosody/util/sasl

install -m644 util/sasl/* /opt/local/lib/prosody/util/sasl

umask 0022 && cp -r plugins/* /opt/local/lib/prosody/modules

install -m644 certs/* /opt/local/etc/prosody/certs

install -m644 man/prosodyctl.man /opt/local/share/man/man1/prosodyctl.1

test -e /opt/local/etc/prosody/prosody.cfg.lua || install -m644 prosody.cfg.lua.install /opt/local/etc/prosody/prosody.cfg.lua

test -e prosody.version && install -m644 prosody.version /opt/local/lib/prosody/prosody.version || true

/Applications/Xcode-beta.app/Contents/Developer/usr/bin/make install -C util-src

install *.so ../util/

slim# prosody

***********************************

Unsupported Lua version: Lua 5.2

Only Lua 5.1 is supported.

***********************************

 

Regards,
Matthew

[Matthew Wild]

Hi Ben,

I think you are building or running the wrong code, as timber would
not display this message for Lua 5.2.

Try running '/opt/local/bin/prosody' instead of just 'prosody'. Also
as a quick check, you can run: grep "if _VERSION"
util/dependencies.lua

If you have timber, the grep will show: if _VERSION < "Lua 5.1".

Regards,
Matthew

[b...@cogs.com]

On Saturday, August 15, 2015 at 6:26:17 AM UTC-4, Matthew Wild wrote:

Hi Ben,

I think you are building or running the wrong code, as timber would
not display this message for Lua 5.2.

could be here is my mercurial line that I'm using to get timber

slim# hg clone https://hg.prosody.im/trunk timber-trunk

requesting all changes

adding changesets

adding manifests

adding file changes

added 6771 changesets with 7712 changes to 314 files                                                                                                                                          

updating to branch default

231 files updated, 0 files merged, 0 files removed, 0 files unresolved

Try running '/opt/local/bin/prosody' instead of just 'prosody'. Also
as a quick check, you can run: grep "if _VERSION"
util/dependencies.lua

grep "if _VERSION" util/dependencies.lua

if _VERSION ~= "Lua 5.1" then

That is true for the source I have been using and a fresh folder using the mercurial clone command used above.

Thank you for your help I think we are getting very close.

Ben

[Matthew Wild]

On 15 August 2015 at 12:30, <b...@cogs.com> wrote:
>
>
> On Saturday, August 15, 2015 at 6:26:17 AM UTC-4, Matthew Wild wrote:
>>
>> Hi Ben,
>>
>> I think you are building or running the wrong code, as timber would
>> not display this message for Lua 5.2.
>
>
> could be here is my mercurial line that I'm using to get timber
>
> slim# hg clone https://hg.prosody.im/trunk timber-trunk

This is incorrect. Just clone the URL I gave you earlier: hg clone
https://hg.prosody.im/timber

Then you should be good :)

Regards,
Matthew

[b...@cogs.com]

I changed my timber-trunk util/dependencies.lua and prosody launched. Prosody is now prompting it is unable to fine luafilesystem, LuaSec and util.encodings.

This is really great I think I can now focus on the details of getting the build to happen.

Thank you for your help. I'm really psyched at how simple Prosody is to work with.

Ben

 

Regards,
Matthew

[Matthew Wild]

Great. But just so you know, changing the version check is not all
that is required to make Prosody work with 5.2 :) If you have the
wrong version of the code (trunk) then remember it still won't work
until you switch to timber. We have no branch called "timber-trunk".

The dependency warnings you see now are for the C libraries that
Prosody needs, they need to be compiled for Lua 5.2 also (and in Lua
5.2's search paths). Once you have those, you'll have passed all the
dependency checks.

Regards,
Matthew

[b...@cogs.com]

Ok I coned that directory and all I had to do was edit the /util-src/Makefile I mentioned earlier.

That built a running Prosody that is unable to find the luafilesystem, LuaSec and util.encodings.

I will try to figure out what the right settings and try to get them into the macosx section of the configure script.

Thank you,

Ben

[Matthew Wild]

On 15 August 2015 at 13:11, <b...@cogs.com> wrote:
>
>
> On Saturday, August 15, 2015 at 7:33:42 AM UTC-4, Matthew Wild wrote:
>>
>> On 15 August 2015 at 12:30, <b...@cogs.com> wrote:
>> >
>> >
>> > On Saturday, August 15, 2015 at 6:26:17 AM UTC-4, Matthew Wild wrote:
>> >>
>> >> Hi Ben,
>> >>
>> >> I think you are building or running the wrong code, as timber would
>> >> not display this message for Lua 5.2.
>> >
>> >
>> > could be here is my mercurial line that I'm using to get timber
>> >
>> > slim# hg clone https://hg.prosody.im/trunk timber-trunk
>>
>> This is incorrect. Just clone the URL I gave you earlier: hg clone
>> https://hg.prosody.im/timber
>
> Ok I coned that directory and all I had to do was edit the
> /util-src/Makefile I mentioned earlier.
>
> That built a running Prosody that is unable to find the luafilesystem,
> LuaSec and util.encodings.

Not finding util.encodings is a bit strange. Check what happens when
you run: lua5.2 -l util.encodings (in the directory where you ran
'make')

If you're around for a bit and want some realtime help, I'm around in
the chatroom[1] right now and you're always welcome :)

Regards,
Matthew

[1]: https://prosody.im/discuss#chatroom

[b...@cogs.com]

Hello Matthew,

On Saturday, August 15, 2015 at 8:15:22 AM UTC-4, Matthew Wild wrote:

On 15 August 2015 at 13:11,  <b...@cogs.com> wrote:
>
>
> On Saturday, August 15, 2015 at 7:33:42 AM UTC-4, Matthew Wild wrote:
>>
>> On 15 August 2015 at 12:30,  <b...@cogs.com> wrote:
>> >
>> >
>> > On Saturday, August 15, 2015 at 6:26:17 AM UTC-4, Matthew Wild wrote:
>> >>
>> >> Hi Ben,
>> >>
>> >> I think you are building or running the wrong code, as timber would
>> >> not display this message for Lua 5.2.
>> >
>> >
>> > could be here is my mercurial line that I'm using to get timber
>> >
>> > slim# hg clone https://hg.prosody.im/trunk timber-trunk
>>
>> This is incorrect. Just clone the URL I gave you earlier: hg clone
>> https://hg.prosody.im/timber
>
> Ok I coned that directory and all I had to do was edit the
> /util-src/Makefile I mentioned earlier.
>
> That built a running Prosody that is unable to find the luafilesystem,
> LuaSec and util.encodings.

Not finding util.encodings is a bit strange. Check what happens when
you run: lua5.2 -l util.encodings (in the directory where you ran
'make')

Here is the current results. I will describe what I think is currently going on.

 

slim#  lua -l util.encodings    

lua: error loading module 'util.encodings' from file './util/encodings.so':

dlopen(./util/encodings.so, 6): Symbol not found: _stringprep_nameprep

  Referenced from: ./util/encodings.so

  Expected in: flat namespace

 in ./util/encodings.so

stack traceback:

[C]: in ?

[C]: in function 'require'

[C]: in ?

 

I have done some digging and I have it on good authority that on the macports-dev list that

"the appropriate -I at compile time is currently being used to find MacPorts-installed headers, but no matching -L at link time to find MacPorts-installed libraries"

 I found that timber user config.unix IDNA_LIBS=-L/opt/local/lib eliminated my linker error and I could build timber.

I guess this setting should happen under the macosx setting due to platforms use of two-level spacing. 

I also don't think that will be the final tweak needed.

I think we may need to set LDFLAGS to flatten namespaces.

ld a.o b.o c.o ... -L/opt/local/lib -lidn

I think I have found where to deal with the settings inside macports but I'm not sure what is required to the util.encodings.so to build.

LuaSec is also missing that I have luasec installed and I wonder if it could be camel casing problem,

Should we consider this thread done and I can start a new thread if I have any more questions?

Thanks,

Ben

[Kim Alvefur]

Hi Ben,

FWIW, the changes needed to run Prosody on Lua 5.2 have been fiddled
over from timber to the 0.10 and trunk branches.

--
Regards,
Kim "Zash" Alvefur

[b...@cogs.com]

On Thursday, August 20, 2015 at 6:07:52 PM UTC-4, Kim Alvefur wrote:

Hi Ben,

FWIW, the changes needed to run Prosody on Lua 5.2 have been fiddled
over from timber to the 0.10 and trunk branches.

Wow that is great! I might try to modify the Portfile in macports for 0.10 release and the missing dependencies.

That brings up another thing I ran into with the ./configure I see that setting ostype to macosx sets the paths  homebrew so I was thinking that adding an ostype for macports would set the path and LDFLAGS for macports.

I have timber up and running is it a dead branch?

Now that I have a repeatable build LDAP/kerberos is my next priority. 

Thanks,

Ben

[Kim Alvefur]

On 2015-08-24 13:56, b...@cogs.com wrote:
> That brings up another thing I ran into with the ./configure I see that
> setting ostype to macosx sets the paths homebrew so I was thinking that
> adding an ostype for macports would set the path and LDFLAGS for macports.

Sounds good.

> I have timber up and running is it a dead branch?

No, not dead, just a bit of a mess right now. There are still some
features in timber that are planned to be moved to 0.10.

--
Kim "Zash" Alvefur