Bug#368883: qt4-x11: FTBFS on alpha

2006-06-04 Thread Steve Langasek
reopen 368883
thanks

 * debian/patches/17_alpha_ice.dpatch: new patch from Steve Langasek to
  fix FTBFS on alpha (Closes: #368883)
  (urgency set to high for that fix).

sigh Except that, by adding in the new upstream release at the same time,
qt4-x11 is now hitting the same error in a different part of the code...

[...]
g++ -c -pipe -I/usr/include/mysql -I/usr/include/freetype2 
-I/usr/include/postgresql -g -fvisibility=hidden -fvisibility-inlines-hidden 
-Wall -W -D_REENTRANT -fPIC  -DQT_SHARED -DQT_BUILD_OPENGL_LIB 
-DQT_NO_CAST_TO_ASCII -DQT3_SUPPORT -DQT_MOC_COMPAT -DQT_GUI_LIB -DQT_CORE_LIB 
-D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -I../../mkspecs/linux-g++ -I. 
-I../../include/QtCore -I../../include/QtGui -I../../include 
-I../../include/QtOpenGL -I/usr/include/freetype2 -I/usr/X11R6/include 
-I/usr/X11R6/include -I.moc/debug-shared -I. -o .obj/debug-shared/qgl.o qgl.cpp
../../include/QtCore/../../src/corelib/thread/qthreadstorage.h: In constructor 
'QThreadStorageT::QThreadStorage() [with T = QGLThreadContext*]':
../../include/QtCore/../../src/corelib/thread/qthreadstorage.h:116: internal 
compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See URL:http://gcc.gnu.org/bugs.html for instructions.
For Debian GNU/Linux specific bug reporting instructions,
see URL:file:///usr/share/doc/gcc-4.0/README.Bugs.
make[4]: *** [.obj/debug-shared/qgl.o] Error 1
[...]

So, reopening.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


signature.asc
Description: Digital signature


Bug#368883: qt4-x11: FTBFS on alpha

2006-06-03 Thread Samuel Thibault
Hi,

Could this be fixed any time soon?  qt4-x11 is currently blocking no
less than 83 packages.

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Processed: Re: Bug#368883: qt4-x11: FTBFS on alpha

2006-06-03 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 tag 368883 + pending
Bug#368883: qt4-x11: FTBFS on alpha
Tags were: patch
Tags added: pending

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#368883: qt4-x11: FTBFS on alpha

2006-06-03 Thread Pierre Habouzit
tag 368883 + pending
thanks

Le Sam 3 Juin 2006 10:57, Samuel Thibault a écrit :
 Hi,

 Could this be fixed any time soon?  qt4-x11 is currently blocking no
 less than 83 packages.

 Samuel

that one is quite annoying.

Brian: will you have time to fix that soon (like in less than a couple 
of days ?) else I'll do an upload just to fix the alpha FTBFS now that 
there is a patch.

If I've no news from you, I suppose I'll do an upload on sunday.
-- 
·O·  Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org


pgphIPyRA2lFc.pgp
Description: PGP signature


Bug#368883: qt4-x11: FTBFS on alpha

2006-06-03 Thread Brian Nelson
Pierre Habouzit [EMAIL PROTECTED] writes:

 tag 368883 + pending
 thanks

 Le Sam 3 Juin 2006 10:57, Samuel Thibault a écrit :
 Hi,

 Could this be fixed any time soon?  qt4-x11 is currently blocking no
 less than 83 packages.

 Samuel

 that one is quite annoying.

 Brian: will you have time to fix that soon (like in less than a couple 
 of days ?) else I'll do an upload just to fix the alpha FTBFS now that 
 there is a patch.

 If I've no news from you, I suppose I'll do an upload on sunday.

I should be able to do it today (Saturday). If not, go ahead and upload
on Sunday.

-- 
Captain Logic is not steering this tugboat.



Bug#368883: qt4-x11: FTBFS on alpha

2006-05-31 Thread Steve Langasek
tags 368883 patch
thanks

So, having diagnosed that this is an interaction between
-fvisibility-inlines-hidden and referencing inlined methods (bug #369642),
the obvious workaround is to keep the problematic methods from getting
inlined.

The attached patch should do this; unfortunately, I haven't tested it
completely because qt4-x11 is also missing a build-conflict with
unixodbc-dev, and I don't have the patience to try to build it a second time
on alpha.  Please consider applying the patch, I don't believe it has
negative side-effects for other archs.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/
diff -u qt4-x11-4.1.2/debian/changelog qt4-x11-4.1.2/debian/changelog
--- qt4-x11-4.1.2/debian/changelog
+++ qt4-x11-4.1.2/debian/changelog
@@ -1,3 +1,11 @@
+qt4-x11 (4.1.2-2.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Workaround for -fvisibility-inlines-hidden on alpha: break out the
+static methods so they're not inlined.  Closes: #368883.
+
+ -- Steve Langasek [EMAIL PROTECTED]  Tue, 30 May 2006 19:56:44 -0700
+
 qt4-x11 (4.1.2-2) unstable; urgency=low
 
   * debian/libqt4-debug-dev.install, debian/libqt4-dev.install: added
only in patch2:
unchanged:
--- qt4-x11-4.1.2.orig/src/corelib/global/qlibraryinfo.cpp
+++ qt4-x11-4.1.2/src/corelib/global/qlibraryinfo.cpp
@@ -47,14 +47,7 @@
 {
 public:
 static QSettings *findConfiguration();
-static void cleanup()
-{
-QLibrarySettings *ls = qt_library_settings();
-if (ls) {
-delete static_castQSettings *(ls-settings);
-ls-settings = 0;
-}
-}
+static void cleanup();
 static QSettings *configuration()
 {
 QLibrarySettings *ls = qt_library_settings();
@@ -64,6 +57,15 @@
 Q_GLOBAL_STATIC(QLibrarySettings, qt_library_settings)
 };
 
+void QLibraryInfoPrivate::cleanup()
+{
+QLibrarySettings *ls = qt_library_settings();
+if (ls) {
+delete static_castQSettings *(ls-settings);
+ls-settings = 0;
+}
+}
+
 QLibrarySettings::QLibrarySettings()
 {
 settings = QLibraryInfoPrivate::findConfiguration();
only in patch2:
unchanged:
--- qt4-x11-4.1.2.orig/src/corelib/tools/qhash.h
+++ qt4-x11-4.1.2/src/corelib/tools/qhash.h
@@ -396,7 +396,7 @@
 }
 
 template class Key, class T
-Q_INLINE_TEMPLATE void QHashKey, T::duplicateNode(QHashData::Node *node, 
void *newNode)
+void QHashKey, T::duplicateNode(QHashData::Node *node, void *newNode)
 {
 Node *concreteNode = concrete(node);
 if (QTypeInfoT::isDummy) {


signature.asc
Description: Digital signature


Bug#368883: qt4-x11: FTBFS on alpha

2006-05-30 Thread Steve Langasek
clone 368883 -1
reassign -1 g++-4.0
severity -1 important
thanks

This ICE also happens with g++-4.1 and gcc-snapshot.

Working on a minimal test case.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#368883: qt4-x11: FTBFS on alpha

2006-05-25 Thread Filipus Klutiero
Package: qt4-x11
Version: 4.1.2-2
Severity: serious
Justification: no longer builds from source

gcc ICEd when attempting to build qt4-x11 on alpha on 2006-05-14. I
don't know what's the issue and what could fix. However, 4.1.2-1 built
and the changes to -2 seem minimal, so it should be easy to check
whether there was a gcc regression or the qt4-x11 changes triggered the FTBFS 
and need
a workaround.

qt4-x11 needs an update for X11R7 to reach testing, and I heard that
transition was planned for soon (possibly under 1 week). So, until this
bug is fixed, either it will a blocker, or 4.1.2-1 will be pushed on
alpha (which looks better, *if* doing that is possible).


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#368883: qt4-x11: FTBFS on alpha

2006-05-25 Thread Brian Nelson
Filipus Klutiero [EMAIL PROTECTED] writes:

 gcc ICEd when attempting to build qt4-x11 on alpha on 2006-05-14. I
 don't know what's the issue and what could fix. However, 4.1.2-1 built
 and the changes to -2 seem minimal, so it should be easy to check
 whether there was a gcc regression or the qt4-x11 changes triggered the
 FTBFS and need
 a workaround.

Isn't an ICE always a compiler bug?  In any case, nothing in the Qt code
changed between -1 and -2, so it's certainly a GCC regression.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#368883: qt4-x11: FTBFS on alpha

2006-05-25 Thread Filipus Klutiero

Brian Nelson a écrit :



Isn't an ICE always a compiler bug?


Yes, I was just asking if it was a new bug or a pre-existing one.


 In any case, nothing in the Qt code
changed between -1 and -2, so it's certainly a GCC regression.

Thanks for the information...I guess that's bad news. It seems there are 
almost 2 monthes of changes in the gcc 4.0 branch between 4.0.3-1 and 
4.0.3-3, so it's quite possible that it's indeed a GCC regression. When 
looking at the gcc-4.0 bugs reported in Debian's BTS for  4.0.3-1, I 
can't see much that would explain this.
I'm completely clueless about building, but somebody should start by 
figuring which GCC regression is blocking this. Given the fact that 
branch 4.0 looks very inactive, maybe the easiest thing would be to 
identify the changeset which introduced this regression.




Bug#368883: qt4-x11: FTBFS on alpha

2006-05-25 Thread Pierre Habouzit
Le Jeu 25 Mai 2006 22:30, Filipus Klutiero a écrit :
 Brian Nelson a écrit :
 Isn't an ICE always a compiler bug?

 Yes, I was just asking if it was a new bug or a pre-existing one.

   In any case, nothing in the Qt code
 changed between -1 and -2, so it's certainly a GCC regression.

 Thanks for the information...I guess that's bad news. It seems there
 are almost 2 monthes of changes in the gcc 4.0 branch between 4.0.3-1
 and 4.0.3-3, so it's quite possible that it's indeed a GCC
 regression. When looking at the gcc-4.0 bugs reported in Debian's BTS
 for  4.0.3-1, I can't see much that would explain this.
 I'm completely clueless about building, but somebody should start by
 figuring which GCC regression is blocking this. Given the fact that
 branch 4.0 looks very inactive, maybe the easiest thing would be to
 identify the changeset which introduced this regression.

one can also try to compile it with gcc 4.1
-- 
·O·  Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org


pgpgodT8j8Pjf.pgp
Description: PGP signature