matt@freebsd ~/gentoo $ tail -n 100 var/tmp/portage/media-libs/x264-0.0.20091021/temp/build.log * CPV: media-libs/x264-0.0.20091021 * REPO: gentoo_prefix * USE: amd64-fbsd elibc_FreeBSD kernel_FreeBSD prefix threads userland_GNU >>> Unpacking source... >>> Unpacking x264-snapshot-20091021-2245.tar.bz2 to /usr/home/matt/gentoo/var/tmp/portage/media-libs/x264-0.0.20091021/work >>> Source unpacked in /usr/home/matt/gentoo/var/tmp/portage/media-libs/x264-0.0.20091021/work >>> Preparing source in /usr/home/matt/gentoo/var/tmp/portage/media-libs/x264-0.0.20091021/work/x264-snapshot-20091021-2245 ... * Applying x264-nostrip.patch ... [ ok ] * Applying x264-onlylib-20090408.patch ... [ ok ] >>> Source prepared. >>> Configuring source in /usr/home/matt/gentoo/var/tmp/portage/media-libs/x264-0.0.20091021/work/x264-snapshot-20091021-2245 ... Found no assembler Minimum version is yasm-0.6.2 If you really want to compile without asm, configure with --disable-asm. * ERROR: media-libs/x264-0.0.20091021 failed: * (no error message) matt@freebsd ~/gentoo $ emerge --info Portage 2.2.00.15134-prefix (prefix/bsd/freebsd/8.0/x64, gcc-4.2.4, unavailable, 8.0-RELEASE amd64) ================================================================= System uname: FreeBSD-8.0-RELEASE-amd64-64bit-ELF Timestamp of tree: Tue, 29 Dec 2009 21:44:08 +0000 app-shells/bash: 4.0_p28-r00.1 dev-lang/python: 2.6.2-r2 sys-devel/autoconf: 2.13, 2.63-r01.1 sys-devel/automake: 1.10.2-r00.1 sys-devel/binutils: 2.20.51.0.4 sys-devel/gcc-config: 1.4.1-r00.2 sys-devel/libtool: 2.2.6b ACCEPT_KEYWORDS="~x64-freebsd" ACCEPT_LICENSE="* -@EULA" CBUILD="x86_64-pc-freebsd8.0" CFLAGS="-march=athlon64 -O2 -pipe" CHOST="x86_64-pc-freebsd8.0" CONFIG_PROTECT="/etc /usr/share/X11/xkb" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c" CXXFLAGS="-march=athlon64 -O2 -pipe" DISTDIR="/usr/home/matt/gentoo/usr/portage/distfiles" FEATURES="assume-digests collision-protect distlocks fixpackages news parallel-fetch preserve-libs protect-owned sfperms strict unmerge-logs unmerge-orphans userfetch" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LDFLAGS="" LINGUAS="en en_US" [ebuild N ] media-libs/x264-0.0.20091021 USE="threads -debug -pic" 0 kB
In x264 ebuild: x86-fbsd? ( >=dev-lang/yasm-0.6.2 )" So, if ARCH was modified in the prefix freebsd x64 profiles to x86-fbsd instead of amd64-fbsd we would probably gain the most from the Gentoo/fbsd team (because amd64-fbsd never really took off but x86-fbsd limps along). Just a thought, not sure what else it will break (if anything). IMO, the perfect time to test, while you are testing anyway..
re-visit if x64-freebsd port is ever re-vived.
