Message: previous - next
Month: April 2011

Re: [trinity-devel] [arch] Your Qt3 is not patched for compatibility with tqtinterface

From: Calvin Morrison <mutantturkey@...>
Date: Sun, 10 Apr 2011 22:50:41 -0400
On 5 April 2011 16:46, Baho Utot <baho-utot@...> wrote:
> On 04/05/2011 05:55 AM, Serghei Amelian wrote:
>> On Tuesday 05 April 2011 12:44:42 Baho Utot wrote:
>>> On 04/04/2011 08:18 PM, Calvin Morrison wrote:
>>>> Hmmmm,
>>>> All of a sudden whenever building anything for trinity, I keep running
>>>> into this problem "   Your Qt3 is not patched for compatibility with
>>>> tqtinterface " but I don't really know why. I have installed the
>>>> patched versions and it was all working until last week. Am I missing
>>>> something? Also, Baho and David, have you run into similar problems?
>>> Yes I am currently working with problems with tqtinterface,
>>> I have problems with it finding moc and uic.
>>> moc and uic are where they are supposed to be but the configure script
>>> won't find them.
>>> I am currently working on the build environment to see if all the
>>> variables are set as they should be.  I think there is something wrong
>>> with the build environment.
>>> tqtinterface tells me moc and uic are at /opt/qt/bin which is wrong
>>> qt include directory is at /usr/include/qt3 which is wrong
>>> When I examine the file list from my qt3 build it shows moc uic in
>>> /usr/bin and the qt include directory as /usr/include/qt
>>> even if I pass
>>>      export _prefix="/usr"
>>>      msg "Starting cmake..."
>>>      cmake ${_source}/${_module}/ \
>>>          -DCMAKE_INSTALL_PREFIX=${_prefix} \
>>>          -DQT_VERSION=3
>>>          -DQT_PREFIX_DIR=${_prefix} \
>>>          -DQT_INCLUDE_DIR=${_prefix}/include/qt \
>>>          -DQT_BINARY_DIR=${_prefix}/bin
>>> --   QT_INCLUDE_DIR: /usr/include/qt3<-- this is wrong as I passed
>>> /usr/include/qt
>> No, you don't. After  "-DQT_VERSION=3" is missing a backslash character.
> And I even was looking for just that.
> Wasn't the first time I missed the blackslash...Doubt it will be the last.


I am still running into the same original problem, it just breaks with
this same error.

Looking for some guidance

Calvin Morrison