Re: Problems with zsh 3.1.9 and cygwin

["Jonathan Fosburgh" <wotan@xxxxxxxxxxxx>]

----- Original Message -----
From: "Mike Boilen" <mboilen@xxxxxxxxxxxxx>
To: "'Jonathan Fosburgh'" <wotan@xxxxxxxxxxxx>; <zsh-users@xxxxxxxxxxxxxx>
Sent: Thursday, July 20, 2000 12:44 PM
Subject: RE: Problems with zsh 3.1.9 and cygwin


> I appear to have a different problem from you.  I tried removing MMAP
(which
> I think has been undef'd automatically when compiling against cygwin
> anyway), but it didn't help.  I get the exact same error.
>
> Thanks anyway.
>
> Mike
>
> -----Original Message-----
> From: Jonathan Fosburgh [mailto:wotan@xxxxxxxxxxxx]
> Sent: Thursday, July 20, 2000 10:25 AM
> To: Mike Boilen; zsh-users@xxxxxxxxxxxxxx
> Subject: Re: Problems with zsh 3.1.9 and cygwin
>
>
> ----- Original Message -----
> From: "Jonathan Fosburgh" <wotan@xxxxxxxxxxxx>
> To: "Mike Boilen" <mboilen@xxxxxxxxxxxxx>; <zsh-users@xxxxxxxxxxxxxx>
> Sent: Thursday, July 20, 2000 12:23 PM
> Subject: Re: Problems with zsh 3.1.9 and cygwin
>
>
> > ----- Original Message -----
> > From: "Mike Boilen" <mboilen@xxxxxxxxxxxxx>
> > To: <zsh-users@xxxxxxxxxxxxxx>
> > Sent: Thursday, July 20, 2000 11:54 AM
> > Subject: Problems with zsh 3.1.9 and cygwin
> >
> >
> > > I am using windows 2000 server with cygwin 1.1.2 (or whatever the
newest
> > > release is; I downloaded it yesterday).  The code for zsh 3.1.9 builds
> > fine
> > > without modification.  However, when I run it, I get the error:
> > >
> > >       0 [main] zsh 18877 handle_exceptions: Exception:
> > > STATUS_ACCESS_VIOLATION
> > >     913 [main] zsh 18877 stackdump: Dumping stack trace to
> > zsh.exe.stackdump
> > >
> > Go take a look at the mailing list archives, I had the exact same
problems
> > and you may wish to look at my solution. Plus, this message probably
will
> > not make it to the list as we are blacklisted (also in the archives) so
if
> > you would, please repost anything usefull so it gets in there.
> >
> Someone tell me to look at what lists I sending mail to before I send it.
> Everything I was talking about is on the cygwin mailing list, not this
one.
> I have never posted to this one and I do not know if I am blacklisted
here.

I had a request to post what I posted to cygwin here,so here it is.

This is not the account I am subscribed from, that mail server is currently
being blocked for strange reasons, and there is nothing we can do about it.
:( 

There was a recent thread on here regarding getting ksh and zsh to compile and run. I also had a thread running a few weeks ago detailing my problems. I have finally solved those and believe I know the problem the other person is having. In brief, I have been able to compile zsh-3.1.* but running it gave me STATUS_ACCESS_VIOLATION errors. Fixes in the archives didn't work. After much working through gdb, I determined the problem lay somewhere in termcap or terminfo, so I performed a complete upgrade of cygwin and started over configuring and compileing both zsh-3.1.7 and 3.1.9. I then ran into problems with /bin/sh. Apparently I originally did not have ash in my installation and so had created a link for /bin/sh. This probably was a hard link to /bin/bash, but I am not sure anymore. After removing that, my configure scripts started working again. During the compile portion, it died in both builds with problems in libcurses. I upgraded to the most recent curses I could find (nc!
urses-5) and tried again. This time it compiled fine and I can run both builds. For the benefit of the person who started the recent zsh thread, I believe you had some kind of problem with undefined symbols having puts or something like that? If so, you might upgrade your curses libraries, or possibly the termcap package in the base system.


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@xxxxxxxxxxxxxxxxxxxxx