From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2885 invoked from network); 19 Jan 2004 10:57:24 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 19 Jan 2004 10:57:24 -0000 Received: (qmail 29776 invoked by alias); 19 Jan 2004 10:57:10 -0000 Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 7009 Received: (qmail 29738 invoked from network); 19 Jan 2004 10:57:10 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 19 Jan 2004 10:57:10 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [62.189.58.19] by sunsite.dk (MessageWall 1.0.8) with SMTP; 19 Jan 2004 10:57:10 -0000 Received: from MAILSWEEPER01.csr.com (mailhost1.csr.com [62.189.183.235]) by lhuumrelay3.lnd.ops.eu.uu.net (8.11.0/8.11.0) with ESMTP id i0JAv9v28739 for ; Mon, 19 Jan 2004 10:57:09 GMT Received: from EXCHANGE02.csr.com (unverified) by MAILSWEEPER01.csr.com (Content Technologies SMTPRS 4.3.12) with ESMTP id ; Mon, 19 Jan 2004 10:55:57 +0000 Received: from csr.com ([192.168.144.127]) by EXCHANGE02.csr.com with Microsoft SMTPSVC(5.0.2195.5329); Mon, 19 Jan 2004 10:48:02 +0000 To: chuckr cc: zsh-users@sunsite.dk Subject: Re: cross-compiling In-reply-to: "chuckr"'s message of "Sun, 18 Jan 2004 14:07:50 EST." <400AD986.9070708@chuckr.org> Date: Mon, 19 Jan 2004 10:45:54 +0000 Message-ID: <8419.1074509154@csr.com> From: Peter Stephenson X-OriginalArrivalTime: 19 Jan 2004 10:48:02.0586 (UTC) FILETIME=[B63547A0:01C3DE79] chuckr wrote: > I have a Linux PDA, a Sharp Zaurus running Linux 2.4.20, and I like to > cross-compile my applications on my main Intel Linux box sitting next to > it, connected via usb networking. Your configure script does nicely > realize that it's doing cross-compiling, and it even goes an extra step, > if I don't give it any of the --target, --build, or --host flags, it > gets it from the fact that the gcc in the path isn't making intel code. Unfortunately that's a bit of a red herring (and it should really say so in the INSTALL file). The configure basics support cross-compiling, but many zsh tests actually need to run on the system in question to find out how the features work. There are numerous cases where simply compiling isn't good enough to work out what's going on. This could be fixed along the lines of making some assumptions for tests when cross-compiling, and telling the user what might need fixing. Possibly some places where we need to search header files for information (e.g. signal names) need fixing too. That's already a sizeable chunk of work and can only be done by someone who is set up to use it. I can't see it happening unless somebody volunteers, I'm afraid. -- Peter Stephenson Software Engineer CSR Ltd., Science Park, Milton Road, Cambridge, CB4 0WH, UK Tel: +44 (0)1223 692070 ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **********************************************************************