From: Scott Lipcon <slipcon@hops.cs.jhu.edu>
To: Hrvoje Niksic <hniksic@srce.hr>
Cc: Zefram <zefram@dcs.warwick.ac.uk>,
Scott Lipcon <slipcon@insux1.cs.jhu.edu>,
zsh-workers@math.gatech.edu
Subject: Re: Solaris x86?
Date: Fri, 25 Oct 1996 11:48:30 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.3.95.961025114516.9561D-100000@hops.cs.jhu.edu> (raw)
In-Reply-To: <kigzq1b9hjx.fsf@jagor.srce.hr>
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 <hniksic@srce.hr> | Student at FER Zagreb, Croatia
> --------------------------------+--------------------------------
> main(){printf(&unix["\021%six\012\0"],(unix)["have"]+"fun"-0x60);}
>
next prev parent reply other threads:[~1996-10-25 15:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-10-25 15:14 Scott Lipcon
1996-10-25 15:31 ` Zefram
1996-10-25 15:35 ` Scott Lipcon
1996-10-25 15:42 ` Hrvoje Niksic
1996-10-25 15:48 ` Scott Lipcon [this message]
1996-10-25 15:59 ` Hrvoje Niksic
1996-10-26 0:38 ` Scott Lipcon
1996-10-29 13:12 ` Richard Coleman
1996-10-29 13:39 ` Scott Lipcon
1996-11-06 18:55 ` Scott Lipcon
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=Pine.GSO.3.95.961025114516.9561D-100000@hops.cs.jhu.edu \
--to=slipcon@hops.cs.jhu.edu \
--cc=hniksic@srce.hr \
--cc=slipcon@insux1.cs.jhu.edu \
--cc=zefram@dcs.warwick.ac.uk \
--cc=zsh-workers@math.gatech.edu \
/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).