[Lunar-bugs] [bug] qt3 fails to build

jasper maintainer at lunar-linux.org
Tue Aug 24 13:39:23 GMT 2004


 Project:      lunar-linux
 Version:      <none>
 Component:    moonbase (modules)
 Category:     bug reports
 Priority:     normal
 Assigned to:  florin
 Reported by:  jasper
 Updated by:   jasper
 Status:       active

Yay, I fixed it! Solution: rebuild gcc with _POSIX2_VERSION=199209

So, it might not be a bad idea to follow LFS in this and compile
coreutils to support the old style options... I have a feeling this
won't be the last problem related to this.

jasper



Previous comments:
------------------------------------------------------------------------

Sun, 08/22/2004 - 20:32 : jasper

gcc 3.3.3
kernel 2.6.8
CFLAGS = -O2 -mcpu=i686 -march=i686 -mmmx -msse -msse2
-mfpmath=sse,387

same thing without sse/sse2 and with -march=pentium4


I've no clue what could be the problem.

Relevant bit of error log:
===
QThreadStorage: thread 4000 exited after QThreadStorage destroyed
make[3]: *** [qmake_image_collection.cpp] Segmentation fault
make[3]: *** Deleting file `qmake_image_collection.cpp'
make[3]: Leaving directory
`/usr/src/qt-x11-free-3.3.3/tools/designer/designer'
make[2]: *** [sub-designer] Error 2
make[2]: Leaving directory `/usr/src/qt-x11-free-3.3.3/tools/designer'
make[1]: *** [sub-designer] Error 2
make[1]: Leaving directory `/usr/src/qt-x11-free-3.3.3/tools'
make: *** [sub-tools] Error 2
Creating /var/log/lunar/compile/qt3-3.3.3.bz2 
! Problem detected during BUILD
===

Jasper





------------------------------------------------------------------------

Sun, 08/22/2004 - 21:41 : florin

 Acording to some sources on the Internet, tis bug is generated by a
b0rked gcc. See
 
http://linuxfromscratch.org/pipermail/blfs-support/2004-February/048214.html

  The solution is to use a good gcc and maybe glibc.

  Florin


------------------------------------------------------------------------

Sun, 08/22/2004 - 21:49 : v3rt1g0

qt3 compiles fine on this box with the following specs, which is rather
close to you, strange...
gcc version: 3.3.3
glibc version: 2.3.3
kernel: 2.6.8.1 (headers: 2.6.8.0)
CFLAGS: -O3 -mcpu=pentium4 -march=pentium4 -funroll-loops -mmmx -msse
-msse2 -mfpmath=sse,387
CXXFLAGS: -O3 -mcpu=pentium4 -march=pentium4 -funroll-loops -mmmx -msse
-msse2 -mfpmath=sse,387 -Wno-deprecated

------------------------------------------------------------------------

Mon, 08/23/2004 - 12:45 : jasper

Apart from blaiming sofar, what is the cause for the broken coreutils?
And more importantly, if I rebuild from scratch, how do I prevent it
from happening again?

[OT] This issue tracker system is a bit strange with separate
'comments' and 'folow up' reply possibilities. 

------------------------------------------------------------------------

Mon, 08/23/2004 - 17:47 : florin

it seems that glibc 2.3.3 have some changes which permits the generation
of borked gcc and coreutils sometimes. It happened to me, perldude,
jazman until now. 


-- 
View: http://lunar-linux.org/?q=node/view/391
Edit: http://lunar-linux.org/?q=project/comments/add/391




More information about the Lunar-bugs mailing list