From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 100195 invoked by alias); 15 May 2015 19:02:41 -0000 Mailing-List: contact crossgcc-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: crossgcc-owner@sourceware.org Received: (qmail 100180 invoked by uid 89); 15 May 2015 19:02:40 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-ie0-f179.google.com Received: from mail-ie0-f179.google.com (HELO mail-ie0-f179.google.com) (209.85.223.179) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Fri, 15 May 2015 19:02:38 +0000 Received: by ieczm2 with SMTP id zm2so53413198iec.1 for ; Fri, 15 May 2015 12:02:36 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.107.137.143 with SMTP id t15mr15156109ioi.16.1431716521386; Fri, 15 May 2015 12:02:01 -0700 (PDT) Received: by 10.50.107.42 with HTTP; Fri, 15 May 2015 12:02:01 -0700 (PDT) In-Reply-To: References: <20150515204017.2eb99e8c@free-electrons.com> Date: Fri, 15 May 2015 19:02:00 -0000 Message-ID: Subject: Re: [crosstool-ng] Pre-built toolchains for testing in Buildroot From: Bryan Hundven To: Reinoud Koornstra Cc: Thomas Petazzoni , "crossgcc@sourceware.org" , "Yann E. MORIN" Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2015-05/txt/msg00016.txt.bz2 Reinoud, On Fri, May 15, 2015 at 11:53 AM, Reinoud Koornstra wrote: > Hi Thomas and Bryan, Please don't top post. ;) > > You said: "- The MIPS uClibc toolchain fails to build gdb, weston and > civetweb (I > believe due to uClibc issues)" > > I did experience this issue as well with gcc 4.9.2 > I filed it earlier and Bryan is aware too, there just isn't a fix yet. > uClibc with gcc 4.9.2 does build for arm. Correct. But this is only with SSP enabled, iirc. > With gcc 5.1.0 uclibc doesn't build and any platform. > Hence, gcc 4.9.2 and gcc 5.1.0 do not work with uclibc on all > platforms even though you can have this config. I haven't validated "Any platform". > I don't agree on moving away from uclibc all together. > Buildroot supports uclibc AND uclibc-ng. > I think crosstools-ng needs to do the same. > I'm not sure whether there'll ever be another uclibc release, but the > current git tree surely has way more added features and their mailing > list is very active. I don't have a horse in this race. Which ever is being more actively maintained and released (note, uclibc has not made a release in years!) is what crosstool-ng will (or wont) use. > At this moment uclibc-ng seems to make more sense, because it keeps up > with the current changes in uclibc and maintains their own branch and > releases new versions. > It surely works for me. > Thanks, > > Reinoud. > > On Fri, May 15, 2015 at 12:40 PM, Thomas Petazzoni > wrote: >> Hello, >> >> Buildroot is an embedded Linux build system, which is capable of using >> external pre-built cross-compilation toolchains. Crosstool-NG >> toolchains are supported through this mechanism. >> >> I while back, Yann E. Morin, the former maintainer of Crosstool-NG, >> created some pre-built toolchains that the Buildroot project uses to >> run some test builds against Crosstool-NG toolchains. This ensures that >> people building toolchains with Crosstool-NG will be able to use them >> with Buildroot. >> >> Those toolchains are available here: >> >> http://autobuild.buildroot.org/toolchains/tarballs/armv5-ctng-linux-gnueabi.tar.xz >> http://autobuild.buildroot.org/toolchains/tarballs/armv6-ctng-linux-uclibcgnueabi.tar.xz >> http://autobuild.buildroot.org/toolchains/tarballs/armv7-ctng-linux-gnueabihf.tar.xz >> http://autobuild.buildroot.org/toolchains/tarballs/i486-ctng-linux-uclibc.tar.xz >> http://autobuild.buildroot.org/toolchains/tarballs/i686-ctng-linux-gnu.tar.xz >> http://autobuild.buildroot.org/toolchains/tarballs/mips64el-ctng_n32-linux-gnu.tar.xz >> http://autobuild.buildroot.org/toolchains/tarballs/mips64el-ctng_n64-linux-gnu.tar.xz >> http://autobuild.buildroot.org/toolchains/tarballs/mipsel-ctng-linux-uclibc.tar.xz >> http://autobuild.buildroot.org/toolchains/tarballs/powerpc-ctng-linux-uclibc.tar.xz >> http://autobuild.buildroot.org/toolchains/tarballs/powerpc-ctng_e500v2-linux-gnuspe.tar.xz >> http://autobuild.buildroot.org/toolchains/tarballs/powerpc64-ctng-linux-gnu.tar.xz >> http://autobuild.buildroot.org/toolchains/tarballs/x86_64-ctng_locales-linux-gnu.tar.xz >> >> However, those toolchains are now one year old, and some of them have >> some issues: >> >> - The uClibc toolchains were built without IPv6 support, and Buildroot >> now requires IPv6 support to be present. Due to this, we had to >> disable the use of all uClibc toolchains from the above list. >> >> See >> http://git.buildroot.net/buildroot-test/commit/?id=e11a3af5aa56ba7f44aca8e615e5b2222d860dd6 >> >> - The ARM toolchains are affected by gcc bug PR58854, causing >> lttng-tools to fail building. >> >> - The PowerPC toolchains are affected by gcc bug PR60155, causing a >> build problem with SDL and mpeg2. >> >> - The MIPS64 toolchain uses a too old glibc version, which lacks >> SYS_getdents64, causing a build failure of Python 3. >> >> - The MIPS uClibc toolchain fails to build gdb, weston and civetweb (I >> believe due to uClibc issues) >> >> Is there someone in the Crosstool-NG community interested in working >> with the Buildroot community to provide more up-to-date pre-built >> Crosstool-NG toolchains, and fixing the above issues? >> >> Also, I would strongly advise Crosstool-NG to move away from uClibc, >> and use uClibc-ng instead. This project is much more lively, and has >> tons of fixes that have never been in a uClibc stable release. >> >> Best regards, >> >> Thomas Petazzoni >> -- >> Thomas Petazzoni, CTO, Free Electrons >> Embedded Linux, Kernel and Android engineering >> http://free-electrons.com >> >> -- >> For unsubscribe information see http://sourceware.org/lists.html#faq >> > > -- > For unsubscribe information see http://sourceware.org/lists.html#faq > -Bryan -- For unsubscribe information see http://sourceware.org/lists.html#faq