Summary: | x11-libs/qt-4.1.4 compilation failure | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Patrick Lauer <patrick> |
Component: | New packages | Assignee: | Qt Bug Alias <qt> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | cla |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Patrick Lauer
![]() Oops, wrong emerge --info, here's the correct one: Portage 2.1.2_pre2 (default-linux/x86/2006.1, gcc-4.1.1, glibc-2.4-r3, 2.6.16.16 x86_64) ================================================================= System uname: 2.6.16.16 x86_64 AMD Athlon(tm) 64 Processor 3200+ Gentoo Base System version 1.12.5 Last Sync: Sun, 01 Oct 2006 09:50:01 +0000 ccache version 2.3 [enabled] app-admin/eselect-compiler: [Not Present] dev-java/java-config: [Not Present] dev-lang/python: 2.4.3-r4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.3 dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.7.9-r1, 1.9.6-r2 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.13-r3 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=i686 -pipe" CHOST="i686-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/gconf /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-O2 -march=i686 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig buildpkg ccache distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://85.25.128.62 ftp://212.219.56.134/sites/www.ibiblio.org/gentoo/ ftp://ftp.snt.utwente.nl/pub/os/linux/gentoo" 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'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync12.de.gentoo.org/gentoo-portage" USE="x86 X berkdb bitmap-fonts cli crypt cups dlloader dri elibc_glibc fortran gdbm gpm input_devices_evdev input_devices_keyboard input_devices_mouse ipv6 isdnlog kernel_linux libg++ ncurses nls nptl nptlonly pam pcre perl ppds pppd python readline reflection session spl ssl tcpd truetype-fonts type1-fonts udev unicode userland_GNU video_cards_apm video_cards_ark video_cards_ati video_cards_chips video_cards_cirrus video_cards_cyrix video_cards_dummy video_cards_fbdev video_cards_glint video_cards_i128 video_cards_i740 video_cards_i810 video_cards_imstt video_cards_mga video_cards_neomagic video_cards_nsc video_cards_nv video_cards_rendition video_cards_s3 video_cards_s3virge video_cards_savage video_cards_siliconmotion video_cards_sis video_cards_sisusb video_cards_tdfx video_cards_tga video_cards_trident video_cards_tseng video_cards_v4l video_cards_vesa video_cards_vga video_cards_via video_cards_vmware video_cards_voodoo xorg zlib" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS, PORTAGE_RSYNC_EXTRA_OPTS If you emerge it again, does it fail in the same place? What if you remove the portage tmpdir before re-emerging? (In reply to comment #2) > If you emerge it again, does it fail in the same place? Yes, reliably > What if you remove the portage tmpdir before re-emerging? same error Right when you start the emerge, can you pick out what Qt is picking up as your architecture? It uses some assembly routines based on what it thinks your arch is, and I'm wondering if it's not picking it up correctly on your machine. emergering new version of qt (4.1.4) fails as described here. reemergering causes same thing at same place during compilation. After emergering glib(replacing to the same version) and removing glib-2.0 folder from /usr/lib/local, as well as pkgconfig info (glib-2.0.pc) to "safe" place, compiling was successfull. Caleb, arch was picked correctly(both times). (In reply to comment #4) > Right when you start the emerge, can you pick out what Qt is picking up as your > architecture? It uses some assembly routines based on what it thinks your arch > is, and I'm wondering if it's not picking it up correctly on your machine. > >>> Compiling source in /var/tmp/portage/qt-4.1.4/work/qt-x11-opensource-src-4.1.4 ... This is the Qt/X11 Open Source Edition. Determining system architecture... (Linux:2.6.16.16:x86_64) 64-bit AMD 80x86 (x86_64) 'x86_64' is supported System architecture: 'x86_64' -fvisibility support enabled. sse support enabled. This is running in a 32bit chroot, so of course 64bit assembler can and will fail :-) I know that this is mildly unusual, but it's a 64bit box building binpkgs for 32bit x86 ... I've just run into the exact same issue, with 4.2.2. I dealt with it by using the setarch utility before running the qt compile. You can actually use setarch with chroot as well, which should fool any other "clever" build scripts. Use setarch; INVALID. *** Bug 209584 has been marked as a duplicate of this bug. *** |