From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24189 invoked from network); 19 Sep 2002 15:14:01 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 19 Sep 2002 15:14:01 -0000 Received: (qmail 13794 invoked by alias); 19 Sep 2002 15:13:47 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 17703 Received: (qmail 13775 invoked from network); 19 Sep 2002 15:13:45 -0000 From: "David Gómez" Date: Thu, 19 Sep 2002 17:12:57 +0200 To: zsh-workers@sunsite.dk Subject: Re: Using zsh in gcc compilation Message-ID: <20020919151257.GA27445@fargo> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.3.28i On Thu, Sep 19, 2002 at 02:19:32PM +0100, Peter Stephenson wrote: > It may be in the generation of multilib.h, in that case, because > genmultilib in the gcc source directory looks pretty hair-raising. I > ran it as... Yes, you're right. And i think i now why. The output of genmultilib is different when executed by zsh or bash. It seems genmultilib use the $options variable to store the first positional parameter to genmultilib, and i'm sure you've guessed it, $options is already defined by zsh. I'm going to test multilib now with a different name instead of options, but i'm pretty sure this it's what is causing the problem. -- David Gómez "The question of whether computers can think is just like the question of whether submarines can swim." -- Edsger W. Dijkstra