zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: termcap moodule problem on Cygwin
Date: Mon, 29 Jan 2001 15:10:17 +0000	[thread overview]
Message-ID: <Tc0a8890c516786f052@mailsweeper01.cambridgesiliconradio.com> (raw)
In-Reply-To: Your message of "Mon, 29 Jan 2001 17:55:53 +0300." <001601c08a03$93fb5170$21c9ca95@mow.siemens.ru>

> Cygwin has only static libtermcap. It gets linked twice - into main zsh
> (libzsh to be sure) where term is (re-)initalized and into termcap.dll where
> bin_echotc is defined. Only first one calls tgetent() so every call to `echot
> c
> cap' crashes somewhere in termcap.

It must surely be possible to make sure it is linked in once only, which
would be the right thing to do.  If the worst comes to the worst, get
configure to detect a static termcap and only link it into the main module.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
Cambridge Silicon Radio, Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, UK                          Tel: +44 (0)1223 392070


  reply	other threads:[~2001-01-29 15:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-29 14:55 Andrej Borsenkow
2001-01-29 15:10 ` Peter Stephenson [this message]
2001-01-30  8:25   ` Andrej Borsenkow
2001-01-30 10:34     ` Peter Stephenson
2001-01-31  8:50       ` Somebody with gcc knowledge here? (Was: termcap moodule problem on Cygwin ) Andrej Borsenkow
2001-01-31 10:37       ` PATCH: RE: termcap moodule problem on Cygwin Andrej Borsenkow
2001-01-31 11:30         ` Peter Stephenson
2001-01-31 12:42           ` Andrej Borsenkow
2001-01-31 13:49             ` Peter Stephenson
2001-02-05 15:31               ` Andrej Borsenkow
2001-02-13 14:36                 ` Andrej Borsenkow
2001-01-29 16:48 ` Zefram

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=Tc0a8890c516786f052@mailsweeper01.cambridgesiliconradio.com \
    --to=pws@csr.com \
    --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).