Re: jabberd-2.3.6 release
W dniu 29.02.2016, pon o godzinie 17∶35 +0300, użytkownik
ungifte...@gmail.com napisał:
> Yes, It's Gentoo specific. Sorry.
>
> epatch "${FILESDIR}"/${P}-optimization.patch
> eautoreconf
Doh... I should have removed that check long time ago...
Done: http://github.com/jabberd2/jabberd2/commit/7746da1
--
/o__
(_<^' Any given program will expand to fill available memory.
signature.asc
Description: This is a digitally signed message part
Re: jabberd-2.3.6 release
On Mon, Feb 29, 2016 at 01:46:12PM +0100, Tomasz Sterna wrote: > W dniu 29.02.2016, pon o godzinie 13∶14 +0300, użytkownik > ungifte...@gmail.com napisał: > > > Next jabberd2 release is available. > > > > Have to emerge autoconf-archive for new coloring feature > > Do you build from bare GitHub source? > > This macro should get included to the release archive which do not > require any autotools packages installed for building. I got the same error building the package on Fedora. I had to run autoreconf on 2.3.5 as I was getting libtool errors like "Version mismatch error.". Which were removed by running autoreconf. Updating to 2.3.6 gave me then above error during configure, which was resolved by removing the autoreconf I introduced earlier. So, no problems on my side anymore. Just wanted to mention that I saw the same error as the original poster. Adrian
Re: jabberd-2.3.6 release
On 29.02.2016 15:46, Tomasz Sterna wrote:
> W dniu 29.02.2016, pon o godzinie 13∶14 +0300, użytkownik
> ungifte...@gmail.com napisał:
>>> Next jabberd2 release is available.
>>
>> Have to emerge autoconf-archive for new coloring feature
>
> Do you build from bare GitHub source?
>
> This macro should get included to the release archive which do not
> require any autotools packages installed for building.
Yes, It's Gentoo specific. Sorry.
epatch "${FILESDIR}"/${P}-optimization.patch
eautoreconf
Re: jabberd-2.3.6 release
W dniu 29.02.2016, pon o godzinie 13∶14 +0300, użytkownik ungifte...@gmail.com napisał: > > Next jabberd2 release is available. > > Have to emerge autoconf-archive for new coloring feature Do you build from bare GitHub source? This macro should get included to the release archive which do not require any autotools packages installed for building. -- /o__ Q: How many Martians does it take to screw in a light bulb? (_<^' A: One and a half.
Re: jabberd-2.3.6 release
On 28.02.2016 02:04, Tomasz Sterna wrote:
> Next jabberd2 release is available.
Have to emerge autoconf-archive for new coloring feature:
./configure: line 12456: syntax error near unexpected token
`-fdiagnostics-color,'
./configure: line 12456: `AX_CHECK_COMPILE_FLAG(-fdiagnostics-color,
CFLAGS="${CFLAGS} -fdiagnostics-color",'
found 3 colored gcc warnings :) Compiled fine.
> Get 2.3.6 release at GitHub:
> https://github.com/jabberd2/jabberd2/releases
>
>
> This is a major bugfix release.
>
> The main change is that WebSocket connections are now fully working and
> stable.
> Also if you are using MUC, you want to upgrade as 2.3.5 direct presence
> bug prevented users from entering MUC rooms.
>
> Make sure to read the NEWS before upgrade:
> https://github.com/jabberd2/jabberd2/blob/jabberd-2.3.6/NEWS
>
>
> Changes:
> * Support WebSocket fragmented packets
> * Fixed delivering directed presence (to self)
> * Reset in-sess 'from' to FullJID on non-Presence packets
>
> https://github.com/jabberd2/jabberd2/commits/jabberd-2.3.6
>
>
>
