zsh-workers
 help / color / mirror / code / Atom feed
From: gwing@primenet.com.au
To: zsh-workers@math.gatech.edu (zsh-workers)
Subject: zsh-3.1.1 on NetBSD patch & problems
Date: Mon, 17 Feb 1997 17:49:28 +1100 (EST)	[thread overview]
Message-ID: <19970217064928.14467.qmail@primenet.com.au> (raw)

Heyla,
I've set up zsh to use modules on NetBSD
This is on NetBSD 1.2C .  Similar systems like OpenBSD and FreeBSD may
work with the same things.

A couple of things:

1) What's happened to default compctls?
% zsh-3.0.0 -f
% compctl
bindkey -b
builtin -c
export -v
setopt -o
typeset -v
unset -v
unsetopt -o
vared -v
which -c
COMMAND -c
DEFAULT -f
FIRST

% zsh-3.1.1 -f
% compctl
COMMAND -c
DEFAULT -f
FIRST


2) NetBSD make has lots of problems with the Makefile:
 2a) Zle/* stuff doesn't get built the first time you ``make'' in Src.
 2b) if you've made everything, then ``make'' without changing everything,
     everything is rebuilt.
 Of course, GNU make works fine.

3) why is -pedantic set for --enable-debug ?

4) How about `important' changes like
      * Src/options.c: set ALWAYSLASTPROMPT, APPENDHISTORY, AUTOLIST,
	AUTOMENU, AUTOPARAMKEYS, AUTOPARAMSLASH, AUTOREMOVESLASH,
	LISTAMBIGUOUS, LISTTYPES options by default
   going into Etc/NEWS

5) On NetBSD:
 ``ld -x -Bshareable -o foo.so foo..o''
seems to be doing the same thing as
 ``ar r foo.a foo..o bar..o
   ranlib foo.a
   ld -x -Bshareable -Bforcearchive -o foo.so foo.a''
which is the standard way NetBSD does shared libraries. 
The first form is compatible with the current zsh Makefile style.  The second
would require several changes.  Hopefully, the first form will always work 
like the second.

6) I had something else, but I can't think of it now, so here's the patch.


*** configure.in	1997/01/25 19:00:07	3.1.1.11
--- configure.in	1997/02/17 05:53:09
***************
*** 208,214 ****
  fi
  if test -n "$auto_ldflags"; then
    if test "${enable_zsh_debug}" = yes; then
!     LDFLAGS=-g
    fi
  fi
  
--- 208,217 ----
  fi
  if test -n "$auto_ldflags"; then
    if test "${enable_zsh_debug}" = yes; then
!     case "$host_os" in
!       netbsd*)    LDFLAGS="" ;;
!       *)          LDFLAGS=-g ;;
!     esac
    fi
  fi
  
***************
*** 821,826 ****
--- 824,830 ----
      solaris*)     DLLDFLAGS="${DLLDFLAGS=-G}" ;;
      sunos*)       DLLDFLAGS="${DLLDFLAGS=-assert nodefinitions}" ;;
      sysv4*|esix*) DLLDFLAGS="${DLLDFLAGS=-G $ldflags}" ;;
+     netbsd*)      DLLDFLAGS="${DLLDFLAGS=-x -Bshareable}" ;;
    esac
    case "$host_os" in
      hpux*)  EXTRA_LDFLAGS="${EXTRA_LDFLAGS=-Wl,-E}" ;;


-- 
Geoff Wing [gwing@primenet.com.au]   Technical Manager
  Phone    : +61-3-9818 2977         PrimeNet - Internet Consultancy
  Facsimile: +61-3-9819 3788         Web : <URL:http://www.primenet.com.au/>
  Mobile   : 0412 162 441


             reply	other threads:[~1997-02-17  7:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-02-17  6:49 gwing [this message]
1997-02-17 18:08 ` Zefram
1997-02-17 19:37   ` Vinnie Shelton
1997-02-17 19:47     ` Hrvoje Niksic
1997-02-17 20:38     ` Zefram
1997-02-17 23:03       ` Richard Coleman
1997-02-17 23:48         ` Vinnie Shelton
1997-02-19 14:23   ` gwing
1997-02-19 15:22     ` Zoltan Hidvegi
1997-02-19 17:24     ` 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=19970217064928.14467.qmail@primenet.com.au \
    --to=gwing@primenet.com.au \
    --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).