app-office/openoffice-3.0.0 compilation breaks. ------------- /var/tmp/portage/app-office/openoffice-3.0.0/work/ooo/build/ooo300-m9/bridges/source/cpp_uno/gcc3_linux_x86-64 Making: ../../../unxlngx6.pro/slo/abi.obj /var/tmp/portage/app-office/openoffice-3.0.0/work/ooo/build/ooo300-m9/bridges/source/cpp_uno/gcc3_linux_x86-64/abi.cxx:76: error: '__int128_t' does not name a type dmake: Error code 1, while making '../../../unxlngx6.pro/slo/abi.obj' ERROR: Error 65280 occurred while making /var/tmp/portage/app-office/openoffice-3.0.0/work/ooo/build/ooo300-m9/bridges/source/cpp_uno/gcc3_linux_x86-64 rmdir /tmp/23763 make: *** [stamp/build] Error 1 * * ERROR: app-office/openoffice-3.0.0 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 5441: Called die * The specific snippet of code: * make || die "Build failed" * The die message: * Build failed Reproducible: Always Steps to Reproduce: 1.start emerging 2.you will get it 3. Actual Results: build fails, always on same place Expected Results: not to fail !!! When you file a bug report, please include the following information: GENTOO_VM=sun-jdk-1.6 CLASSPATH="" JAVA_HOME="/opt/sun-jdk-1.6.0.11" JAVACFLAGS="-source 1.5 -target 1.5" COMPILER="" COMPILER = gcc version 4.3.2 (Gentoo 4.3.2-r2 p1.5, pie-10.1.5) Note, in emerge --info, the running System kernel reported is not that of the target system for which OO is being compiled. I'm compiling in chroot invironment, with /proc mounted into my chroot system i'm busy emerging. Just thought I mention this.. emerge --info Portage 2.2_rc22 (default/linux/x86/2008.0, gcc-4.3.2, glibc-2.6.1-r0, 2.6.25-gentoo-r7_siberia x86_64) ================================================================= System uname: Linux-2.6.25-gentoo-r7_siberia-x86_64-Intel-R-_Core-TM-2_Duo_CPU_E7200_@_2.53GHz-with-glibc2.0 Timestamp of tree: Thu, 15 Jan 2009 23:15:02 +0000 ccache version 2.4 [disabled] app-shells/bash: 3.2_p39 dev-java/java-config: 1.3.7-r1, 2.1.6-r1 dev-lang/python: 2.4.4-r13, 2.5.2-r7 dev-python/pycrypto: 2.0.1-r6 dev-util/ccache: 2.4-r7 sys-apps/baselayout: 1.12.11.1 sys-apps/sandbox: 1.2.18.1-r2 sys-devel/autoconf: 2.13, 2.63 sys-devel/automake: 1.5, 1.7.9-r1, 1.9.6-r2, 1.10.2 sys-devel/binutils: 2.18-r3 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 1.5.26 virtual/os-headers: 2.6.27-r2 ACCEPT_KEYWORDS="x86" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=pentium -mmmx -msse -msse2 -msse3 -mssse3 -mfpmath=sse -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /var/lib/hsqldb" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/udev/rules.d" CXXFLAGS="-O2 -march=pentium -mmmx -msse -msse2 -msse3 -mssse3 -mfpmath=sse -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="distlocks fixpackages parallel-fetch preserve-libs protect-owned sandbox sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="ftp://ftp.wh2.tu-dresden.de/pub/mirrors/gentoo http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ ftp://mirror.netcologne.de/gentoo/ ftp://ftp.snt.utwente.nl/pub/os/linux/gentoo http://mirror.gentoo.no/ ftp://ftp.ing.umu.se/linux/gentoo/ " LANG="C" LDFLAGS="-Wl,-O1" LINGUAS="en en_GB en_US utf8" MAKEOPTS="-j1" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="X acl acpi alsa bash-completion berkdb branding bzip2 cli cracklib crypt cups curl cxx dbus dga directfb dri dvd ffmpeg firefox fortran gdbm gnutls gpm gtk hal iconv ipv6 isdnlog java java6 jpeg jpeg2k matroska midi mime mmx mp3 mplayer mudflap ncurses nls nptl nptlonly ogg openal opengl openmp pam pcmcia pcre pdf perl posix pppd python qt4 rdesktop readline reflection samba session sndfile spell spl sse sse2 sse3 ssl ssse3 svg svga sysfs tcpd theora truetype unicode usb v4l v4l2 vim-syntax vnc vorbis wifi win32codecs x264 x86 xinerama xml xorg xscreensaver xulrunner xv xvid zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 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 mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse synaptics evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en en_GB en_US utf8" USERLAND="GNU" VIDEO_CARDS="intel i810 i915 i940 i950 vesa fbdev vga" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LC_ALL, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
dtardon->denisr: Excuse me, but exactly what system (architecture) do you have (or think you have)? You've reported it against x86 (which is also what the 'emerge --info' listing says), but you're trying to compile openoffice for amd64 (or x86_64, which is what this arch is known like outside of gentoo).... The problematic file shouldn't be--and from quick peek into appropriate makefile.mk it isn't, indeed--compiled on any platform outside of amd64, so I think the problem is actually in your configuration, not in openoffice.
(In reply to comment #1) > dtardon->denisr: Excuse me, but exactly what system (architecture) do you have > (or think you have)? You've reported it against x86 (which is also what the > 'emerge --info' listing says), but you're trying to compile openoffice for > amd64 (or x86_64, which is what this arch is known like outside of gentoo).... > The problematic file shouldn't be--and from quick peek into appropriate > makefile.mk it isn't, indeed--compiled on any platform outside of amd64, so I > think the problem is actually in your configuration, not in openoffice. > I'm compiling it inside chroot x86 system, and so I'm trying to compile for x86. All other packages emerged this way for x86. The server on which I'm emerging the new Gentoo is actually x86_64, but everything inside the chroot environment is a proper x86 Gentoo system, which I've emerged up from stage3, all libs,compiler, apps etc ... Thus emerge --info shows all the right info about the x86 chroot environment. I don't know therefore why OO build thinks its being compiled on x86_64 ? Note that I have no problem while emering other applications this way (inside this chroot'ed x86 environment). The reason I noted the x86_64 fact previously is because on top of the emerge --info list, System uname shows kernel for x86_64, the running system kernel. (I have proc mounted in my chroot). May be I'm not correct about reporting this as bug in the OO building process, but since no other build so far got confused about which arch its being built for, it seems something OO specific in the build process here which fails. Everything else produced the intended x86 libs and apps.
(In reply to comment #2) > (In reply to comment #1) > > dtardon->denisr: Excuse me, but exactly what system (architecture) do you have > > (or think you have)? You've reported it against x86 (which is also what the > > 'emerge --info' listing says), but you're trying to compile openoffice for > > amd64 (or x86_64, which is what this arch is known like outside of gentoo).... > > The problematic file shouldn't be--and from quick peek into appropriate > > makefile.mk it isn't, indeed--compiled on any platform outside of amd64, so I > > think the problem is actually in your configuration, not in openoffice. > > > > I'm compiling it inside chroot x86 system, and so I'm trying to compile for > x86. All other packages emerged this way for x86. > The server on which I'm emerging the new Gentoo is actually x86_64, but > everything inside the chroot environment is a proper x86 Gentoo system, which > I've emerged up from stage3, all libs,compiler, apps etc ... > > Thus emerge --info shows all the right info about the x86 chroot environment. > I don't know therefore why OO build thinks its being compiled on x86_64 ? > > Note that I have no problem while emering other applications this way (inside > this chroot'ed x86 environment). > > The reason I noted the x86_64 fact previously is because on top of the emerge > --info list, System uname shows kernel for x86_64, the running system kernel. > (I have proc mounted in my chroot). > > May be I'm not correct about reporting this as bug in the OO building process, > but since no other build so far got confused about which arch its being built > for, it seems something OO specific in the build process here which fails. > Everything else produced the intended x86 libs and apps. > Perhaps setarch i686 is in order before compiling it ... Ooopsie, have to try it (pitty have to do this after reporting the bug) and see if it fixes my problem
(In reply to comment #3) > (In reply to comment #2) > > (In reply to comment #1) > > > dtardon->denisr: Excuse me, but exactly what system (architecture) do you have > > > (or think you have)? You've reported it against x86 (which is also what the > > > 'emerge --info' listing says), but you're trying to compile openoffice for > > > amd64 (or x86_64, which is what this arch is known like outside of gentoo).... > > > The problematic file shouldn't be--and from quick peek into appropriate > > > makefile.mk it isn't, indeed--compiled on any platform outside of amd64, so I > > > think the problem is actually in your configuration, not in openoffice. > > > > > > > I'm compiling it inside chroot x86 system, and so I'm trying to compile for > > x86. All other packages emerged this way for x86. > > The server on which I'm emerging the new Gentoo is actually x86_64, but > > everything inside the chroot environment is a proper x86 Gentoo system, which > > I've emerged up from stage3, all libs,compiler, apps etc ... > > > > Thus emerge --info shows all the right info about the x86 chroot environment. > > I don't know therefore why OO build thinks its being compiled on x86_64 ? > > > > Note that I have no problem while emering other applications this way (inside > > this chroot'ed x86 environment). > > > > The reason I noted the x86_64 fact previously is because on top of the emerge > > --info list, System uname shows kernel for x86_64, the running system kernel. > > (I have proc mounted in my chroot). > > > > May be I'm not correct about reporting this as bug in the OO building process, > > but since no other build so far got confused about which arch its being built > > for, it seems something OO specific in the build process here which fails. > > Everything else produced the intended x86 libs and apps. > > > > Perhaps setarch i686 is in order before compiling it ... > > Ooopsie, have to try it (pitty have to do this after reporting the bug) and see > if it fixes my problem > Ok, what's necessary to emerge it here successfully is chroot /my/newx86system setarch i686 Then it emerges fine. Hmm, strange other packages did not require this, but I guess its not a bug in OO build process. Sorry for reporting this, my bad
Thx a lot. I had the same problem. It made me crazy, because I couldn't get a logical explication for that strange behaviour. With setarch i686 it's working. Thanx again.
This is a user-side system-configuration problem, nothing we can do here, so closing
