zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list),
	"David Gómez" <david@pleyades.net>
Subject: Re: Using zsh in gcc compilation
Date: Thu, 19 Sep 2002 13:15:07 +0100	[thread overview]
Message-ID: <1338.1032437707@csr.com> (raw)
In-Reply-To: ""David Gómez""'s message of "Thu, 19 Sep 2002 13:30:48 +0200." <20020919113048.GA17371@fargo>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1801 bytes --]

"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 <pws@csr.com>                  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.
**********************************************************************


  reply	other threads:[~2002-09-19 12:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-19  9:52 David Gómez
2002-09-19 10:07 ` Peter Stephenson
2002-09-19 11:19   ` Peter Stephenson
2002-09-19 11:30     ` David Gómez
2002-09-19 12:15       ` Peter Stephenson [this message]
2002-09-19 12:43         ` David Gómez
2002-09-19 13:19           ` Peter Stephenson
2002-09-19 11:16 David Gómez
2002-09-19 15:12 David Gómez
2002-09-19 15:54 ` Bart Schaefer
2002-09-19 16:04   ` David Gómez
     [not found] <20020919150720.GA14948@fargo>
2002-09-19 15:18 ` Peter Stephenson
2002-09-19 15:37   ` David Gómez
2002-09-19 16:03     ` Bart Schaefer
2002-09-19 16:08       ` David Gómez
2002-09-19 16:15   ` DervishD

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1338.1032437707@csr.com \
    --to=pws@csr.com \
    --cc=david@pleyades.net \
    --cc=zsh-workers@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).