Re: jabberd-2.4.0 release

[Tomasz Sterna]

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

[li...@lazygranch.com]

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"]))