View previous topic :: View next topic |
Author |
Message |
legacy Tux's lil' helper
Joined: 10 Sep 2012 Posts: 144
|
Posted: Sun Dec 20, 2015 12:40 am Post subject: crossdev mips64-unknown-linux-gnu fails |
|
|
Code: |
crossdev -v -t mips64-unknown-linux-gnu
|
fails with this error
Code: |
>>> Failed to emerge cross-mips64-unknown-linux-gnu/glibc-2.22-r1, Log file:
>>> '/var/tmp/portage/cross-mips64-unknown-linux-gnu/glibc-2.22-r1/temp/build.log'
* Messages for package cross-mips64-unknown-linux-gnu/glibc-2.22-r1:
* ERROR: cross-mips64-unknown-linux-gnu/glibc-2.22-r1::myOverlay failed (configure phase):
* failed to configure glibc
*
* Call stack:
* ebuild.sh, line 93: Called src_configure
* environment, line 3220: Called eblit-run 'src_configure'
* environment, line 943: Called eblit-glibc-src_configure
* src_configure.eblit, line 258: Called foreach_abi 'toolchain-glibc_src_configure'
* common.eblit, line 343: Called toolchain-glibc_src_configure
* src_configure.eblit, line 250: Called toolchain-glibc_headers_configure
* src_configure.eblit, line 245: Called die
* The specific snippet of code:
* CC="$(tc-getBUILD_CC)" \
* CFLAGS="-O1 -pipe" \
* CPPFLAGS="-U_FORTIFY_SOURCE" \
* LDFLAGS="" \
* "$@" || die "failed to configure glibc"
*
* If you need support, post the output of `emerge --info '=cross-mips64-unknown-linux-gnu/glibc-2.22-r1::myOverlay'`,
* the complete build log and the output of `emerge -pqv '=cross-mips64-unknown-linux-gnu/glibc-2.22-r1::myOverlay'`.
* The complete build log is located at '/var/tmp/portage/cross-mips64-unknown-linux-gnu/glibc-2.22-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/cross-mips64-unknown-linux-gnu/glibc-2.22-r1/temp/environment'.
* Working directory: '/var/tmp/portage/cross-mips64-unknown-linux-gnu/glibc-2.22-r1/work/build-default-mips64-unknown-linux-gnu-headers'
* S: '/var/tmp/portage/cross-mips64-unknown-linux-gnu/glibc-2.22-r1/work/glibc-2.22'
* glibc failed :(
* If you file a bug, please attach the following logfiles:
* /var/log/portage/cross-mips64-unknown-linux-gnu-info.log
* /var/log/portage/cross-mips64-unknown-linux-gnu-glibc-headers.log.xz
* /var/tmp/portage/cross-mips64-unknown-linux-gnu/glibc*/temp/glibc-config.logs.tar.xz
|
what have I to do to fix ?
I am using the last stage3 for i586 plus the last portage, everything is fresh installed ! |
|
Back to top |
|
|
legacy Tux's lil' helper
Joined: 10 Sep 2012 Posts: 144
|
Posted: Fri Dec 25, 2015 6:57 pm Post subject: |
|
|
Code: |
x60 ~ # PORTDIR_OVERLAY="/usr/local/portage-crossdev" ACCEPT_KEYWORDS="mips" crossdev -v --target mips64-unknown-linux-gnu
|
Code: |
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
* crossdev version: 20150602
* Host Portage ARCH: x86
* Target Portage ARCH: mips
* Target System: mips64-unknown-linux-gnu
* Stage: 4 (C/C++ compiler)
* ABIs: n32
* binutils: binutils-[latest]
* gcc: gcc-[latest]
* headers: linux-headers-[latest]
* libc: glibc-[latest]
* CROSSDEV_OVERLAY: /usr/local/portage/gentoo-b3
* PORT_LOGDIR: /var/log/portage
* PORTAGE_CONFIGROOT:
* Portage flags: -v
_ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~
* leaving sys-devel/binutils in /usr/local/portage/gentoo-b3
* leaving sys-devel/gcc in /usr/local/portage/gentoo-b3
* leaving sys-kernel/linux-headers in /usr/local/portage/gentoo-b3
* leaving sys-libs/glibc in /usr/local/portage/gentoo-b3
* leaving sys-devel/gdb in /usr/local/portage/gentoo-b3
* leaving metadata/layout.conf alone in /usr/local/portage/gentoo-b3
_ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~
* Log: /var/log/portage/cross-mips64-unknown-linux-gnu-binutils.log
* Emerging cross-binutils ...
* IMPORTANT: 19 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
These are the packages that would be merged, in order:
Calculating dependencies .... done!
Total: 0 packages, Size of downloads: 0 KiB
[ ok ]
* Log: /var/log/portage/cross-mips64-unknown-linux-gnu-linux-headers-quick.log
* Emerging cross-linux-headers-quick ...
* IMPORTANT: 19 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
These are the packages that would be merged, in order:
Calculating dependencies .... done!
Total: 0 packages, Size of downloads: 0 KiB
[ ok ]
* Log: /var/log/portage/cross-mips64-unknown-linux-gnu-glibc-headers.log
* Emerging cross-glibc-headers ...
* IMPORTANT: 19 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
These are the packages that would be merged, in order:
[ebuild N *] cross-mips64-unknown-linux-gnu/glibc-9999:2.2::gentoo-b3 USE="gd -debug -hardened -multilib -nscd -profile (-selinux) -suid -systemtap -vanilla" 0 KiB
Total: 1 package (1 new), Size of downloads: 0 KiB
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) cross-mips64-unknown-linux-gnu/glibc-9999::gentoo-b3
>>> Unpacking source...
GIT update -->
repository: git://sourceware.org/git/glibc.git
at the commit: 3cf74f8a4a0e0c7b7a9b4d40ba220832f33ea638
branch: master
storage directory: "/usr/portage/distfiles/egit-src/glibc.git"
checkout type: bare repository
Cloning into '/var/tmp/portage/cross-mips64-unknown-linux-gnu/glibc-9999/work/glibc-9999'...
done.
Checking out files: 100% (15312/15312), done.
Branch branch-master set up to track remote branch master from origin.
Switched to a new branch 'branch-master'
>>> Unpacked to /var/tmp/portage/cross-mips64-unknown-linux-gnu/glibc-9999/work/glibc-9999
>>> Source unpacked in /var/tmp/portage/cross-mips64-unknown-linux-gnu/glibc-9999/work
>>> Preparing source in /var/tmp/portage/cross-mips64-unknown-linux-gnu/glibc-9999/work/glibc-9999 ...
* Using GNU config files from /usr/share/gnuconfig
* Updating scripts/config.sub
[ ok ]
* Updating scripts/config.guess
[ ok ]
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/cross-mips64-unknown-linux-gnu/glibc-9999/work/glibc-9999 ...
* Running toolchain-glibc_src_configure for ABI n32
* Forcing cached settings:
* ac_cv_header_cpuid_h=yes
* libc_cv_386_tls=yes
* libc_cv_390_tls=yes
* libc_cv_alpha_tls=yes
* libc_cv_arm_tls=yes
* libc_cv_hppa_tls=yes
* libc_cv_ia64_tls=yes
* libc_cv_mips_tls=yes
* libc_cv_powerpc_tls=yes
* libc_cv_powerpc32_tls=yes
* libc_cv_powerpc64_tls=yes
* libc_cv_sparc_tls=yes
* libc_cv_sparc32_tls=yes
* libc_cv_sparc64_tls=yes
* libc_cv_sh_tls=yes
* libc_cv_x86_64_tls=yes
* libc_cv_asm_cfi_directives=yes
* libc_cv_broken_visibility_attribute=no
* libc_cv_c_cleanup=yes
* libc_cv_forced_unwind=yes
* libc_cv_gcc___thread=yes
* libc_cv_mlong_double_128=yes
* libc_cv_mlong_double_128ibm=yes
* libc_cv_ppc_machine=yes
* libc_cv_ppc_rel16=yes
* libc_cv_predef_fortify_source=no
* libc_cv_predef_stack_protector=no
* libc_cv_visibility_attribute=yes
* libc_cv_z_combreloc=yes
* libc_cv_z_execstack=yes
* libc_cv_z_initfirst=yes
* libc_cv_z_nodelete=yes
* libc_cv_z_nodlopen=yes
* libc_cv_z_relro=yes
* libc_mips_abi=default
* libc_mips_float=hard
/var/tmp/portage/cross-mips64-unknown-linux-gnu/glibc-9999/work/glibc-9999/configure --disable-sanity-checks --enable-hacker-mode --without-cvs --disable-werror --enable-bind-now --build=i686-pc-linux-gnu --host=mips64-unknown-linux-gnu --with-headers=/usr/mips64-unknown-linux-gnu/usr/include --prefix=/usr --enable-add-ons=
configure: loading site script /usr/share/config.site
checking build system type... i686-pc-linux-gnu
checking host system type... mips64-unknown-linux-gnu
checking for mips64-unknown-linux-gnu-gcc... i686-pc-linux-gnu-gcc
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether i686-pc-linux-gnu-gcc accepts -g... yes
checking for gcc... gcc
checking for mips64-unknown-linux-gnu-readelf... mips64-unknown-linux-gnu-readelf
checking for mips64-unknown-linux-gnu-g++... no
checking for mips64-unknown-linux-gnu-c++... no
checking for mips64-unknown-linux-gnu-gpp... no
checking for mips64-unknown-linux-gnu-aCC... no
checking for mips64-unknown-linux-gnu-CC... no
checking for mips64-unknown-linux-gnu-cxx... no
checking for mips64-unknown-linux-gnu-cc++... no
checking for mips64-unknown-linux-gnu-cl.exe... no
checking for mips64-unknown-linux-gnu-FCC... no
checking for mips64-unknown-linux-gnu-KCC... no
checking for mips64-unknown-linux-gnu-RCC... no
checking for mips64-unknown-linux-gnu-xlC_r... no
checking for mips64-unknown-linux-gnu-xlC... no
checking for g++... g++
configure: WARNING: using cross tools not prefixed with host triplet
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking whether g++ can link programs... yes
checking for sysdeps preconfigure fragments... aarch64 alpha arm hppa i386 m68k microblaze mips configure: error: Unable to determine ABI.
* ERROR: cross-mips64-unknown-linux-gnu/glibc-9999::gentoo-b3 failed (configure phase):
* failed to configure glibc
*
* Call stack:
* ebuild.sh, line 93: Called src_configure
* environment, line 3539: Called eblit-run 'src_configure'
* environment, line 949: Called eblit-glibc-src_configure
* src_configure.eblit, line 258: Called foreach_abi 'toolchain-glibc_src_configure'
* common.eblit, line 343: Called toolchain-glibc_src_configure
* src_configure.eblit, line 250: Called toolchain-glibc_headers_configure
* src_configure.eblit, line 245: Called die
* The specific snippet of code:
* CC="$(tc-getBUILD_CC)" \
* CFLAGS="-O1 -pipe" \
* CPPFLAGS="-U_FORTIFY_SOURCE" \
* LDFLAGS="" \
* "$@" || die "failed to configure glibc"
*
* If you need support, post the output of `emerge --info '=cross-mips64-unknown-linux-gnu/glibc-9999::gentoo-b3'`,
* the complete build log and the output of `emerge -pqv '=cross-mips64-unknown-linux-gnu/glibc-9999::gentoo-b3'`.
* The complete build log is located at '/var/tmp/portage/cross-mips64-unknown-linux-gnu/glibc-9999/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/cross-mips64-unknown-linux-gnu/glibc-9999/temp/environment'.
* Working directory: '/var/tmp/portage/cross-mips64-unknown-linux-gnu/glibc-9999/work/build-default-mips64-unknown-linux-gnu-headers'
* S: '/var/tmp/portage/cross-mips64-unknown-linux-gnu/glibc-9999/work/glibc-9999'
>>> Failed to emerge cross-mips64-unknown-linux-gnu/glibc-9999, Log file:
>>> '/var/tmp/portage/cross-mips64-unknown-linux-gnu/glibc-9999/temp/build.log'
* Messages for package cross-mips64-unknown-linux-gnu/glibc-9999:
* ERROR: cross-mips64-unknown-linux-gnu/glibc-9999::gentoo-b3 failed (configure phase):
* failed to configure glibc
*
* Call stack:
* ebuild.sh, line 93: Called src_configure
* environment, line 3539: Called eblit-run 'src_configure'
* environment, line 949: Called eblit-glibc-src_configure
* src_configure.eblit, line 258: Called foreach_abi 'toolchain-glibc_src_configure'
* common.eblit, line 343: Called toolchain-glibc_src_configure
* src_configure.eblit, line 250: Called toolchain-glibc_headers_configure
* src_configure.eblit, line 245: Called die
* The specific snippet of code:
* CC="$(tc-getBUILD_CC)" \
* CFLAGS="-O1 -pipe" \
* CPPFLAGS="-U_FORTIFY_SOURCE" \
* LDFLAGS="" \
* "$@" || die "failed to configure glibc"
*
* If you need support, post the output of `emerge --info '=cross-mips64-unknown-linux-gnu/glibc-9999::gentoo-b3'`,
* the complete build log and the output of `emerge -pqv '=cross-mips64-unknown-linux-gnu/glibc-9999::gentoo-b3'`.
* The complete build log is located at '/var/tmp/portage/cross-mips64-unknown-linux-gnu/glibc-9999/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/cross-mips64-unknown-linux-gnu/glibc-9999/temp/environment'.
* Working directory: '/var/tmp/portage/cross-mips64-unknown-linux-gnu/glibc-9999/work/build-default-mips64-unknown-linux-gnu-headers'
* S: '/var/tmp/portage/cross-mips64-unknown-linux-gnu/glibc-9999/work/glibc-9999'
* glibc failed :(
* If you file a bug, please attach the following logfiles:
* /var/log/portage/cross-mips64-unknown-linux-gnu-info.log
* /var/log/portage/cross-mips64-unknown-linux-gnu-glibc-headers.log.xz
* /var/tmp/portage/cross-mips64-unknown-linux-gnu/glibc*/temp/glibc-config.logs.tar.xz
|
checking for sysdeps preconfigure fragments... aarch64 alpha arm hppa i386 m68k microblaze mips configure: error: Unable to determine ABI.
any idea ? |
|
Back to top |
|
|
Basilio n00b
Joined: 04 Feb 2010 Posts: 16
|
Posted: Sun Jun 26, 2016 10:33 am Post subject: |
|
|
Just in case someone stumbles upon "crossdev mips glibc unable to determine ABI":
you need to emerge suitable compiler BEFORE emerging glibc
this is achieved by
Code: |
$ sudo crossdev -t mipsel ... --without-headers
|
this will emerge gcc before glibc-headers |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|