From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: zsh-workers-request@euclid.skiles.gatech.edu Received: from euclid.skiles.gatech.edu (list@euclid.skiles.gatech.edu [130.207.146.50]) by coral.primenet.com.au (8.7.6/8.7.3) with ESMTP id BAA19197 for ; Sat, 26 Oct 1996 01:52:09 +1000 (EST) Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id LAA24706; Fri, 25 Oct 1996 11:49:34 -0400 (EDT) Resent-Date: Fri, 25 Oct 1996 11:49:34 -0400 (EDT) Date: Fri, 25 Oct 1996 11:48:30 -0400 (EDT) From: Scott Lipcon To: Hrvoje Niksic cc: Zefram , Scott Lipcon , zsh-workers@math.gatech.edu Subject: Re: Solaris x86? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"YiYdY1.0.y16.D6ESo"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/2279 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu On 25 Oct 1996, Hrvoje Niksic wrote: > > > > Neither seems to work. Which library was the one that caused problems? > > This may be a stupid question, but are you really using zsh? This > looks much like tcsh prompt and tcsh behaviour. I'm using tcsh, to compile zsh, so I don't have to use tcsh anymore :-) More specific information: Its having a bunch of "assignment makes pointer from integer without a cast" warnings, throughout the source. Then, it totally dies when it gets to signals.c I tried fiddling with the #define's in config.h that have to do with signals - I guess configure decided that Solaris had POSIX signal handling. I tried it with the SysV signal handling, and it got about 200 lines farther in signals.c before stopping with more errors. Is it possible that Solaris x86 has really weird signal handling? Thanks, Scott > > -- > Hrvoje Niksic | Student at FER Zagreb, Croatia > --------------------------------+-------------------------------- > main(){printf(&unix["\021%six\012\0"],(unix)["have"]+"fun"-0x60);} >