Hi, sys-fs/xfsprogs-2.7.11 won't compile on PPC64: [...] powerpc64-unknown-linux-gnu-gcc -O1 -pipe -mtune=970 -mcpu=970 -mabi=altivec -g -DNDEBUG -funsigned-char -fno-strict-aliasing -Wall -DVERSION=\"2.7.11\" -DLOCALEDIR=\"/usr/share/locale\" -DPACKAGE=\"xfsprogs\" -I../include -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -c -o xfs_copy.o xfs_copy.c In file included from /usr/include/asm/elf.h:8, from /usr/include/asm/sigcontext.h:13, from /usr/include/bits/sigcontext.h:28, from /usr/include/signal.h:333, from /usr/include/sys/wait.h:31, from xfs_copy.c:21: /usr/include/asm/types.h:40: error: conflicting types for ‘__s64’ ../include/xfs/platform_defs.h:42: error: previous declaration of ‘__s64’ was here /usr/include/asm/types.h:41: error: conflicting types for ‘__u64’ ../include/xfs/platform_defs.h:41: error: previous declaration of ‘__u64’ was here gmake[1]: *** [xfs_copy.o] Error 1 make: *** [default] Error 2 # emerge --info Portage 2.1_pre9-r4 (default-linux/ppc/ppc64/2006.0/64bit-userland/970/pmac, gcc-4.1.0, glibc-2.4-r2, 2.6.16-gentoo-r3 ppc64) ================================================================= System uname: 2.6.16-gentoo-r3 ppc64 PPC970FX, altivec supported Gentoo Base System version 1.6.14 dev-lang/python: 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.16 ACCEPT_KEYWORDS="ppc64" AUTOCLEAN="yes" CBUILD="powerpc64-unknown-linux-gnu" CFLAGS="-O2 -pipe -mtune=970 -mcpu=970 -mabi=altivec -ftree-vectorize -g" CHOST="powerpc64-unknown-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config /usr/share/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-O2 -pipe -mtune=970 -mcpu=970 -mabi=altivec -ftree-vectorize -g" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks installsources metadata-transfer sandbox sfperms splitdebug strict" GENTOO_MIRRORS="http://mirrors.sec.informatik.tu-darmstadt.de/gentoo/" LANG="en_US.UTF-8" LC_ALL="en_US.UTF-8" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="ppc64 X a52 aac alsa altivec amr apache2 apm berkdb bitmap-fonts bzip2 cdparanoia cdr cli crypt cups dri dts dv dvd dvdr dvdread eds emboss encode exscalibar ffmpeg foomaticdb fortran gdbm ggi gif glitz gmp gnokii gnutls gphoto2 gpm graphviz gstreamer gtk gtk2 hal imagemagick imlib input_devices_keyboard input_devices_mouse ipv6 jpeg kde kdeenablefinal libg++ libwww mad matroska mikmod motif mp3 mp4 mpeg mplayer musicbrainz ncurses nls nptl nptlonly ogg openal opengl pam pcre pdflib perl png ppds python qt qt4 quicktime readline reflection samba sdl session spell spl ssl subtitles tcltk tcpd tetex theora threads tiff truetype truetype-fonts type1-fonts udev unicode usb video_cards_radeon vorbis x264 xcomposite xml xorg xv xvid xvmc zeroconf zlib elibc_glibc kernel_linux userland_GNU" Unset: ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS, LINGUAS, MAKEOPTS, PORTDIR_OVERLAY
Ditto. Hasn't compiled since 2.7.3. Portage 2.1_rc1-r2 (default-linux/ppc/2005.1/ppc64/64bit-userland, gcc-3.4.6, glibc-2.3.6-r4, 2.6.14-gentoo-r7 ppc64) ================================================================= System uname: 2.6.14-gentoo-r7 ppc64 PPC970, altivec supported Gentoo Base System version 1.12.0_pre19 ccache version 2.4 [enabled] dev-lang/python: 2.4.3-r1 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.4-r1 dev-util/confcache: 0.4.2 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r2 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r5 ACCEPT_KEYWORDS="ppc64 ~ppc64" AUTOCLEAN="yes" CBUILD="powerpc64-unknown-linux-gnu" CFLAGS="-O2 -pipe -mcpu=970 -maltivec -mabi=altivec -fomit-frame-pointer" CHOST="powerpc64-unknown-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/init.d /etc/revdep-rebuild /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -pipe -mcpu=970 -maltivec -mabi=altivec -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache confcache distlocks metadata-transfer sandbox sfperms strict userpriv usersandbox" 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'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://localhost/gentoo-portage" USE="ppc64 X509 acl adns altivec apache bash-completion bcmath berkdb big-tables bitmap-fonts bzip2 cgi chroot cli cluster crypt ctype curl dba discard-path dri ecc extraengine force-cgi-redirect ftp gd gdbm gif glibc-omitfp gmp gnutls gpgme hardened hardenedphp hash hpn ibm idea imap inifile ithreads jpeg kerberos libclamav lingerd linuxthreads-tls mailwrapper max-idx-128 md5sum mhash mysql mysqli ncurses nolvmstatic nptl nptlonly oav pcntl pcre pear perl png pop posix python readline reflection samba session simplexml smime smtp snmp soap sockets socks5 spl sqlite ssl swat syslog sysvipc tcpd threads tiff truetype truetype-fonts type1-fonts unicode usb userlocales utf8 xml xml2 xmlrpc xmlwriter xorg xsl zip zlib elibc_glibc kernel_linux userland_GNU" Unset: ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY I just noticed that I'm still using the 2005.0 profile; going to change over to 2006.0 and see if it makes any difference.
Just changed to the hardened-ppc64 profile (didn't see a 2006.0 one, and hardened fit my purpose) and no love. I wonder if the 2.6.16 headers will fix this one, but I'm scared to try, given the dire warning in package.mask about combustibility. Any hope?
opened an upstream bug.
sys-fs/xfsprogs-2.8.10 dies even earlier; any word from upstream?
well.. they said nothing but "check your linux headers!" (see URL field of this bug)
So this is the error message from xfsprogs-2.8.10: In file included from /usr/include/asm/elf.h:8, from /usr/include/asm/sigcontext.h:13, from /usr/include/bits/sigcontext.h:28, from /usr/include/signal.h:333, from /usr/include/aio.h:28, from lio.c:3: /usr/include/asm/types.h:44: error: conflicting types for '__s64' ../include/xfs/platform_defs.h:42: error: previous declaration of '__s64' was here /usr/include/asm/types.h:45: error: conflicting types for '__u64' ../include/xfs/platform_defs.h:41: error: previous declaration of '__u64' was here This happens because asm/sigcontext.h does only include asm/elf.h and so asm/elf.h if __powerpc64__ is defined (needed for elf_gregset_t/elf_fpregset_t).
Created attachment 98029 [details, diff] xfsprogs-2.8.10-ppc64-types.patch ok... this is a hack to get this thing compiled. should only be applied on ppc64...
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=199315
Created attachment 98038 [details, diff] xfsprogs-2.8.10-ppc64-types.patch updated patch. *should* work on all arches, but I haven't tested on any other arch than ppc64 (lack of machine).
Created attachment 98096 [details, diff] xfsprogs-2.8.10-types.patch this is the patch from upstream and is already in upstream CVS for 2.8.13.
base-system: can we add the patch as 2.8.10-r1?
if you dont get to this before i do, feel free
added fix to 2.8.11
This is back in 2.8.21: powerpc64-unknown-linux-gnu-gcc -O3 -pipe -mtune=970 -mcpu=970 -mabi=altivec -O3 -pipe -mtune=970 -mcpu=970 -mabi=altivec -DNDEBUG -DVERSION=\"2.8.21\" -DLOCALEDIR=\"/usr/share/locale\" -DPACKAGE=\"xfsprogs\" -I./include -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -funsigned-char -fno-strict-aliasing -Wall -I. -O3 -pipe -mtune=970 -mcpu=970 -mabi=altivec -DNDEBUG -DVERSION=\"2.8.21\" -DLOCALEDIR=\"/usr/share/locale\" -DPACKAGE=\"xfsprogs\" -I../include -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -funsigned-char -fno-strict-aliasing -Wall -c lio.c -fPIC -DPIC -o .libs/lio.oIn file included from /usr/include/asm/elf.h:8, from /usr/include/asm/sigcontext.h:13, from /usr/include/bits/sigcontext.h:28, from /usr/include/signal.h:333, from /usr/include/aio.h:28, from lio.c:3:/usr/include/asm/types.h:44: error: conflicting types for '__s64'../include/xfs/platform_defs.h:45: error: previous declaration of '__s64' was here/usr/include/asm/types.h:45: error: conflicting types for '__u64'../include/xfs/platform_defs.h:44: error: previous declaration of '__u64' was heregmake[1]: *** [lio.lo] Error 1make: *** [default] Error 2
nah.. that output got corrupted while copy and paste.. stupid mac os x terminal! Will investigate when I'm next to my G5 again.
Created attachment 121587 [details, diff] xfsprogs-2.8.21-kern-types.patch this solved the problem once again.
patch added
base-system: please drop xfsprogs-2.8.21-kern-types.patch from the xfsprogs ebuild with the next version. As x86 already has stablized sys-fs/xfsprogs-2.9.4 for bug #197204 I don't want to touch a stable ebuild, but 2.9.4 does not need the patch any more.
@corsair - 2.9.4 is now stable for ppc64, do you want to close this bug?
once there is a new version in the tree, then the types patch can be dropped as it is no longer required. I just don't want to touch a patch in a stable ebuild. adjusting description.
xfsprogs-2.9.5 in the tree w/out the patch
