Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 81627 - QT 3.3.4-r2 hangs when calling qmake during compilation
Summary: QT 3.3.4-r2 hangs when calling qmake during compilation
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 All
: High critical (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-11 07:26 UTC by Robert Führicht
Modified: 2005-02-14 05:48 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Führicht 2005-02-11 07:26:57 UTC
To reproduce:

1. emerge qt

--- output from emerge process ---

Finding project files. Please wait...
  242 projects found.

Creating makefiles. Please wait...
  for /var/tmp/portage/qt-3.3.4-r2/work/qt-x11-free-3.3.4/src/moc/moc.pro (linux-g++)
/var/tmp/portage/qt-3.3.4-r2/work/qt-x11-free-3.3.4/bin/qmake  -spec /var/tmp/portage/qt-3.3.4-r2/work/qt-x11-free-3.3.4/mkspecs/linux-g++ -o /var/tmp/portage/qt-3.3.4-r2/work/qt-x11-free-3.3.4/./src/moc /var/tmp/portage/qt-3.3.4-r2/work/qt-x11-free-3.3.4/src/moc/moc.pro
  for /var/tmp/portage/qt-3.3.4-r2/work/qt-x11-free-3.3.4/src/qt.pro (linux-g++)
/var/tmp/portage/qt-3.3.4-r2/work/qt-x11-free-3.3.4/bin/qmake  -spec /var/tmp/portage/qt-3.3.4-r2/work/qt-x11-free-3.3.4/mkspecs/linux-g++ -o /var/tmp/portage/qt-3.3.4-r2/work/qt-x11-free-3.3.4/./src /var/tmp/portage/qt-3.3.4-r2/work/qt-x11-free-3.3.4/src/qt.pro
^^^^ hangs here
--- /output from emerge process ---

top shows qmake hogs the cpu, there is no disc activity.

--- emerge info ---

Portage 2.0.51-r15 (default-linux/amd64/2005.0, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.10-gentoo-r7 x86_64)
=================================================================
System uname: 2.6.10-gentoo-r7 x86_64 AMD Athlon(tm) 64 Processor 3200+
Gentoo Base System version 1.6.9
Python:              dev-lang/python-2.2.3-r5,dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb  7 2005, 06:49:42)]
dev-lang/python:     2.2.3-r5, 2.3.4-r1
sys-devel/autoconf:  2.59-r6, 2.13
sys-devel/automake:  1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4
sys-devel/binutils:  2.15.92.0.2-r2
sys-devel/libtool:   1.5.10-r4
virtual/os-headers:  2.6.8.1-r4
ACCEPT_KEYWORDS="amd64 ~amd64"
AUTOCLEAN="yes"
CFLAGS="-O3 -pipe -march=k8 -ftracer -funroll-all-loops -fpeel-loops"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -pipe -march=k8 -ftracer -funroll-all-loops -fpeel-loops"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig digest distlocks sandbox userpriv usersandbox"
GENTOO_MIRRORS="http://gentoo.inode.at/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="amd64 X acpi alsa avi berkdb bitmap-fonts calendar cdparanoia cdr crypt cups dga dillo directfb divx4linux dvd encode esd f77 fam flac foomaticdb fortran gcj gif gtk gtk2 icq imagemagick imlib java jp2 jpeg junit kde libwww lzw lzw-tiff matroska mikmod mpeg ncurses nls nptl nptlonly offensive oggvorbis opengl oss pam pdflib png ppds qt readline samba sdl slang ssl tcpd tetex tiff truetype truetype-fonts type1-fonts usb userlocales xml2 xmms xpm xrandr xv xvid zlib linguas_de"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS

--- /emerge info ---
Comment 1 Caleb Tennis (RETIRED) gentoo-dev 2005-02-11 11:06:20 UTC
This shouldn't have anything to do with the ebuild - it could be anything - your kernel scheduler or compiler most likely.
Comment 2 Robert Führicht 2005-02-11 11:25:25 UTC
I just tried with gcc 4.0.0, same result
Any idea what I could try to get to the bottom of this? What bothers me is that it always occurs at same spot.
Comment 3 Lares Moreau 2005-02-11 18:24:58 UTC
Compiles okay here.  Perhaps the use of more extreme CFLAGS could be the problem. Try again w/ CFLAGS="-O2 -mtune=k8 -pipe"
Comment 4 Robert Führicht 2005-02-12 01:02:58 UTC
less aggressive CFLAGS have no effect, I tried rebuilding gcc in a 2004.3 stage 3 chroot, I switched to another kernel, I recompiled binutils with the rebuilt gcc, but nothing seems to help...
Comment 5 Robert Führicht 2005-02-14 05:48:20 UTC
I replaced gcc, binutils and glibc by using a stage 3 tarball, and it compiles now... I don't know which package broke, I'm recompiling them with reduced CFLAGS as I type.