From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24484 invoked from network); 19 Sep 2002 15:19:33 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 19 Sep 2002 15:19:33 -0000 Received: (qmail 14927 invoked by alias); 19 Sep 2002 15:19:26 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 17704 Received: (qmail 14916 invoked from network); 19 Sep 2002 15:19:25 -0000 To: "David Gómez" , zsh-workers@sunsite.dk (Zsh hackers list) Subject: Re: Using zsh in gcc compilation In-reply-to: ""David Gómez""'s message of "Thu, 19 Sep 2002 17:07:20 +0200." <20020919150720.GA14948@fargo> Date: Thu, 19 Sep 2002 16:18:52 +0100 Message-ID: <16798.1032448732@csr.com> From: Peter Stephenson "David Gómez" wrote: > 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. That's extremely plausible --- `on' occurs very frequently in $options. But that implies the zsh/parameter module is loaded. It shouldn't be doing this by default in sh emulation. You might want to check what startup scripts are being executed for sh mode (running with the option -x should show this). I'm not sure if there's a general way round this. We would look to move towards separate namespaces, but that needs someone to do the work. It's a shame we didn't initially use names like zsh_options instead. -- Peter Stephenson Software Engineer CSR Ltd., Science Park, Milton Road, Cambridge, CB4 0WH, UK Tel: +44 (0)1223 692070 ********************************************************************** The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. **********************************************************************