Bug 178652 - x11-libs/qt-4.3.2 compilation error - amd64 and gcc 3.4
|
Bug#:
178652
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: AMD64
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: qt@gentoo.org
|
Reported By: philip@lightbox.org
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: x11-libs/qt-4.3.2 compilation error - amd64 and gcc 3.4
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2007-05-15 14:43 0000
|
This is the error:
!!! ERROR: x11-libs/qt-4.3.0_rc1 failed.
Call stack:
ebuild.sh, line 1615: Called dyn_compile
ebuild.sh, line 972: Called qa_call 'src_compile'
ebuild.sh, line 44: Called src_compile
qt-4.3.0_rc1.ebuild, line 211: Called die
!!! (no error message)
!!! If you need support, post the topmost build error, and the call stack if
relevant.
!!! A complete build log is located at
'/var/log/portage/x11-libs:qt-4.3.0_rc1:20070515-135506.log'.
I'll attach the log.
emerge --info
Portage 2.1.2.7 (default-linux/amd64/2006.0, gcc-3.4.6, glibc-2.5-r2,
2.6.21-gentoo x86_64)
=================================================================
System uname: 2.6.21-gentoo x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor
3800+
Gentoo Base System release 1.12.10
Timestamp of tree: Tue, 15 May 2007 13:00:06 +0000
dev-java/java-config: 1.3.7, 2.0.32
dev-lang/python: 2.4.4-r4
dev-python/pycrypto: 2.0.1-r5
sys-apps/sandbox: 1.2.18.1
sys-devel/autoconf: 2.13, 2.61
sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
sys-devel/binutils: 2.17
sys-devel/gcc-config: 1.3.16
sys-devel/libtool: 1.5.23b
virtual/os-headers: 2.6.21
ACCEPT_KEYWORDS="amd64 ~amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config
/usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf
/etc/php/apache1-php5/ext-active/ /etc/php/apache2-php5/ext-active/
/etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild
/etc/terminfo"
CXXFLAGS="-O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/linux/distributions/gentoo"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress
--force --whole-file --delete --delete-after --stats --timeout=180
--exclude=/distfiles --exclude=/local --exclude=/packages
--filter=H_**/files/digest-*"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X alsa amd64 arts berkdb bitmap-fonts bzip2 cli cracklib crypt cups dri
eds emboss encode foomaticdb fortran gd gif gnome gpm gstreamer gtk gtk2 iconv
imlib ipv6 isdnlog java jpeg kde lzw lzw-tiff midi mp3 mpeg mysql ncurses nls
nptl ogg opengl pam pcre pdf perl php png pppd python qt3 qt4 quicktime
readline reflection sdl session speex spell spl ssl tcpd theora tiff truetype
truetype-fonts type1-fonts usb vorbis xml xorg xpm xscreensaver xv zip zlib"
ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x
ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3
trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw
asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa
lfloat linear meter mulaw multi null plug rate route share shm softvol"
ELIBC="glibc" INPUT_DEVICES="keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad
cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU"
VIDEO_CARDS="nv"
Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS,
LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS,
PORTDIR_OVERLAY
I'm sorry if this is vague or not a bug but I don't even know where to start
because there is no error message.
This is the bug:
g++ -c -include .pch/release-shared/QtGui -O2 -pipe -I/usr/include/mysql -O2
-pipe -Wall -W -D_REENTRANT -fPIC -DQT_SHARED -DQT_BUILD_GUI_LIB
-DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT
-DQT_RASTER_IMAGEENGINE -DQT_HAVE_MMX -DQT_HAVE_SSE -DQT_HAVE_SSE2
-DQT_NO_STYLE_MAC -DQT_NO_STYLE_WINDOWSVISTA -DQT_NO_STYLE_WINDOWSXP
-DQ_INTERNAL_QAPP_SRC -DQT_NO_DEBUG -DQT_CORE_LIB -D_LARGEFILE64_SOURCE
-D_LARGEFILE_SOURCE -I../../mkspecs/linux-g++ -I. -I../../include/QtCore
-I../../include/QtCore -I../../include -I../../include/QtGui
-I/usr/include/freetype2 -I../3rdparty/harfbuzz/src -Idialogs
-I.moc/release-shared -I/usr/include -I.uic/release-shared -o
.obj/release-shared/qcleanlooksstyle.o styles/qcleanlooksstyle.cpp
../../include/QtCore/../../src/corelib/arch/qatomic_x86_64.h: In member
function `virtual QRect QStyleSheetStyle::subElementRect(QStyle::SubElement,
const QStyleOption*, const QWidget*) const':
../../include/QtCore/../../src/corelib/arch/qatomic_x86_64.h:105: error:
inconsistent operand constraints in an `asm'
../../include/QtCore/../../src/corelib/arch/qatomic_x86_64.h:105: error:
inconsistent operand constraints in an `asm'
Maybe the amd64 team can help here.
Ok, cool thank you.
Apparently I had gcc 4+ installed but it wasn't being used so I used gcc-config
to change my profile. That fixed the problem.
Next time I'll be sure to check the bug reports of the app I'm having a problem
with before filing.
Thanks again for your help and patience.
no problem. It isn't exactly an easy one to diagnose.
*** Bug 180792 has been marked as a duplicate of this bug. ***
*** Bug 189020 has been marked as a duplicate of this bug. ***
*** Bug 189493 has been marked as a duplicate of this bug. ***
*** Bug 191161 has been marked as a duplicate of this bug. ***
*** Bug 191690 has been marked as a duplicate of this bug. ***
*** Bug 192685 has been marked as a duplicate of this bug. ***
*** Bug 197453 has been marked as a duplicate of this bug. ***
*** Bug 198066 has been marked as a duplicate of this bug. ***
*** Bug 201009 has been marked as a duplicate of this bug. ***
Please patch qt-4.3.2.ebuild with the patch too else qt-4.3.2 does not compile
on amd64 with gcc-3.4.6 (bug 201009).
With added patch qt-4.3.2 does compile for me.
Same here, build fails with the ebuild as it is in CVS on systems using gcc-3.4
(e.g. hardened amd64).
My patch from 2007-09-16 fixes it.
The patch applies against x11-libs/qt-4.3.2 (offset 1 line) and I have tested
it successfully on hardened amd64.
Therefore I ask for the patch being applied against x11-libs/qt-4.3.2 from CVS.
Any objections?
Regards,
Milan
I'm having the same problem and I'd love to have that patch in the tree.
Also, emerging skype fails like this for me:
The specific snippet of code:
* [[ -z ${PKG} ]] && die "Unable to resolve $1 to an installed package"
* The die message:
* Unable to resolve >=x11-libs/qt-4.0 to an installed package
I'm trying to emerge qt manually, but shouldn't it be pulled in as a
dependency?
this problem still exists with qt-4.3.2, qt-4.3.2-r1 and qt-4.3.3, so i request
a reopening of this bug. The diff should be add to the newer versions too.
Same problem here with qt-4.3.2-r1.
Can the solution be made mainstream?
Daniel (amd64, gcc-3.4.6)
Nothing for amd64 here, up to qt maintainers to apply or not apply the patch
for obsolete GCC3. Why would anyone use it, is beyond me..
To quote Comment #3 once again:
> The solution is to either compile without -O2, use the -fno-gcse, or use a more
> current compiler (gcc 4.1, for example).
hardened should grow itself a decent toolchain, and noone else should use gcc3.
The patch is nasty, if anything the ebuild should just check for sucky gcc
version and use append-flags accordingly.
i have same problem compiling qt on intel pentium pro with gcc v.4.1.2
so it is not just amd64 and gcc v.3.x.x problem
*** Bug 212579 has been marked as a duplicate of this bug. ***
*** Bug 213038 has been marked as a duplicate of this bug. ***
Fixed in qt-{4.3.2-r1,4.3.4,4.4.0_beta1}, by appending -fno-gcse, for amd64
with GCC 3.
*** Bug 219869 has been marked as a duplicate of this bug. ***
*** Bug 246426 has been marked as a duplicate of this bug. ***