zsh-users
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Paul Lew <paullew@cisco.com>, zsh-users@sunsite.auc.dk
Subject: Re: architecture independent wordcode files (.zwc)
Date: Sun, 13 May 2001 00:43:37 +0000	[thread overview]
Message-ID: <1010513004337.ZM7197@candle.brasslantern.com> (raw)
In-Reply-To: <15101.39024.899564.120545@paullew-ultra.cisco.com>

On May 12,  1:09pm, Paul Lew wrote:
} Subject: architecture independent wordcode files (.zwc)
}
}     Right now we have .zshenv compiled into .zshenv.zwc and .zshrc
}     compiled into .zshrc.zwc on the solaris machine. However, this
}     does not work for the Linux. I got zsh cored when reading the .zwc
}     file for the wrong architecture.
}
}     The emacs .elc files works on different endian machines. Any plan
}     to do the same with .zwc files?

It's supposed to work -- the zcompile doc says:

              The created file always contains  two  versions  of
              the  compiled  format,  one for big-endian machines
              and one for small-endian machines.  The  upshot  of
              this  is that the compiled file is machine indepen-
              dent and if it is read or mapped, only one half  of
              the file is actually used (and mapped).

If possible, please send a stack trace from your core dump to zsh-workers.
Thanks.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


      reply	other threads:[~2001-05-13  0:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-12 20:09 Paul Lew
2001-05-13  0:43 ` Bart Schaefer [this message]

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=1010513004337.ZM7197@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=paullew@cisco.com \
    --cc=zsh-users@sunsite.auc.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).