Re: [sword-devel] libicui18n.so.48

2016-07-04 Thread Daniel Hughes
apt-file search shows tat libicu18n.so.55.1 was installed with the libicu55 package. So this is the version included in the default ubuntu 15.10 repositories. What I'm confused about is why me newly built libsword is trying to use an old libicu On Tue, Jul 5, 2016 at 2:36 PM, Daniel Hughes

Re: [sword-devel] libicui18n.so.48

2016-07-04 Thread Daniel Hughes
I'm using libsword from svn which I built myself today. libsword-1.7.3.so shows as being modified today. I'm running on ubuntu 15.10 I'm using the c# sword bindings that are in /bindings/csharp in svn (I was the one that contributed theses) The libicu* that I have was already on my system I

Re: [sword-devel] libicui18n.so.48

2016-07-04 Thread Greg Hellings
How did you acquire the versions of libsword.so that you have? What operating system are you running on? How did you acquire the versions of libicu* that you have? Your first email mentioned Mono. I'm unaware of any Mono/.NET support for Sword in general. It looks like the libsword.so you have

Re: [sword-devel] libicui18n.so.48

2016-07-04 Thread Daniel Hughes
It's also trying to find libicuuc.so.48 but again I only have 55 Any way to make sword build against the libs that my system actually has? On Tue, Jul 5, 2016 at 11:52 AM, Daniel Hughes wrote: > I'm getting the following error trying to load libsword.so > > Mono:

[sword-devel] libicui18n.so.48

2016-07-04 Thread Daniel Hughes
I'm getting the following error trying to load libsword.so Mono: DllImport error loading library 'libsword.so': 'libicui18n.so.48: cannot open shared object file: No such file or directory'. I don't have a libicui18n.so.48 but I do have a libicui18n.so.55.1 actually I have a libicui18n.so which

Re: [sword-devel] make error

2016-07-04 Thread Jaak Ristioja
IMHO, it were more beneficial to set these flags in the build system (-Wall should enable -Wnonnull-compare anyway) than in the source code. Setting these in a publicly visible header file without "#pragma diagnostic push/pop" makes no sense to me... J On 05.07.2016 01:33, Greg Hellings wrote: >

Re: [sword-devel] make error

2016-07-04 Thread Greg Hellings
The proper fix is to wrap that #pragma with a conditional guard so it only gets applied on GCC 6. I'm sure there are well-documented GCC preprocessor definitions that can be applied there, but Troy will need to commit the fix to SVN once he finds the appropriate guards that he wants to use.

Re: [sword-devel] make error

2016-07-04 Thread Daniel Hughes
I commend the lines and after that make completed successfully. Thanks for the help, Daniel Hughes On Tue, Jul 5, 2016 at 10:19 AM, Jaak Ristioja wrote: > Afaik, -Wnonnull-compare was added to GCC in version 6 (see > https://gcc.gnu.org/gcc-6/porting_to.html ). But it seems

Re: [sword-devel] make error

2016-07-04 Thread Jaak Ristioja
Afaik, -Wnonnull-compare was added to GCC in version 6 (see https://gcc.gnu.org/gcc-6/porting_to.html ). But it seems that the source code in include/swobject.h unconditionally evaluates these pragmas, regardless of GCC version. This bug was introduced in SVN 3426. The most simple workaround is to

Re: [sword-devel] make error

2016-07-04 Thread Greg Hellings
This is a new line that Troy just committed over the weekend. It is targeting GCC 6. What version of which compiler are you using? Perhaps that pragma needs to be guarded for GCC 6 specifically. --Greg On Jul 4, 2016 5:11 PM, "Daniel Hughes" wrote: > Hi, > > I'm trying to

[sword-devel] make error

2016-07-04 Thread Daniel Hughes
Hi, I'm trying to build sword from svn by running the following commands: make distclean ./autogen.sh ./usrinst.sh make sudo make install but am getting the following error running make: ../include/swobject.h:31:32: error: unknown option after '#pragma GCC diagnostic' kind [-Werror=pragmas]