| Summary: | texlive-core-2007-r13 fails to build | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Greg Trigg <trigggl> |
| Component: | Current packages | Assignee: | ppc64 architecture team <ppc64> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | major | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | PPC64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Please also post your `emerge --info' (for both machines). could you verify that this happens with a stable system, too? (i.e. gcc-4.1.2) I returned my CFLAGS to normal, but that made no difference. It probably does have something to do with the gcc I'm using, but it may be too late for me to go back to 4.1.2. I tried that but other builds started failing. I'll try again. If I am able to go back, I'll update this report. emerge --info Portage 2.1.4.4 (default/linux/powerpc/ppc64/2008.0/64bit-userland, gcc-4.2.4, glibc-2.7-r2, 2.6.24-gentoo-r3 ppc64) ================================================================= System uname: 2.6.24-gentoo-r3 ppc64 POWER3 (630+) Timestamp of tree: Wed, 09 Jul 2008 11:04:01 +0000 distcc 2.18.3 powerpc64-unknown-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.4 [enabled] app-shells/bash: 3.2_p33 dev-lang/python: 2.4.4-r13 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.61-r2 sys-devel/automake: 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.1 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.24 ACCEPT_KEYWORDS="ppc64" CBUILD="powerpc64-unknown-linux-gnu" CFLAGS="-O2 -pipe" CHOST="powerpc64-unknown-linux-gnu" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c /etc/udev/rules.d" CXXFLAGS="-O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="buildpkg ccache distcc distlocks fixpackages metadata-transfer parallel-fetch sandbox sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS=" http://open-systems.ufl.edu/mirrors/gentoo " LANG="en_US.utf8" MAKEOPTS="-j5" 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" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="acl berkdb bzip2 cli cracklib crypt cups dri fortran gdbm gpm ibm iconv ipv6 isdnlog midi mudflap ncurses nls nptl nptlonly openmp pam pcre perl ppc64 pppd python readline reflection session spl ssl tcpd unicode xorg zlib" 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" 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 evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="fbdev mach64 mga nv r128 radeon" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS I suggest you eith downgrade to gcc 4.1.2 or upgrade to gcc 4.3.1-r1. I just compiled texlive-core-2007-r13 in my gcc-4.3.1-r1 chroot, no problems at all. I'm sorry I cannot help you more, but gcc 4.2.x doesn't seem to be a good choice on ppc64 :-/ Please reopen if you can reproduce with either gcc 4.1.2 or 4.3.x if you want to start from scratch you might find these stages useful: http://www.unixforces.net/~markus/gentoo/stages/ppc64/ I built the stages from 2008.07.06 using stable packages in addition to gcc-4.3.1-r1 and python-2.5.2-r5 from ~ppc64 (the python version is stable now, too). The stages are optimized for some cpus, too: power3, power4, power5. :-) |
Both of my IBM PPC64 machines fail to build app-text/texlive-core-2007-r13. Reproducible: Always Steps to Reproduce: 1. emerge --sync 2. emerge --update --newuse --deep world 3. Actual Results: powerpc64-unknown-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I./.. -DUNIX -DKPATHSEA -DNeedFunctionPrototypes -DSHIFTLOWCHARS -O3 -pipe -c squeeze.c /bin/sh ./texc.script ./tex.lpro texc.lpro ./texc.script: line 12: 25423 Segmentation fault ed $1 <<edscriptend /% begin code for uncompressed fonts only/d .,/% end code for uncompressed fonts only/d .,/% end of code for unpacking compressed fonts/s/% // w $2 edscriptend make[2]: *** [texc.lpro] Error 139 make[2]: *** Waiting for unfinished jobs.... make[2]: Leaving directory `/var/tmp/portage/app-text/texlive-core-2007-r13/work/texk/dvipsk' make[1]: *** [all] Error 1 make[1]: Leaving directory `/var/tmp/portage/app-text/texlive-core-2007-r13/work/texk' make: *** [all] Error 1 * * ERROR: app-text/texlive-core-2007-r13 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2856: Called die * The specific snippet of code: * emake texmf=${TEXMF_PATH:-/usr/share/texmf} || die "emake failed"; * The die message: * emake failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/app-text/texlive-core-2007-r13/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-text/texlive-core-2007-r13/temp/environment'. * Expected Results: A successful build. I'm using gcc 4.2.4 on two computers. One of them uses "-O3 -pipe", the other "-Os -pipe". They stop at an identical spot with the same errors.