← Back to team overview

cuneiform team mailing list archive

[Bug 520862] Re: PUMA_Init failed. (cuneifomr 0.9.0)

 

Hi there,

I can successfully run cuneiform 0.9.0 out of my local RPM-build-directory!
I even did NOT change one of these "aggressive" flags (exept the "-Werror=format-security"-thing I've disabeled for now).

That means the binary is exactly the same as put into the RPM afterwards.
To run cuneiform localy I've used the following script:

#!/bin/bash
#
PATH_TO_TESTFILE="/media/win_fat/Tools_LINUX/CuneIform_test"

export CF_DATADIR="/home/maxipunkt/rpm/BUILD/cuneiform-
linux-0.9.0/datafiles"

./cuneiform -l ger -f html -o test.html $PATH_TO_TESTFILE/test.tiff


Does that simply mean cuneiform does't find it's datafiles for what
reason ever?

-- 
PUMA_Init failed. (cuneifomr 0.9.0)
https://bugs.launchpad.net/bugs/520862
You received this bug notification because you are a member of Cuneiform
Linux, which is the registrant for Cuneiform for Linux.

Status in Linux port of Cuneiform: New

Bug description:
As it seems that you don't read through old bugreports (#362224), I'll open a new one:

$ cuneiform -l ger -f html -o test.html test.tiff
Cuneiform for Linux 0.9.0
PUMA_Init failed.

I already had this problem with cuneiform 0.8.0 on my system (MandrivaLinux 2010.0), and it's still there for cuneiform 0.9.0.


I built an RPM of cuneiform out of it's source-code myself. Doing this means using Mandriva's %cmake RPM-macro.
All cmake-options used by this macro can be seen here:
http://launchpadlibrarian.net/35930811/cmake.txt (bug #/362224, comment #16)

Strace-output for cuneiform 0.8.0 can be seen here:
http://launchpadlibrarian.net/35930821/strace_cuneinform.txt  (bug #/362224, comment #17)

For cuneiform 0.9.0 I'll attach a new strace...





References