[sword-devel] I implore you...

[Peter von Kaehne]

Dear Greg,

Von: "Greg Hellings" <greg.hellings at gmail.com>

On Jun 9, 2013 4:28 PM, "Troy A. Griffitts" <scribe at crosswire.org> wrote:
>> Do all the bindings build ok?  It sounded like Peter still had some troubles.
>
> I can work with him to find the difference between his environment and mine and resolve that. The bindings build fine in Fedora 18 just two hours ago, so it seems to be an Ubuntu (I believe Peter is an
> Ubuntu user?) thing. I have not heard other failure reports but the Swig bindings are not regularly built by most people.

Thanks, this would be appreciated.

I would tend to agree that it might be a problem of my environment +/- my level of (in)competence. Having said this, I never remember so many difficulties when it is solely my fault for missing/messing something. I usually come to a point where I slap my forehead and all works.

FWIW, a clean checkout of sword from svn builds fine with autotools for me. The perl bindings build without error (autotools), but throw a strop when loaded in a perl script (as before). The strop appears to mean that a c++ environment (libstdc++) does not link in successfully - acc googling the error message. Looking at the final automake scripts, I would expect that libstdc++ is somewhere mentioned, but it is not. As the automake scripts appear to be build by machine in a multistage process I am not entirely sure where to look for the origin of the problem. If this is the problem.

Using the cmake build-relase.sh script I am  getting a infinite loop at around the 97% mark. Am not at home to give the exact error message. The build-debug script gives another error message. I will forward exact problems later today.

Using cmake along the wiki description - i.e. from scratch instead of using the build scripts, I am unable to build too.

I am not too bothered if the bindings do not make the release in working form for me, as long as I get them working at some stage again. I do need them for module making

Peter