zsh-workers
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: PATCH: omit completion tests if no zpty
Date: Fri, 12 Mar 2004 17:17:52 +0100	[thread overview]
Message-ID: <1430.1079108272@trentino.logica.co.uk> (raw)
In-Reply-To: <18997.1079032558@csr.com>

Peter wrote:
> This should prevent the lack of zpty causing unnecessary grief, although
> obviously it doesn't help if zpty is present but not working.

Note that we're now slightly inconsistent on wording for warnings about
missing modules:
./V01zmodload.ztst: starting.
Warning: zsh/example not linked: not checking autoloading
./V01zmodload.ztst: all tests successful.
./Y01completion.ztst: starting.
./Y01completion.ztst: skipped (the zsh/zpty module is not available)

though I appreciate that in V01, it is only some tests being skipped.

> I will try and get 4.2.0-pre-4 out when Oliver has finished off HP-UX
> for the time being.  I imagine we will have to do without zpty there.

With gcc, dynamic modules were being disabled. Hence, it couldn't load
the modules. The problem was it was trying to use the linker options from
the native compiler. With the patch below, gcc now builds a dynamic zsh.

> It would be nice at least to have some way of detecting if it doesn't
> work.  (Does it have /dev/ptmx?  Is it defining __SVR4?  If so, it might
> be getting into problems fiddling with STREAMS, which is the problem
> we had with the first go using /dev/ptmx on Linux.  If that looks
> likely, restricting the STREAMS stuff to Solaris is probably the best
> bet.  But that's only one of a dozen possibilities.)

__SVR4 is not defined. configure finds /dev/ptmx and deems it usable.
sys/stropts.h also found and deemed usable. Cutting off the two
`&& defined(__SVR4)' sections doesn't help. What else might I try?

Oliver

Index: configure.ac
===================================================================
RCS file: /cvsroot/zsh/zsh/configure.ac,v
retrieving revision 1.13
diff -u -r1.13 configure.ac
--- configure.ac	4 Mar 2004 14:03:48 -0000	1.13
+++ configure.ac	12 Mar 2004 16:07:08 -0000
@@ -2007,18 +2007,21 @@
   fi
   if test -n "$GCC"; then
     case "$host_os" in
+      hpux*)   DLLDFLAGS="${DLLDFLAGS=-shared}" ;;
       darwin*) DLCFLAGS="${DLCFLAGS=-fno-common}" ;;
       *)       DLCFLAGS="${DLCFLAGS=-fPIC}" ;;
     esac
   else
     case "$host_os" in
-      hpux*)                 DLCFLAGS="${DLCFLAGS=+z}" ;;
+      hpux*)
+        DLCFLAGS="${DLCFLAGS=+z}"
+        DLLDFLAGS="${DLLDFLAGS=-b}"
+      ;;
       sunos*)                DLCFLAGS="${DLCFLAGS=-pic}" ;;
       solaris*|sysv4*|esix*) DLCFLAGS="${DLCFLAGS=-KPIC}" ;;
     esac
   fi
   case "$host_os" in
-    hpux*)        DLLDFLAGS="${DLLDFLAGS=-b}" ;;
     freebsd*|linux*|irix*|osf*|gnu*) DLLDFLAGS="${DLLDFLAGS=-shared}" ;;
     sunos*)       DLLDFLAGS="${DLLDFLAGS=-assert nodefinitions}" ;;
     sysv4*|esix*) DLLDFLAGS="${DLLDFLAGS=-G $ldflags}" ;;


  reply	other threads:[~2004-03-12 16:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-11 19:15 Peter Stephenson
2004-03-12 16:17 ` Oliver Kiddle [this message]
2004-03-12 16:56   ` Peter Stephenson
2004-03-12 19:00     ` Oliver Kiddle
2004-03-15 10:43       ` Peter Stephenson

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=1430.1079108272@trentino.logica.co.uk \
    --to=okiddle@yahoo.co.uk \
    --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).