From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19670 invoked from network); 17 Nov 1998 09:32:03 -0000 Received: from math.gatech.edu (list@130.207.146.50) by ns1.primenet.com.au with SMTP; 17 Nov 1998 09:32:03 -0000 Received: (from list@localhost) by math.gatech.edu (8.9.1/8.9.1) id EAA11976; Tue, 17 Nov 1998 04:30:37 -0500 (EST) Resent-Date: Tue, 17 Nov 1998 04:30:37 -0500 (EST) Date: Tue, 17 Nov 1998 10:28:32 +0100 (MET) Message-Id: <199811170928.KAA11788@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@math.gatech.edu In-reply-to: "Andrej Borsenkow"'s message of Tue, 17 Nov 1998 11:37:39 +0300 Subject: Re: ZSH on 64 bit systems Resent-Message-ID: <"2_3uH2.0.3x2.z8KKs"@math> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/4660 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu Andrej Borsenkow wrote: > I plan update my server to new 64 bit version of OS, and am interested in > any experience with running ZSH on such sort of systems. Some background > information: > > ... I've been using zsh on a DEC Alpha for quite some time now without any problems (after some fixes in previous zsh versions that have already made it into the baseline). Alphas use the LP64 convention which seems to become standard for 64Bit systems (longs and pointers are 64 bit, ints are 32 bit). This reminds me... One note for Zefram: when trying to compile a zsh with dynamic loading on this Digital Unix 4.0d I had to use gcc as the linker. Without it the binary couldn't be linked. With it I got heaps of warnings about unresolved symbols but the binary worked fine. The warnings could have been avoided by using `-Xlinker -z -Xlinker defs', I think. Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de