From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22857 invoked by alias); 30 Jan 2012 18:38:57 -0000 Received: (qmail 22847 invoked by uid 22791); 30 Jan 2012 18:38:56 -0000 X-SWARE-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,TW_SG X-Spam-Check-By: sourceware.org Received: from 5.mo6.mail-out.ovh.net (HELO mo6.mail-out.ovh.net) (46.105.54.31) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 30 Jan 2012 18:38:42 +0000 Received: from mail325.ha.ovh.net (b7.ovh.net [213.186.33.57]) by mo6.mail-out.ovh.net (Postfix) with SMTP id CF7B8FF84BA for ; Mon, 30 Jan 2012 19:40:34 +0100 (CET) Received: from b0.ovh.net (HELO queueout) (213.186.33.50) by b0.ovh.net with SMTP; 30 Jan 2012 18:38:40 -0000 Received: from ns0.ovh.net (HELO webmail.ovh.com) (213.186.33.20) by ns0.ovh.net with SMTP; 30 Jan 2012 18:38:40 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Date: Mon, 30 Jan 2012 18:38:00 -0000 From: To: Khem Raj Cc: X-Ovh-Mailout: 178.32.228.6 (mo6.mail-out.ovh.net) Subject: Re: using crossgcc with old glibc In-Reply-To: References: Message-ID: X-Sender: music@linuxconsole.org User-Agent: RoundCube Webmail/0.4 X-Ovh-Tracer-Id: 16406613442793741032 X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: -85 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrfeegtddrvdekucetggdotefuucfrrhhofhhilhgvmecuqfggjfenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnegfrhhlucfvnfffucdludehmdenucfhrhhomhepoehmuhhsihgtsehlihhnuhigtghonhhsohhlvgdrohhrgheqnecuffhomhgrihhnpehsohhurhgtvgifrghrvgdrohhrghenucfjughrpeggtgfgfffhvffujghfkfigfgesthejjhdttderje X-IsSubscribed: yes 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: 2012-01/txt/msg00090.txt.bz2 I tried it with CT_BINUTILS_EXTRA_CONFIG_ARRAY="LDFLAGS=-all-static" and CT_CC_EXTRA_CONFIG_ARRAY="LDFLAGS=-static" into crosstool-ng config but if failed when building gcc with a lot of g++ undefined reference errors I will build my toolchain with the oldest glibc, then I could export it on every computer. Thanks. On Sat, 28 Jan 2012 14:37:45 -0800, Khem Raj wrote: > On Sat, Jan 28, 2012 at 1:24 PM, wrote: >> >> is there a way to use my toolchain on this older system ? > > build statically linked toolchain > > -- > For unsubscribe information see http://sourceware.org/lists.html#faq -- For unsubscribe information see http://sourceware.org/lists.html#faq