People are again taking note of the long-fixed mismatch bug,
fixed 18 months ago, fix propagated into the sword-1-7-x branch 12
months ago. It's been a long time, for a trivial-to-fix bug that
manifests very badly. Can we please at least get a 1.7.something out the
door, if not an updated 1.8?
__
On Fri, Jun 10, 2016 at 07:10:18PM -0400, Karl Kleinpaste wrote:
>People are again taking note of the long-fixed mismatch
>bug, fixed 18 months ago, fix propagated into the sword-1-7-x branch 12
>months ago. It's been a long time, for a trivial-to-fix bug that
>manifests very badl
You would need that patched with the latest from the sword-1-7-x branch. Or
wait for a 1.7.5 release. I'm in the middle of moving across the country
right now, and don't have access to my regular machine (it's packed in my
van). The move is taking much longer than initially planned due to personal
On 06/10/2016 08:05 PM, Fred Smith wrote:
> to build our own Sword containing this fix, do we need sources/patches from
> you
svn co https://www.crosswire.org/svn/sword/trunk sword
cd sword
[ edit usrinst.sh, to turn off --disable-shared
and add --without-xapian ]
./autogen.sh
./usrinst.sh
make
[
