Marc Toussaint wrote:
I found your discussion on the broken QT port to cygwin.
http://cygwin.com/acronyms/#PPIOSPE
I'm redirecting this to the cygwin-xfree list. Please make sure that
your mail client respects the Reply-To: address.
I have the same problem with uic: it is producing broken
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
René Berber wrote:
Running Scribus with the debug enabled cygqt-mt-3.dll the program
works fine with no mutex failure message and using the latest Cygwin
snapshot. As mentioned in my reply to Brian, under gdb there are many
SIGSEGV signals
Yaakov S (Cygwin Ports) wrote:
Running Scribus with the debug enabled cygqt-mt-3.dll the program
works fine with no mutex failure message and using the latest Cygwin
snapshot. As mentioned in my reply to Brian, under gdb there are many
SIGSEGV signals received but continuing results in the same
René Berber wrote:
The library is as close as it gets to a regular library, I separated the debug
info, it's just not optimized.
It would be interesting to test a rebuilt regular library, have you done that?
Answering my own question: no, it doesn't work.
Just tested it, rebuilt Qt with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
René Berber wrote:
Or the change exposed a bug in Qt.
Either way, it was working in 1.5.18 (didn't I already say I'd be
unhappy if my qt3 was broken with 1.5.19?).
The library is as close as it gets to a regular library, I separated the debug
Yaakov S (Cygwin Ports) wrote:
[snip]
Actually, now that you mention it...
I was in the middle of building kdelibs-3.5.1 when gcc choked on
uic-generated code (this happened with both 3.3.4 and 3.3.5). So I went
back to rebuild 3.3.4, and now it won't finish either.
g++ -c -pipe
