trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: February 2014

Re: [trinity-devel] python-tqt FTBFS - ImportError: No module named sip4_tqt

From: "David C. Rankin" <drankinatty@...>
Date: Thu, 06 Feb 2014 09:46:25 -0600
On 02/05/2014 07:42 PM, Slávek Banko wrote:
> Have you tried to sip4-tqt add patch 1912 (sip4-tqt : install as module by 
> default) from bug 1790? If patch 1912 is correct, the files should be 
> installed in a subfolder sip4_tqt. As follows:
> 
> tde-sip-R14preRC1-1-i686.pkg.tar.xz
>   usr/include/python3.3m/sip.h
>   usr/share/licenses/tde-sip/LICENSE
>   usr/bin/sip
>   usr/lib/python3.3/site-packages/sip4_tqt/__init__.py
>   usr/lib/python3.3/site-packages/sip4_tqt/sip.so
>   usr/lib/python3.3/site-packages/sip4_tqt/sipconfig.py
>   usr/lib/python3.3/site-packages/sip4_tqt/sipdistutils.py
> 
> tde-sip4-tqt-R14preRC1-1-i686.pkg.tar.xz
>   usr/include/python2.7/sip.h
>   usr/share/licenses/tde-sip4-tqt/LICENSE
>   usr/lib/python2.7/site-packages/sip4_tqt/__init__.py
>   usr/lib/python2.7/site-packages/sip4_tqt/sip.so
>   usr/lib/python2.7/site-packages/sip4_tqt/sipconfig.py
>   usr/lib/python2.7/site-packages/sip4_tqt/sipdistutils.py
> 
> Slavek

Thank you Slavek,

  I have it sorted. I see the subfolder move, but do not understand why using
sip as a module instead of an executable is preferred. However, I see the
benefit in resolving the conflict with upstream sip. I've simply been replacing
the upstream 'sip' provided file with 'tde-sip' since I was building with
upstream anyway. It was just frustrating to be cramped on time and then to run
into dependency packages changing locations in the filesystem.

-- 
David C. Rankin, J.D.,P.E.