zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <borsenkow.msk@sni.de>
To: "Peter Stephenson" <pws@ibmth.df.unipi.it>,
	"Zsh hackers list" <zsh-workers@math.gatech.edu>
Subject: RE: zsh-3.1.5-pws-5 available
Date: Sun, 24 Jan 1999 15:50:16 +0300	[thread overview]
Message-ID: <000501be4798$1753c6c0$21c9ca95@mowp.siemens.ru> (raw)
In-Reply-To: <9901231125.AA13246@ibmth.df.unipi.it>


The patch below makes it possible to compile ZSH dynamic on ReliantUNIX. It
avoids building shared lib by exporting executables symbols.

I don't claim, that it works on all versions. It should work on 5.43 and
above, that are current.

Question:

   sysv4*|esix*) DLLDFLAGS="${DLLDFLAGS=-G $ldflags}" ;;
                                            ^^^^^^^^

ldflags does not appear to be used (or set) anywhere else. What is the point
of it? Also, as I noted, configure seems to ignore values of CPPFLAGS and
LDFLAGS. Is it intentional?

/andrej

--- zsh-3.1.5-pws-5/configure.in.org    Thu Jan 21 12:02:34 1999
+++ zsh-3.1.5-pws-5/configure.in        Sun Jan 24 15:38:01 1999
@@ -1008,9 +1008,10 @@
     aix*)         DLLDFLAGS="${DLLDFLAGS=-G -bexpall -lc}" ;;
     solaris*|sysv4*|esix*) DLLDFLAGS="${DLLDFLAGS=-G}" ;;
   esac
-  case "$host_os" in
-    hpux*)  EXTRA_LDFLAGS="${EXTRA_LDFLAGS=-Wl,-E}" ;;
-    linux*) EXTRA_LDFLAGS="${EXTRA_LDFLAGS=-rdynamic}" ;;
+  case "$host" in
+    *-hpux*)  EXTRA_LDFLAGS="${EXTRA_LDFLAGS=-Wl,-E}" ;;
+    *-linux*) EXTRA_LDFLAGS="${EXTRA_LDFLAGS=-rdynamic}" ;;
+    mips-sni-sysv4) EXTRA_LDFLAGS="${EXTRA_LDFLAGS=-Wl,-Blargedynsym}" ;;
   esac
   AC_CACHE_CHECK(if your dlsym() needs a leading underscore,
    zsh_cv_func_dlsym_needs_underscore,


  reply	other threads:[~1999-01-25  9:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-23 11:25 Peter Stephenson
1999-01-24 12:50 ` Andrej Borsenkow [this message]
1999-01-25 10:05   ` Helmut Jarausch
1999-01-25 16:38     ` Peter Stephenson
1999-01-25  0:41 ` PATCH: Missing bits " Bart Schaefer
1999-01-25  1:48   ` Bart Schaefer
1999-01-25  9:16 Sven Wischnowsky

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='000501be4798$1753c6c0$21c9ca95@mowp.siemens.ru' \
    --to=borsenkow.msk@sni.de \
    --cc=pws@ibmth.df.unipi.it \
    --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).