Re: jabberd-2.4.0 release
On Tue, 31 May 2016 09:52:38 +0200 Tomasz Sterna wrote: > W dniu 31.05.2016, wto o godzinie 00∶39 -0700, użytkownik > li...@lazygranch.com napisał: > > ./configure --with-extra-library-path /usr/local/lib --with-extra- > > include-path /usr/local/include > > yielded > > > > checking build system type... /usr/local/lib > > configure: error: invalid value of canonical build > > Double-dash options format is: > --long-option=value > > So, you need: > ./configure --with-extra-library-path=/usr/local/lib > --with-extra-include-path=/usr/local/include > > That works. It isn't finding the config files which I assume I can fix on the command line. The point is the new binary is running. Thanks for your help.
Re: jabberd-2.4.0 release
W dniu 31.05.2016, wto o godzinie 00∶39 -0700, użytkownik li...@lazygranch.com napisał: > ./configure --with-extra-library-path /usr/local/lib --with-extra- > include-path /usr/local/include > yielded > > checking build system type... /usr/local/lib > configure: error: invalid value of canonical build Double-dash options format is: --long-option=value So, you need: ./configure --with-extra-library-path=/usr/local/lib --with-extra-include-path=/usr/local/include -- /o__ In case of injury notify your superior immediately. He'll kiss it and (_<^' make it better.
Re: jabberd-2.4.0 release
On Sat, 28 May 2016 08:16:50 +0200 Tomasz Sterna wrote: > W dniu 27.05.2016, pią o godzinie 19∶14 -0700, użytkownik > li...@lazygranch.com napisał: > > Do you have both expat and its headers installed? > > Verify headers: > > /usr/local/include > > > > So is this a flag or environment variable I need to set? > > Yes. > > $ ./configure --help > [...] > --with-extra-include-path > use additional include paths > --with-extra-library-path > use additional library paths (remember to > update > /etc/ld.so.conf too) I'm guessing the library command you suggested is ldconfig. In any event, ./configure --with-extra-library-path /usr/local/lib --with-extra-include-path /usr/local/include yielded checking build system type... /usr/local/lib configure: error: invalid value of canonical build I'm just going to wait for the freebsd port.
Re: jabberd-2.4.0 release
W dniu 28.05.2016, sob o godzinie 11∶48 -0700, użytkownik li...@lazygranch.com napisał: > Right. But what exactly do I update? Sorry... I am a Linux guy, not familiar with FreeBSD internals. But I am pretty sure, FreeBSD also has some kind of dynamic linker. Seek its documentation. > I don't understand this: > > remember to update /etc/ld.so.conf too > Common issue is to build jabberd2 against libraries in non-standard > path and then jabberd2 fails to run, because dynamic linker cannot > find > these libraries. > This is a reminder, to update dynamic linker configuration file. -- smoku @ http://abadcafe.pl/ @ http://xiaoka.com/ signature.asc Description: This is a digitally signed message part
Re: jabberd-2.4.0 release
Right. But what exactly do I update? Original Message From: Tomasz Sterna Sent: Saturday, May 28, 2016 7:20 AM To: jabberd2@lists.xiaoka.com Reply To: jabberd2@lists.xiaoka.com Subject: Re: jabberd-2.4.0 release W dniu 27.05.2016, pią o godzinie 23∶57 -0700, użytkownik li...@lazygranch.com napisał: > I don't understand this: > remember to update /etc/ld.so.conf too Common issue is to build jabberd2 against libraries in non-standard path and then jabberd2 fails to run, because dynamic linker cannot find these libraries. This is a reminder, to update dynamic linker configuration file. -- smoku @ http://abadcafe.pl/ @ http://xiaoka.com/
Re: jabberd-2.4.0 release
W dniu 27.05.2016, pią o godzinie 23∶57 -0700, użytkownik li...@lazygranch.com napisał: > I don't understand this: > remember to update /etc/ld.so.conf too Common issue is to build jabberd2 against libraries in non-standard path and then jabberd2 fails to run, because dynamic linker cannot find these libraries. This is a reminder, to update dynamic linker configuration file. -- smoku @ http://abadcafe.pl/ @ http://xiaoka.com/ signature.asc Description: This is a digitally signed message part
Re: jabberd-2.4.0 release
Sorry for the top posting (smartphone) . I though it would be interesting to look at how the program is compiled in /usr/ports. (As far as I know, just look in the work directory.) The environment is the same. The configure file looked the same except for the rev difference. Baffling! Anyway, I can handle the flags on the configure file, but I don't understand this: remember to update /etc/ld.so.conf too Original Message From: Tomasz Sterna Sent: Friday, May 27, 2016 11:30 PM To: jabberd2@lists.xiaoka.com Reply To: jabberd2@lists.xiaoka.com Subject: Re: jabberd-2.4.0 release W dniu 27.05.2016, pią o godzinie 19∶14 -0700, użytkownik li...@lazygranch.com napisał: > Do you have both expat and its headers installed? > Verify headers: > /usr/local/include > > So is this a flag or environment variable I need to set? Yes. $ ./configure --help [...] --with-extra-include-path use additional include paths --with-extra-library-path use additional library paths (remember to update /etc/ld.so.conf too) -- smoku @ http://abadcafe.pl/ @ http://xiaoka.com/
Re: jabberd-2.4.0 release
W dniu 27.05.2016, pią o godzinie 19∶14 -0700, użytkownik li...@lazygranch.com napisał: > Do you have both expat and its headers installed? > Verify headers: > /usr/local/include > > So is this a flag or environment variable I need to set? Yes. $ ./configure --help [...] --with-extra-include-path use additional include paths --with-extra-library-path use additional library paths (remember to update /etc/ld.so.conf too) -- smoku @ http://abadcafe.pl/ @ http://xiaoka.com/ signature.asc Description: This is a digitally signed message part
Re: jabberd-2.4.0 release
On Fri, 27 May 2016 19:29:43 +0200 Tomasz Sterna wrote: > W dniu 27.05.2016, pią o godzinie 00∶09 -0700, użytkownik > li...@lazygranch.com napisał: > > Actually I had downloaded jabberd-2.4.0.tar.gz. [...] > > Doing some internet search, it is suggested the procedure should be: > > aclocal > > automake --add-missing > > autoconf > > ./configure > > Using jabberd-2.4.0.tar.gz you do not need to do autotools stuff. > Just: > > ./configure > make > sudo make install > > > > I get this error message: > > -- > > checking for XML_ParserCreate in -lexpat... no > > configure: error: Expat not found > > configure cannot find Expat [1]. > Do you have both expat and its headers installed? > > [1] http://www.libexpat.org/ > Verify headers: - # pwd /usr/local/include # ls expat* expat.h expat_config.h expat_external.h Verify expat: - # pwd /usr/local/lib # ls libexpat* libexpat.a libexpat.so.1 libexpat.so.6 libexpat.so libexpat.so.1.6.0 -- So is this a flag or environment variable I need to set?
Re: jabberd-2.4.0 release
W dniu 27.05.2016, pią o godzinie 00∶09 -0700, użytkownik li...@lazygranch.com napisał: > Actually I had downloaded jabberd-2.4.0.tar.gz. [...] > Doing some internet search, it is suggested the procedure should be: > aclocal > automake --add-missing > autoconf > ./configure Using jabberd-2.4.0.tar.gz you do not need to do autotools stuff. Just: ./configure make sudo make install > I get this error message: > -- > checking for XML_ParserCreate in -lexpat... no > configure: error: Expat not found configure cannot find Expat [1]. Do you have both expat and its headers installed? [1] http://www.libexpat.org/ -- /o__ (_<^' Honk if you are against noise pollution! signature.asc Description: This is a digitally signed message part
Re: jabberd-2.4.0 release
I'm on freebsd 10.2 Original Message From: Matěj Cepl Sent: Friday, May 27, 2016 9:31 AM To: jabberd2@lists.xiaoka.com Reply To: jabberd2@lists.xiaoka.com Subject: Re: jabberd-2.4.0 release On 2016-05-27, 07:09 GMT, li...@lazygranch.com wrote: > I get this error message: > -- > checking for XML_ParserCreate in -lexpat... no > configure: error: Expat not found > -- > I have expat, so it is a matter of configure not finding it. Do you have appropriate -dev (for Debian), or -devel (for Fedora/SUSE) package installed? Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 Less is more or less more. -- Y_Plentyn on #LinuxGER (from fortunes -- I cannot resist :-)
Re: jabberd-2.4.0 release
On 2016-05-27, 07:09 GMT, li...@lazygranch.com wrote: > I get this error message: > -- > checking for XML_ParserCreate in -lexpat... no > configure: error: Expat not found > -- > I have expat, so it is a matter of configure not finding it. Do you have appropriate -dev (for Debian), or -devel (for Fedora/SUSE) package installed? Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 Less is more or less more. -- Y_Plentyn on #LinuxGER (from fortunes -- I cannot resist :-)
Re: jabberd-2.4.0 release
On Fri, May 27, 2016 at 12:09:41AM -0700, li...@lazygranch.com wrote: > On Fri, 27 May 2016 06:22:01 +0200 > Tomasz Sterna wrote: > > > W dniu 26.05.2016, czw o godzinie 19∶46 -0700, użytkownik > > li...@lazygranch.com napisał: > > > This is from my attempt to compile the tar.gz file after doing > > > autoreconf -i > > > ./configure > > > > > > I get > > > ./configure: 12735: Syntax error: word unexpected (expecting ")") > > > > > > Do not use the source labeled "Source code (tar.gz)" - this is plain > > git source dump, not ready for direct consumption. > > > > Use the source labeled jabberd-2.4.0.tar.xz or jabberd-2.4.0.tar.gz > > (the ones with .asc signatures). These are prepared, with ./configure > > script etc. generated. > > > > > > > > P.S. or install autoconf-archive package > > > > Actually I had downloaded jabberd-2.4.0.tar.gz. However I downloaded > the xz file. I also installed autoconf-archive, though I don't know how > I'm supposed to use it. > > Doing some internet search, it is suggested the procedure should be: > aclocal > automake --add-missing > autoconf > ./configure > > I get this error message: > -- > checking for XML_ParserCreate in -lexpat... no > configure: error: Expat not found > -- > I have expat, so it is a matter of configure not finding it. As a reference: The Fedora package was also built from jabberd-2.4.0.tar.gz without any problems. https://kojipkgs.fedoraproject.org//packages/jabberd/2.4.0/1.fc25/data/logs/x86_64/build.log Adrian signature.asc Description: PGP signature
Re: jabberd-2.4.0 release
On Fri, 27 May 2016 06:22:01 +0200 Tomasz Sterna wrote: > W dniu 26.05.2016, czw o godzinie 19∶46 -0700, użytkownik > li...@lazygranch.com napisał: > > This is from my attempt to compile the tar.gz file after doing > > autoreconf -i > > ./configure > > > > I get > > ./configure: 12735: Syntax error: word unexpected (expecting ")") > > > Do not use the source labeled "Source code (tar.gz)" - this is plain > git source dump, not ready for direct consumption. > > Use the source labeled jabberd-2.4.0.tar.xz or jabberd-2.4.0.tar.gz > (the ones with .asc signatures). These are prepared, with ./configure > script etc. generated. > > > > P.S. or install autoconf-archive package > Actually I had downloaded jabberd-2.4.0.tar.gz. However I downloaded the xz file. I also installed autoconf-archive, though I don't know how I'm supposed to use it. Doing some internet search, it is suggested the procedure should be: aclocal automake --add-missing autoconf ./configure I get this error message: -- checking for XML_ParserCreate in -lexpat... no configure: error: Expat not found -- I have expat, so it is a matter of configure not finding it. Actually I had downloaded jabberd-2.4.0.tar.gz. However I downloaded the xz file. I also installed autoconf-archive, though I don't know how I'm supposed to use it. Doing some internet search, it is suggested the procedure should be: aclocal automake --add-missing autoconf ./configure I get this error message: -- checking for XML_ParserCreate in -lexpat... no configure: error: Expat not found -- I have expat, so it is a matter of configure not finding it.
Re: jabberd-2.4.0 release
W dniu 26.05.2016, czw o godzinie 19∶46 -0700, użytkownik li...@lazygranch.com napisał: > This is from my attempt to compile the tar.gz file after doing > autoreconf -i > ./configure > > I get > ./configure: 12735: Syntax error: word unexpected (expecting ")") Do not use the source labeled "Source code (tar.gz)" - this is plain git source dump, not ready for direct consumption. Use the source labeled jabberd-2.4.0.tar.xz or jabberd-2.4.0.tar.gz (the ones with .asc signatures). These are prepared, with ./configure script etc. generated. P.S. or install autoconf-archive package -- /o__ (_<^' As famous as the unknown soldier. signature.asc Description: This is a digitally signed message part
Re: jabberd-2.4.0 release
On Mon, 23 May 2016 21:53:36 +0200 Tomasz Sterna wrote: > W dniu 23.05.2016, pon o godzinie 15∶38 -0400, użytkownik Greg Troxel > napisał: > > Does this imply that it should be safe, aside from cautions in NEWS, > > to update a machine running 2.3.x to 2.4.0? > > Yes. No breaking changes. > > > Often a minor version change indicates something more dramatic than > > bugfixes, so I thought I would ask. > > I am attempting to follow http://semver.org/ so every release should > bring up MINOR number, with PATCH reserved for fixing screw-ups in > MINOR release. > > 2.4.0 fixes bugs in XMPP/XEP/daemons implementation, not in the > release process itself. > > So, expect 2.5.0 to follow up, not 2.4.1. > > > This is from my attempt to compile the tar.gz file after doing autoreconf -i ./configure I get ./configure: 12735: Syntax error: word unexpected (expecting ")") Using vim on configure: # Colorized build output AX_CHECK_COMPILE_FLAG(-fdiagnostics-color, CFLAGS="${CFLAGS} -fdiagnostics-color", AX_CHECK_COMPILE_FLAG([-fcolor-diagnostics], [CFLAGS="${CFLAGS} -fcolor-diagnostics"]))
Re: jabberd-2.4.0 release
Tomasz Sterna writes: > W dniu 23.05.2016, pon o godzinie 15∶38 -0400, użytkownik Greg Troxel > napisał: >> Does this imply that it should be safe, aside from cautions in NEWS, >> to update a machine running 2.3.x to 2.4.0? > > Yes. No breaking changes. > >> Often a minor version change indicates something more dramatic than >> bugfixes, so I thought I would ask. > > I am attempting to follow http://semver.org/ so every release should > bring up MINOR number, with PATCH reserved for fixing screw-ups in > MINOR release. > > 2.4.0 fixes bugs in XMPP/XEP/daemons implementation, not in the release > process itself. > > So, expect 2.5.0 to follow up, not 2.4.1. Thanks. That's a change in versioning policy, but makes sense. I tend to update the pkgsrc entry, and wanted to get a sense of how cautious I should be since other people, absent effort, get whatever udpates I commit. signature.asc Description: PGP signature
Re: jabberd-2.4.0 release
W dniu 23.05.2016, pon o godzinie 15∶38 -0400, użytkownik Greg Troxel napisał: > Does this imply that it should be safe, aside from cautions in NEWS, > to update a machine running 2.3.x to 2.4.0? Yes. No breaking changes. > Often a minor version change indicates something more dramatic than > bugfixes, so I thought I would ask. I am attempting to follow http://semver.org/ so every release should bring up MINOR number, with PATCH reserved for fixing screw-ups in MINOR release. 2.4.0 fixes bugs in XMPP/XEP/daemons implementation, not in the release process itself. So, expect 2.5.0 to follow up, not 2.4.1. -- /o__ (_<^' Captain's Log, star date 21:34.5... signature.asc Description: This is a digitally signed message part
Re: jabberd-2.4.0 release
Tomasz Sterna writes: > Next jabberd2 release is available. > > Get 2.4.0 release at GitHub: > https://github.com/jabberd2/jabberd2/releases > > This is a bugfix release. Does this imply that it should be safe, aside from cautions in NEWS, to update a machine running 2.3.x to 2.4.0? Often a minor version change indicates something more dramatic than bugfixes, so I thought I would ask. In other words, why isn't this 2.3.N+1? signature.asc Description: PGP signature
jabberd-2.4.0 release
Next jabberd2 release is available. Get 2.4.0 release at GitHub: https://github.com/jabberd2/jabberd2/releases This is a bugfix release. Make sure to read the NEWS before upgrade: https://github.com/jabberd2/jabberd2/blob/jabberd-2.4.0/NEWS Changes: * Check for C99 support in compiler * Count RIO bytes and check against max stanza size * Gracefully drop unhandled HTTP connections * wss:// (WebSocket over SSL) support in c2s * Allow BareJID S10N packets * Fallback to connecting S2S using local.ip when none of the origin.ip works * Removed explicit SQLite transactions * SQLite postconnect SQL support * SQLite DB setup script improvements * Many Coverity Scan and cppcheck detected issues fixed * Properly lowercase SASL mechanisms in c2s * Support out-of-source build https://github.com/jabberd2/jabberd2/commits/jabberd-2.4.0 -- smoku @ http://abadcafe.pl/ @ http://xiaoka.com/ signature.asc Description: This is a digitally signed message part