Re: [PyKDE] More 3.7 compile issues
On Wed, 9 Jul 2003 16:32:07 -0400
Steve Simmons [EMAIL PROTECTED] wrote:
On Wed, Jul 09, 2003 at 03:49:46PM -0400, Rob Knapp wrote:
These issues have been resolved. I'm just noting them here in case anyone
else has the same problem. Not sure how they would since it was my
own idiocy...but I can't be the only one this unobservant, can I?
Nope, I did it too.
I would normally do 'python build.py' and 'make' as an ordinary
user, then 'make install' as root. Unfortunately sip and PyQt (and
PyKDE?) attempt to compile directly into a /usr/local (or equiv)
directory. This has been an issue for quite some time, and one of
these days I'll fix the Makefiles and send the patches to the developers.
No need to fix anything. I quote from my RPM spec files:
rm -rf %{buildroot}
mkdir -p %{buildroot}/%{_libdir}/python%{pydir}/site-packages
python build.py \
-fno-exceptions \
-b %{buildroot}/%{_bindir} \
-d %{buildroot}/%{_libdir}/python%{pydir}/site-packages \
-q /usr/lib/qt3 \
-lqt-mt EOF
yes
EOF
where you replace the %{macros} with something appropriate for you:
for instance replace %{buildroot} by /home/yourusername/tmp/usr
If you use ccache ( http://ccache.samba.org for gcc users only) recompiling
come at almost no cost:
make CXX=/usr/bin/ccache g++
You may also want to install you own Python in /home/yourusername/tmp/usr
if you want to test things out before doing a real install.
Gerard
___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] More 3.7 compile issues
On Wednesday 09 July 2003 4:29 pm, Rob Knapp wrote: I'm currently compiling on a win32 platform and the build process reported that sipBadLengthForSlice was an unknown identifier. The line number provided was line 130 in spi/qstringlist.sip. Make sure you are using SIP v3.7. For the time being I've hacked the .sip file to simply return NULL in those circumstances since my immediate needs don't require that class...however it would be nice to have the option of using it in future. However, there is a larger problem. When I reach the end of my compilation and attempt to import qt I get this: Traceback (most recent call last): File stdin line 1, in ? File d:\projects\lib\qt.py, line 924 in ? libqtc.sipRegisterClasses() SystemError: Unable to find class object for QSignalMapper That sounds like you have a 3.7 libqtc.pyd and a 3.6 qt.py. An explanation of both problems might be that you forgot to run nmake install after building both SIP and PyQt. Phil ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] More 3.7 compile issues
These issues have been resolved. I'm just noting them here in case anyone else has the same problem. Not sure how they would since it was my own idiocy...but I can't be the only one this unobservant, can I? The whole problem was that I wasn't watching the make processes for errors. Apparently the buid of sip was failing to copy libsip.dll and sip.exe over for some reason (in use by another app maybe?) And the second issue came from not realizing an error had occured during the make install. On Wed July 9 2003 12:30 pm, Phil Thompson wrote: On Wednesday 09 July 2003 4:29 pm, Rob Knapp wrote: I'm currently compiling on a win32 platform and the build process reported that sipBadLengthForSlice was an unknown identifier. The line number provided was line 130 in spi/qstringlist.sip. Make sure you are using SIP v3.7. Removing all versions of sip from my computer and re-making it did the trick. I'm not sure where how sip wasn't getting replaced. [snip] However, there is a larger problem. When I reach the end of my compilation and attempt to import qt I get this: [snip] That sounds like you have a 3.7 libqtc.pyd and a 3.6 qt.py. An explanation of both problems might be that you forgot to run nmake install after building both SIP and PyQt. This also resolved the problem. The make of qtuic.pyd failed (because I don't have the XML module installed), which prevented nmake install from copying this over. Copying the .py files over manually resolved this issue. Phil ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] More 3.7 compile issues
On Wed, Jul 09, 2003 at 02:14:33PM -0700, Jonathan Gardner wrote: On Wednesday 09 July 2003 13:32, Steve Simmons wrote: On Wed, Jul 09, 2003 at 03:49:46PM -0400, Rob Knapp wrote: I would normally do 'python build.py' and 'make' as an ordinary user, then 'make install' as root. Unfortunately sip and PyQt (and PyKDE?) attempt to compile directly into a /usr/local (or equiv) directory. . . Isn't this desired behavior? By default, most packages install into /usr/local. If you want it to go into /usr or somewhere else, you'll have to specify it in args to build.py (or the configure program in other packages). For install yes, but for build no. You should be able to compile completely as a user, and potentially even run tests as a user, without being root. Invoking large complex make processes as root is, well, not something a cautious sysadmin would do. A better approach is to always, always, always remove sip and PyQt before installing something new. After all, you are really asking for trouble if you have libsip.so.9 and libsip.so.10 in the same directory. Before installing, yes. But consider the joy of removing them and then discovering that the new version doesn't build, or has bugs in your environment. Yet another reason why one should be able to build and test before doing the actual install. ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
