> > What does exactly mean "Speicherzugriffsfehler"? I think may mean
>
> Sementation fault
So it seems the qmake have segfaulted. I do not see any obvious reason
why, so it may be hard to track.
I looked at the strace output and unfortunately, it seems to capture only
the cleanup of temporary files after the segfault.
What qmake version have you installed?
Try sending me output of "/usr/lib/qt3/bin/qmake --version"
I may try installing same version of opensuse (10.2-i686) in a virtual
machine (I managed to find a disc with it :) and trying to reproduce the
problem, though I am not familiar with checkinstall. What commands exactly
have you used?
Also, you may try to put these three lines:
#!/bin/sh
export REAL_QMAKE=/usr/lib/qt3/bin/qmake
strace $REAL_QMAKE 2>/tmp/qmake-bugs
into a file called "qmake_debug", chmod +x it and put it somewhere
Then set environment variable QMAKE to point to it ("export
QMAKE=/path/where/the/script/is/qmake_debug") and re-run configure (or
entire build process)
Then send me file /tmp/qmake-bugs
I hope something of this will help to trace the bug ...
Martin Petricek
> I did it. Here is the output:
GPG/PGP Public key: http://www.petricek.net/petricm.pgp
Fingerprint 6AA8 FFCE C061 1CB2 55F0 A1F3 3AA9 EB4F BD50 C1B8
/------------------------------------------------------------\
| WWW: http://www.petricek.net/ |
\------------------------------------------------------------/
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Pdfedit-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pdfedit-support
