Qt-interest Archive, December 2006
qtdemo problem
Message 1 in thread
I have successfully built and installed Qt-4.2.2 on 64-bit OpenBSD 3.9.
I have added /usr/local/Trolltech/bin to my path.
Initially the command 'which moc' reported 'moc not found'.
I found that the files in /usr/local/Trolltech/bin all had -rw------- permissions.
I fixed that by executing as root 'chmod -R 755 /usr/local/Trolltech/*'.
Now when I try to run qtdemo, I get error messages saying that various
libraries cannot be loaded.
How do I fix this problem?
Thanks,
Dave Feustel
--
[ signature omitted ]
Message 2 in thread
did you move qt folder after the Qt libs generation?
may be http://doc.trolltech.com/4.2/qt-conf.html can help you...
Dave@xxxxxxxxxxxxx a écrit :
>I have successfully built and installed Qt-4.2.2 on 64-bit OpenBSD 3.9.
>I have added /usr/local/Trolltech/bin to my path.
>Initially the command 'which moc' reported 'moc not found'.
>I found that the files in /usr/local/Trolltech/bin all had -rw------- permissions.
>I fixed that by executing as root 'chmod -R 755 /usr/local/Trolltech/*'.
>Now when I try to run qtdemo, I get error messages saying that various
>libraries cannot be loaded.
>
>How do I fix this problem?
>
>Thanks,
>Dave Feustel
>
>--
>To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx with "unsubscribe" in the subject or the body.
>List archive and information: http://lists.trolltech.com/qt-interest/
>
>
>
>
--
[ signature omitted ]
Message 3 in thread
Hi,
> I have successfully built and installed Qt-4.2.2 on 64-bit OpenBSD 3.9.
What were the exact commands used to build and install Qt?
--
[ signature omitted ]
Message 4 in thread
> Hi,
>
> > I have successfully built and installed Qt-4.2.2 on 64-bit OpenBSD 3.9.
>
> What were the exact commands used to build and install Qt?
./configure
gmake -k
<fixed openbsd mkspec file as per your suggestion>
./configure
gmake -k
gmake install (as root)
--
[ signature omitted ]
Message 5 in thread
> You probably need to add /usr/local/Trolltech/lib to you
> LD_LIBRARY_PATH so the dynamic linker can find the shared library files.
That did the trick. Thanks!
Dave
--
[ signature omitted ]
