6 Jul
2014
6 Jul
'14
6:19 p.m.
On 06/07/2014 17:11, Michael Howard wrote:
On 05/07/2014 13:47, Michele Calgaro wrote:
It seems that it fails because 'python2.6-dbg ../configure.py' cannot
find module sipconfig_d;
ImportError: No module named sipconfig_d
and indeed, it does not exist in the python2.6 tree, but does in the
python2.7 tree.
--
Hi Mike,
sorry for the late reply, I am going through a pretty busy period
recently.
I must apologise, the script that I use was causing the build to use
concurrent jobs masking the error. New build output attached.
The build fails with/at;
mkdir -p dbg-build-2.6
cd dbg-build-2.6 && echo yes \
| python2.6-dbg ../configure.py \
-c -n /usr/include/tqscintilla \
-o /usr/lib -u -j 10 \
-d /usr/lib/python2.6/dist-packages/python_tqt \
-l /usr/include/python2.6_d \
-v /usr/share/sip/tqt \
-m /usr/lib/python2.6/config_d \
CXXFLAGS_RELEASE="" CXXFLAGS="-O0 -g
-I/usr/include/tqt" STRIP=""
Traceback (most recent call last):
File "../configure.py", line 31, in <module>
from sip4_tqt import sipconfig
File "/usr/lib/python2.6/dist-packages/sip4_tqt/sipconfig.py", line
10, in <module>
raise ImportError, 'No module named sipconfig; package
python-sip-tqt-dbg not installed'
ImportError: No module named sipconfig; package python-sip-tqt-dbg not
installed
[16791 refs]
make: *** [dbg-build-2.6/configure-stamp] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
'python-sip-tqt-dbg ' is installed, as
part of the build sequence,
i.e. after each suite/prog is built (tqt3, tqtinterface etc) it is
automatically installed and the next build sequence starts. Perhaps
I'll try not installing and let the build sequence find and install
the dependencies.
If I understand correctly from the above, you build a
module/prog,
then install it in your system, then move to the next one and so on.
Correct?
If so, here comes the next question: which command/tool do you use
for building a module? debuild / pbuilder? dpkg-buildpackage? manual
invocation of fakeroot debian/rules binary? Others?
Perhaps python-sip-tqt-dbg is not installed in the right environment.
For example you could have python-sip-tqt-dbg installed in your
system, but debuild may not be able to find it.... or there may be
other combinations.
Based on "how you build", let's see what the next step is, even
though it seems strange that the problem came up all of a sudden in
wheezy (jessie is a different beast, and there is no guarantee that
what works now will still work the next hour.... been there many
times :) )
Can you also upload a build log? It may help as well.
Cheers
Michele