cuneiform team mailing list archive

[MaxiPunkt <maxantispam@xxxxxxxxxx>]

Hi there,

I had to put the commands on console instead of my script.
Otherwise the strace-output whouldn't have been very meaningful.

If these strace-outputs don't help you and you need an output with GDB, you should give me a hint how to manage this.
I didn't really work with GDB before (apart from the KDE-feature to have a gdb-backtrace automatically, when a program crashed.

** Attachment added: "strace of working/non_working cuneiform and commands used"
   http://launchpadlibrarian.net/39237957/cune_test.tar.gz

-- 
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...