zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: "David Gómez" <david@pleyades.net>, zsh-workers@sunsite.dk
Subject: Re: Using zsh in gcc compilation
Date: Thu, 19 Sep 2002 14:19:32 +0100	[thread overview]
Message-ID: <3468.1032441572@csr.com> (raw)
In-Reply-To: ""David Gómez""'s message of "Thu, 19 Sep 2002 14:43:18 +0200." <20020919124318.GA17624@fargo>

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

"David Gómez" wrote:
> './xgcc --print-multi-lib' gives the output '.;' and
> './xgcc -B./ --print-multi-lib' gives '.;' 'on;@on'
> 
> but executing this command with bash produces the same output, so i'm not
> sure if we're in the right path to tracking down the error... 

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

  sh ../../gcc/genmultilib \
  "msoft-float mcpu=v8" "soft v8" \
  "msoft-float=mno-fpu mcpu?v8=mv8" \
  "" ""  ""

with both sh and `ARGV0=sh zsh' here (SunOS 2.6 --- actually the real
compilation system is using a simpler set of options, but that should
just make a problem less likely), and they gave the same output, but
obviously this depends on the input --- if you can find out the
appropriate flags, which seem to be fairly well hidden, you could try
this.  Make is actually using

	  $(SHELL) $(srcdir)/genmultilib \
	    "$(MULTILIB_OPTIONS)" \
	    "$(MULTILIB_DIRNAMES)" \
	    "$(MULTILIB_MATCHES)" \
	    "$(MULTILIB_EXCEPTIONS)" \
	    "$(MULTILIB_EXTRA_OPTS)" \
	    "$(MULTILIB_EXCLUSIONS)" \
	    > tmp-mlib.h; \

You are using a recent version of zsh...?

-- 
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 13:20 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
2002-09-19 12:43         ` David Gómez
2002-09-19 13:19           ` Peter Stephenson [this message]
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=3468.1032441572@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).