From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22978 invoked by alias); 14 Nov 2003 08:13:17 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 22963 invoked from network); 14 Nov 2003 08:13:16 -0000 Received: from unknown (HELO web41105.mail.yahoo.com) (66.218.93.21) by sources.redhat.com with SMTP; 14 Nov 2003 08:13:16 -0000 Message-ID: <20031114081315.82002.qmail@web41105.mail.yahoo.com> Received: from [128.12.51.83] by web41105.mail.yahoo.com via HTTP; Fri, 14 Nov 2003 00:13:15 PST Date: Fri, 14 Nov 2003 08:13:00 -0000 From: Dara Hazeghi Subject: Re: gcc323 + specific glibc To: csc@cadence.com Cc: gcc-help@gcc.gnu.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-11/txt/msg00192.txt.bz2 Hello, one slightly hackish approach is to lie to gcc, and make it think that it is cross-compiling. 3.2.3 doesn't support sysroot, so it's not surprising that should fail. Probably if you do --target=i386-redhat-linux (or some such), configure will be stupid enough to think it's cross-compiling, and you can use --with-headers= and --with-libs= as you tried previously (this worked for me a while back, when targeting libc1). Note that you'll need to edit the libc.so from the old libc image (it's a text file, but the paths in it will probably be wrong) to get a fully functional 'cross' compiler. Cheers, Dara __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree