Summary: | cross-mips*/glibc: building sys-libs/glibc headers-only fails for mips targets | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Stuart Longland (RETIRED) <redhatter> |
Component: | [OLD] Development | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | mips |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | MIPS | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Failed glibc build for CTARGET=mipsel-unknown-linux-gnu CHOST=i686-pc-linux-gnu |
Description
Stuart Longland (RETIRED)
![]() Created attachment 235139 [details]
Failed glibc build for CTARGET=mipsel-unknown-linux-gnu CHOST=i686-pc-linux-gnu
this is correct behavior. you need the C library headers before you can build the first gcc. chances are, mips is doing something specific in glibc with their headers. Ahh okay, I recall we used to build just a straight gcc with no libs as the "stage 1" gcc, and that could be built without headers and would work for building the kernel too. I'm just trying a run specifying --without-headers. I don't recall having issues building a toolchain on my Yeeloong for arm-926ejs-linux-gnueabi (target; Ka-Ro TX27/Freescale i.MX27) like this, so we could very well be looking at a MIPS headers issue. I'm not sure where to start looking however. duron ~ # crossdev -t mipsel-unknown-linux-gnu --without-headers ----------------------------------------------------------------------------------------------------------------- * crossdev version: @CDEVPV@ * Host Portage ARCH: x86 * Target Portage ARCH: mips * Target System: mipsel-unknown-linux-gnu * Stage: 4 (C/C++ compiler) * binutils: binutils-[latest] * gcc: gcc-[latest] * headers: linux-headers-[latest] * libc: glibc-[latest] * PORTDIR_OVERLAY: /home/portage/overlays/local * PORT_LOGDIR: /var/log/portage * PKGDIR: /home/portage/packages/ia32/duron//cross/mipsel-unknown-linux-gnu * PORTAGE_TMPDIR: /tmp/cross/mipsel-unknown-linux-gnu _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ * Forcing the latest versions of {binutils,gcc}-config/gnuconfig ... [ ok ] * Log: /var/log/portage/cross-mipsel-unknown-linux-gnu-binutils.log * Emerging cross-binutils ... [ ok ] * Log: /var/log/portage/cross-mipsel-unknown-linux-gnu-gcc-stage1.log * Emerging cross-gcc-stage1 ... [ ok ] * Log: /var/log/portage/cross-mipsel-unknown-linux-gnu-linux-headers.log * Emerging cross-linux-headers ... [ ok ] * Log: /var/log/portage/cross-mipsel-unknown-linux-gnu-glibc.log * Emerging cross-glibc ... [ ok ] * Log: /var/log/portage/cross-mipsel-unknown-linux-gnu-gcc-stage2.log * Emerging cross-gcc-stage2 ... [ ok ] duron ~ # mipsel-unknown-linux-gnu-gcc --version mipsel-unknown-linux-gnu-gcc (Gentoo 4.4.4 p1.0) 4.4.4 Copyright (C) 2010 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. duron ~ # mipsel-unknown-linux-gnu-as --version GNU assembler (GNU Binutils) 2.20.1.20100303 Copyright 2009 Free Software Foundation, Inc. This program is free software; you may redistribute it under the terms of the GNU General Public License version 3 or later. This program has absolutely no warranty. This assembler was configured for a target of `mipsel-unknown-linux-gnu'. duron ~ # ^^ Looking at the above, I'd say this is a viable work-around until we can get the headers issue sorted out. Now to sort out a canadian-cross toolchain, and to get my stages updated. *** This bug has been marked as a duplicate of bug 235551 *** |