Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: architecture independent wordcode files (.zwc)
- X-seq: zsh-users 3877
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: Paul Lew <paullew@xxxxxxxxx>, zsh-users@xxxxxxxxxxxxxx
- Subject: Re: architecture independent wordcode files (.zwc)
- Date: Sun, 13 May 2001 00:43:37 +0000
- In-reply-to: <15101.39024.899564.120545@xxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <15101.39024.899564.120545@xxxxxxxxxxxxxxxxxxxxxxx>
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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author