zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: River Tarnell <river@wikimedia.org>,
	"Zsh Hackers' List" <zsh-workers@sunsite.dk>
Subject: Re: [PATCH] 4.3.5 build fails on SunOS 4.1.4
Date: Mon, 3 Mar 2008 12:36:22 +0000	[thread overview]
Message-ID: <20080303123622.169e55c8@news01> (raw)
In-Reply-To: <1282467763.20080303045815@wikimedia.org>

On Mon, 3 Mar 2008 04:58:15 +0000
River Tarnell <river@wikimedia.org> wrote:
> this platform doesn't provide strtoul(), and zsh has no compat.c
> replacement.  the patch (attached) provides one from NetBSD sources
> (which i believe has a liberal enough license to be included in zsh).

Right, and you've even included the licence, so I've committed it as it is.
Thanks.

> there are two remaining problems, but i have no idea where to start
> on either of them:
> 
>  + unless compiled with --disable-dynamic, any attempt to use
>    completion-related features crashes the shell with 'Undefined
>    symbol: _incompfunc'

I think the answer here is probably --disable-dynamic.  It's going back a
while, but I have a suspicion dynamic linking has always been problematic
on SunOS 4.  It might be fixable if anyone thought it worth while and had
the time and facilities.

For the specific problem, on some older systems an underscore needed to be
added by hand to entry points when fetching them with dlsym().  It looks
like this is some variant of that problem (although dlsym() isn't directly
involved).  Again, it's going back a bit and I'm not sure how this was
supposed to pan out.

>  + job control doesn't work properly.  while typing ^Z in 'vi'
>    works fine, in 'vim', the program immediately resumes, rather
>    than returning to the shell.  both work fine with the system
>    'csh'.

Job control definitely worked once on 4.1.x because I used to use it all
the time about 15(!) years ago, although I think that was in the age before
vim.  It's likely to need some poking around with a suitable system, unless
it awakes some memory of Bart's.

It might be worth trying "ttyctl -f" before calling vim the first time in
case it's monkeying with terminal settings.  I don't hold out much hope,
but it's at least a very quick test.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070


  reply	other threads:[~2008-03-03 12:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-03  4:58 River Tarnell
2008-03-03 12:36 ` Peter Stephenson [this message]
2008-03-03 17:31   ` Vin Shelton

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=20080303123622.169e55c8@news01 \
    --to=pws@csr.com \
    --cc=river@wikimedia.org \
    --cc=zsh-workers@sunsite.dk \
    /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).