From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22055 invoked from network); 19 Sep 2002 12:15:52 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 19 Sep 2002 12:15:52 -0000 Received: (qmail 6961 invoked by alias); 19 Sep 2002 12:15:38 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 17699 Received: (qmail 6945 invoked from network); 19 Sep 2002 12:15:36 -0000 To: zsh-workers@sunsite.dk (Zsh hackers list), "David Gómez" Subject: Re: Using zsh in gcc compilation In-reply-to: ""David Gómez""'s message of "Thu, 19 Sep 2002 13:30:48 +0200." <20020919113048.GA17371@fargo> Date: Thu, 19 Sep 2002 13:15:07 +0100 Message-ID: <1338.1032437707@csr.com> From: Peter Stephenson "David Gómez" wrote: > ml has two values, '.;' and 'on;@on'. First is substituted to nothing and the > second one to '-on'. What I don't know is where MULTILIB is created and why h > as > this two values which seems so strange. Maybe we're getting closer after all... can you run build_tooldir=/usr/local/sparc-sun-solaris2.6 ./xgcc -B./ -B$build_tooldir/bin/ -isystem $build_tooldir/include \ -isystem $build_tooldir/sys-include --print-multi-lib in the gcc directory and see what that gives? This should be what's being passed down as MULTILIBS. You're build_tooldir will be different --- it's usually just the path to the binaries with bin stripped, followed by the configuration name. I don't know if it's relevant at this point, possibly not. (Possibly GCC_FOR_TARGET is different at this point; that's everything from ./xgcc up to sys-include, in which case this might not be the right argument. If you can see a value of GCC_FOR_TARGET being passed down into the system at that point, that's the one to use.) -- 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. **********************************************************************