From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12383 invoked by alias); 6 Sep 2009 11:01:45 -0000 Received: (qmail 11921 invoked by uid 22791); 6 Sep 2009 11:01:43 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from vmlinux.org (HELO vmlinux.org) (193.41.214.66) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 06 Sep 2009 11:01:26 +0000 Received: from localhost (localhost [127.0.0.1]) by vmlinux.org (Postfix) with ESMTP id 785C51DDA27E for ; Sun, 6 Sep 2009 13:01:28 +0200 (CEST) Received: from vmlinux.org ([127.0.0.1]) by localhost (vmlinux.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B6YU6lQpiZtc for ; Sun, 6 Sep 2009 13:01:25 +0200 (CEST) Received: from [192.168.1.124] (90-224-113-214-no111.tbcn.telia.com [90.224.113.214]) by vmlinux.org (Postfix) with ESMTPSA id A6D671DDA27D for ; Sun, 6 Sep 2009 13:01:25 +0200 (CEST) Message-ID: <4AA39681.6040902@vmlinux.org> Date: Sun, 06 Sep 2009 11:01:00 -0000 From: Joachim Nilsson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.1) Gecko/20090715 Lightning/1.0pre Thunderbird/3.0b3 MIME-Version: 1.0 To: crossgcc@sourceware.org Subject: croostool-ng: GCC 4.4.1 Working! Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 X-SW-Source: 2009-09/txt/msg00018.txt.bz2 Hi everybody! I managed to get a working armeb-unknown-linux-uclibc toolchain using GCC v4.4.1 today. Yay! :) We have an Intel IXP465 based CPU board at work that I'm currently targeting with my work, but we also have an i.MX27 and sonn possibly Arm11 based ones as well. So I'll be working with crosstool-ng quite a bit during the fall and winter months. Anyway, I used the latest head (correct hg terminology?) of crosstool-ng and added the 4.4.1 GCC patches from buildroot: http://git.buildroot.net/buildroot/tree/toolchain/gcc/4.4.1 That's about it. How would I proceed in contributing these patches, inline attachments, publish a Mercurial branch, or is it sufficient with the above pointer? Just curious for any future contributions really. Regards /Jocke -- For unsubscribe information see http://sourceware.org/lists.html#faq