Re: [PyKDE] eric3 and x86_64

2004-06-28 Thread Hans-Peter Jansen
On Sunday 27 June 2004 23:17, Rick L Vinyard Jr wrote:
>
> Actually, I haven't filed a bug report yet. After getting further
> segfaults in eric, I don't think I've identified the real problem,
> and switching to qt from qt-mt wasn't a real solution (but it did
> get the main eric interface running... unusable, but running).
>
> Once again, I'm not sure where to proceed from here, but I'll try
> the following:
>   (1) Back out sip ebuild changes and rebuild with qt-mt
>   (2) Rebuild PyQt
>   (3) Try Phil's ed.py again

I found something interesting in the SuSE qscintilla.spec.

They're using this patch:

--- qt/qscintilla.pro
+++ qt/qscintilla.pro   2003/01/30 23:13:06:06
@@ -25,7 +25,7 @@
  
 TEMPLATE = lib
 TARGET = qscintilla
-DESTDIR = $(QTDIR)/lib
+DESTDIR = $(QTDIR_LIB)
 CONFIG += qt warn_off release dll thread
 INCLUDEPATH = . ../include ../src
 DEFINES = QEXTSCINTILLA_MAKE_DLL QT SCI_LEXER

and build with this sequence:

rm -rf $RPM_BUILD_ROOT
export QTDIR=/usr/lib/qt3/
export QTDIR_LIB=$RPM_BUILD_ROOT/$QTDIR/%_lib
export PATH=$QTDIR/bin/:$PATH
cd qt
qmake -o Makefile qscintilla.pro
make

%_lib expands to lib64 on such systems, thus the final on disk layout
should look like:

/usr/lib/qt3/lib64/libqscintilla.so -> libqscintilla.so.4.0.0
/usr/lib/qt3/lib64/libqscintilla.so.4 -> libqscintilla.so.4.0.0
/usr/lib/qt3/lib64/libqscintilla.so.4.0 -> libqscintilla.so.4.0.0
/usr/lib/qt3/lib64/libqscintilla.so.4.0.0

Note, that it is very easy to damage the build on x86_64 systems, since
they often provide some compatibility libs in corresponding lib dirs..

Pete

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde


Re: [PyKDE] eric3 and x86_64

2004-06-27 Thread Rick L Vinyard Jr
On Sunday 27 June 2004 03:58 pm, [EMAIL PROTECTED] wrote:
> You know, that you have to re-emerge PyQt after updating sip or
> qscintilla!? 

Yup... did that each time I switched sip in the sequence sip -> qscintilla -> 
PyQt. If I was using the ebuilds I emerged them in that sequence, and if I 
was using tarballs I built them in the same sequence.

In fact, one of the earlier things I did was emerge -e PyQt.

-- 
Rick L. Vinyard, Jr.
http://miskatonic.cs.nmsu.edu

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde


Re: [PyKDE] eric3 and x86_64

2004-06-27 Thread current
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sunday 27 June 2004 23:39, Rick L Vinyard Jr wrote:
> I haven't changed _anything_ on the machine except sip, qscintilla and PyQt
> since the last time these were emerged and resulted in segfaults. I'm not
> sure why manually installing these from the tarballs followed by emerging
> the packages worked, when simply emerging the same packages failed or
> simply manually installing failed, but it works...
You know, that you have to re-emerge PyQt after updating sip or qscintilla!? 
Please take in account that Portage doesn't support reverse dependencies yet. 
I added post install comments in the sip ebuilds, which I expect to go stable 
sooner or later, a few days ago.


Carsten Lohrke
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA30LuVwbzmvGLSW8RAiVjAJ0REicNavkNHTQnIHPChzp+E2TCqACdEFSk
Tg9QK3KLIdR/iWyC7D0yhaI=
=YTBF
-END PGP SIGNATURE-

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde


Re: [PyKDE] eric3 and x86_64

2004-06-27 Thread Rick L Vinyard Jr
On Sunday 27 June 2004 03:17 pm, Rick L Vinyard Jr wrote:
> Once again, I'm not sure where to proceed from here, but I'll try the
> following:
>   (1) Back out sip ebuild changes and rebuild with qt-mt
>   (2) Rebuild PyQt
>   (3) Try Phil's ed.py again

Curiouser and couriouser. I really haven't a clue now, but it all works. I 
emerged sip (4.0), qscintilla (1.6.0) and PyQt (3.12) for the 
I-don't-know-what time (maybe sixth time) and eric is now working without 
segfaults.

I haven't changed _anything_ on the machine except sip, qscintilla and PyQt 
since the last time these were emerged and resulted in segfaults. I'm not 
sure why manually installing these from the tarballs followed by emerging the 
packages worked, when simply emerging the same packages failed or simply 
manually installing failed, but it works...

-- 
Rick L. Vinyard, Jr.
http://miskatonic.cs.nmsu.edu

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde


Re: [PyKDE] eric3 and x86_64

2004-06-27 Thread Rick L Vinyard Jr
On Sunday 27 June 2004 02:12 pm, Jim Bublitz wrote:
> On Sunday 27 June 2004 12:14, Rick L Vinyard Jr wrote:
> > On Sunday 27 June 2004 11:30 am, Hans-Peter Jansen wrote:
> >
> > But, rebuilding sip against the qt libs rather than qt-mt seems to
> > resolve everything... and now the eric snapshot is working (and I would
> > guess the released versions of eric as well). Why? I haven't a clue, but
> > it does.
> >
> > I'm going to modify the sip ebuild, and if it works out, I'll post a
> > patch and a bug-fix for amd64 at bugs.gentoo.org.
>
> Your patch will make it impossible for amd64 users to build or run PyKDE,
> which requires qt-mt.

Actually, I haven't filed a bug report yet. After getting further segfaults in 
eric, I don't think I've identified the real problem, and switching to qt 
from qt-mt wasn't a real solution (but it did get the main eric interface 
running... unusable, but running).

Once again, I'm not sure where to proceed from here, but I'll try the 
following:
(1) Back out sip ebuild changes and rebuild with qt-mt
(2) Rebuild PyQt
(3) Try Phil's ed.py again

-- 
Rick L. Vinyard, Jr.
http://miskatonic.cs.nmsu.edu

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde


Re: [PyKDE] eric3 and x86_64

2004-06-27 Thread Jim Bublitz
On Sunday 27 June 2004 12:14, Rick L Vinyard Jr wrote:
> On Sunday 27 June 2004 11:30 am, Hans-Peter Jansen wrote:

> But, rebuilding sip against the qt libs rather than qt-mt seems to resolve
> everything... and now the eric snapshot is working (and I would guess the
> released versions of eric as well). Why? I haven't a clue, but it does.

> I'm going to modify the sip ebuild, and if it works out, I'll post a patch
> and a bug-fix for amd64 at bugs.gentoo.org.

Your patch will make it impossible for amd64 users to build or run PyKDE, 
which requires qt-mt.

Jim

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde


Re: [PyKDE] eric3 and x86_64

2004-06-27 Thread Rick L Vinyard Jr
On Sunday 27 June 2004 01:45 pm, Rick L Vinyard Jr wrote:
>   But, during a session, if I open a qscintilla widget it works fine, but on
> exit I get a segfault (perhaps widget destruction?):

> backtraces, etc., but it doesn't (yet) seem to interfere with the operation
> of eric.

I think I spoke too soon. It did fine when I tested it by creating new 
untitled widgets. But, any attempt to open a python file (I suppose that uses 
a subclassed widget???) or to close an open widget causes a segfault.

-- 
Rick L. Vinyard, Jr.
http://miskatonic.cs.nmsu.edu

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde


Re: [PyKDE] eric3 and x86_64

2004-06-27 Thread Rick L Vinyard Jr
On Sunday 27 June 2004 11:44 am, Phil Thompson wrote:
> Is the attached any use?

Oddly enough, I get:
bash-2.05b$ python ed.py
Segmentation fault
bash-2.05b$ 

Also, here's something else to note:
If I execute eric (I'm back to the gentoo 3.4.2 ebuild now), and close 
without opening a qscintilla widget:
bash-2.05b$ eric3
bash-2.05b$
But, during a session, if I open a qscintilla widget it works fine, but on 
exit I get a segfault (perhaps widget destruction?):
bash-2.05b$ eric3
Segmentation fault
bash-2.05b$

I modified the sip ebuild and all seems well enough now. If you're interested 
in hunting down the segfaults I'd be happy to provide you with backtraces, 
etc., but it doesn't (yet) seem to interfere with the operation of eric.

-- 
Rick L. Vinyard, Jr.
http://miskatonic.cs.nmsu.edu

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde


Re: [PyKDE] eric3 and x86_64

2004-06-27 Thread Rick L Vinyard Jr
On Sunday 27 June 2004 11:30 am, Hans-Peter Jansen wrote:
> > Do you know where I could find a little script to test the
> > qscintilla library?
>
> No, sorry, but what does something like:
>
> python -c "from qtext import QextScintilla"

Unfortunately, no problems loading the library...

bash-2.05b$ python -c "from qtext import QextScintilla"
bash-2.05b$ 

But, that got me thinking, so I started digging into the qscintilla ebuild. I 
installed qscintilla from a tarball using the same commands as the ebuild 
and... still errors. But, the commands were a very basic installtion 
sequence, so no surprise there.

So, I dug a little further back, and found this in the sip ebuild:
python configure.py -l qt-mt

This shouldn't be a problem, since my qt libraries are built with x86_64 
threading support (as is glibc). In fact, I've used qt threads rather 
extensively on this machine for about 5 months with no problems.

But, rebuilding sip against the qt libs rather than qt-mt seems to resolve 
everything... and now the eric snapshot is working (and I would guess the 
released versions of eric as well). Why? I haven't a clue, but it does.

I'm going to modify the sip ebuild, and if it works out, I'll post a patch and 
a bug-fix for amd64 at bugs.gentoo.org.

Thanks for all your help Hans!

-- 
Rick L. Vinyard, Jr.
http://miskatonic.cs.nmsu.edu

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde


Re: [PyKDE] eric3 and x86_64

2004-06-27 Thread Phil Thompson
On Sunday 27 June 2004 6:30 pm, Hans-Peter Jansen wrote:
> On Sunday 27 June 2004 18:55, Rick L Vinyard Jr wrote:
> > On Sunday 27 June 2004 03:31 am, Hans-Peter Jansen wrote:
> > > If you can extract the configure.py calls of sip and PyQt, send
> > > them over. I will have a look over them, and please check some
> > > qscintillaless scripts to rule this one out...
> >
> > I've checked out several (about 10) of the scripts in the PyQt 3.12
> > distro at random. All of the examples tried worked without
> > problems, so I'm assuming that this rules out sip and PyQt as the
> > culprits?
>
> Yep.
>
> > I googled for qscintilla to try and find a tiny canonical example,
> > perhaps something with just a qscintilla widget only, but I
> > couldn't find one online or in the 1.60 tarball.
>
> Yes, it's badly missing in PyQt examples.. 
>
> > Do you know where I could find a little script to test the
> > qscintilla library?

Is the attached any use?

Phil


ed.py
Description: application/python


Re: [PyKDE] eric3 and x86_64

2004-06-27 Thread Hans-Peter Jansen
On Sunday 27 June 2004 18:55, Rick L Vinyard Jr wrote:
> On Sunday 27 June 2004 03:31 am, Hans-Peter Jansen wrote:
> > If you can extract the configure.py calls of sip and PyQt, send
> > them over. I will have a look over them, and please check some
> > qscintillaless scripts to rule this one out...
>
> I've checked out several (about 10) of the scripts in the PyQt 3.12
> distro at random. All of the examples tried worked without
> problems, so I'm assuming that this rules out sip and PyQt as the
> culprits?

Yep.

> I googled for qscintilla to try and find a tiny canonical example,
> perhaps something with just a qscintilla widget only, but I
> couldn't find one online or in the 1.60 tarball.

Yes, it's badly missing in PyQt examples.. 

> Do you know where I could find a little script to test the
> qscintilla library?

No, sorry, but what does something like:

python -c "from qtext import QextScintilla"

Pete

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde


Re: [PyKDE] eric3 and x86_64

2004-06-27 Thread Rick L Vinyard Jr
On Sunday 27 June 2004 03:31 am, Hans-Peter Jansen wrote:
> If you can extract the configure.py calls of sip and PyQt, send them
> over. I will have a look over them, and please check some
> qscintillaless scripts to rule this one out...

I've checked out several (about 10) of the scripts in the PyQt 3.12 distro at 
random. All of the examples tried worked without problems, so I'm assuming 
that this rules out sip and PyQt as the culprits?

I googled for qscintilla to try and find a tiny canonical example, perhaps 
something with just a qscintilla widget only, but I couldn't find one online 
or in the 1.60 tarball.

Do you know where I could find a little script to test the qscintilla library?

-- 
Rick L. Vinyard, Jr.
http://miskatonic.cs.nmsu.edu

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde


Re: [PyKDE] eric3 and x86_64

2004-06-27 Thread Hans-Peter Jansen
On Sunday 27 June 2004 01:38, Rick L Vinyard Jr wrote:
> On Saturday 26 June 2004 05:00 pm, Hans-Peter Jansen wrote:
>
> > Did
> > you supplied proper build arguments to the whole set, aka. lib64
> > vs. lib issues, and the like?
>
> I'm just building from the gentoo packages, but that could very
> well be part of the issue with the gentoo ebuilds.

If you can extract the configure.py calls of sip and PyQt, send them 
over. I will have a look over them, and please check some 
qscintillaless scripts to rule this one out...

Pete

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde


Re: [PyKDE] eric3 and x86_64

2004-06-26 Thread Rick L Vinyard Jr
On Saturday 26 June 2004 05:00 pm, Hans-Peter Jansen wrote:
> Eric is definitely not the offender here, as I ran some of the above
> combinations on my SuSE 9.1-x86_64 system properly.

That does help a bit. At least I know it's not a 64 bit issue... but just a 
gentoo amd64 issue.

> Did
> you supplied proper build arguments to the whole set, aka. lib64 vs.
> lib issues, and the like?

I'm just building from the gentoo packages, but that could very well be part 
of the issue with the gentoo ebuilds.

> Providing a backtrace would be helpful, probably from a debug build,
> as well as trying some example3 scripts..

I think the next step will be to test the PyQT, sip and qscintilla libraries 
as installed. I doubt it goes as deep as qt, since I've been running KDE for 
awhile. I wonder if anyone else is having trouble with using one or more of 
these libs on gentoo amd64?

-- 
Rick L. Vinyard, Jr.
http://miskatonic.cs.nmsu.edu

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde


Re: [PyKDE] eric3 and x86_64

2004-06-26 Thread Hans-Peter Jansen
On Saturday 26 June 2004 21:29, Rick L Vinyard Jr wrote:
> Hello.
>
> I've been trying to get some (any) version of eric3 installed on a
> gentoo amd64 box. I've completely rebuilt all dependant libraries,
> just in case that was an issue. I've also tried different
> combinations of the PyQt (3.11, 3.12), sip (4.0.rc2, 4.0rc4, 4.0)
> and qscintilla (1.54, 1.60) libraries to no avail.
>
> Despite changing libraries, behavior seems consistent. All 3.4+
> (3.4.1, 3.4.2, snapshot-20040622) versions seem to die after the
> splash screen with a segfault. All versions prior to 3.4 (3.3.x,
> 3.2.x) make it past the splash screen, the main window is displayed
> briefly (about 1 second) and terminates with a bus error.
>
> Any suggestions?

Eric is definitely not the offender here, as I ran some of the above 
combinations on my SuSE 9.1-x86_64 system properly. The last x86_64 
issue, I know was fixed by Phil around sip 4.0rc2/3.12pre time. Did 
you supplied proper build arguments to the whole set, aka. lib64 vs. 
lib issues, and the like?

Providing a backtrace would be helpful, probably from a debug build, 
as well as trying some example3 scripts..

Pete

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde


[PyKDE] eric3 and x86_64

2004-06-26 Thread Rick L Vinyard Jr
Hello.

I've been trying to get some (any) version of eric3 installed on a gentoo 
amd64 box. I've completely rebuilt all dependant libraries, just in case that 
was an issue. I've also tried different combinations of the PyQt (3.11, 
3.12), sip (4.0.rc2, 4.0rc4, 4.0) and qscintilla (1.54, 1.60) libraries to no 
avail.

Despite changing libraries, behavior seems consistent. All 3.4+ (3.4.1, 3.4.2, 
snapshot-20040622) versions seem to die after the splash screen with a 
segfault. All versions prior to 3.4 (3.3.x, 3.2.x) make it past the splash 
screen, the main window is displayed briefly (about 1 second) and terminates 
with a bus error.

Any suggestions?

___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde