From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Timo Aaltonen" <tjaalton@cc.hut.fi>, <zsh-workers@sunsite.dk>
Subject: RE: AIX abd GCC
Date: Wed, 27 Jun 2001 18:37:36 +0400 [thread overview]
Message-ID: <004b01c0ff16$b5a0c6b0$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <Pine.OSF.4.10.10106271710360.12353-100000@tiku.hut.fi>
>
> >
> > Did you use DLLDFLAGS=-shared or it worked OOTB?
> >
> > Could you give exact configure invocation you used?
>
> Yes, that was the only trick I used..
>
> ..but it works also without it, OOTB.
>
You mean, it even correctly finds boolcodes & friends?
Anyway, after reading AIX ld docs I am not happy with how we are doing it.
We do not actually build shared libraries (meaning shareable code) so every
zsh instance gets own copy of every loaded module.
Timo, could you do me a favour, update CVS and try the following patch. Just
go into zsh dir and do
cvs up -dP
then apply the patch. This should produce better code ... I hope.
Or should we just leave it as is?
-andrej
Index: zshconfig.ac
===================================================================
RCS file: /cvsroot/zsh/zsh/zshconfig.ac,v
retrieving revision 1.8
diff -u -r1.8 zshconfig.ac
--- zshconfig.ac 2001/06/19 06:59:24 1.8
+++ zshconfig.ac 2001/06/27 14:32:38
@@ -1535,6 +1535,11 @@
DL_EXT="${DL_EXT=so}"
DLLD="${DLLD=$CC}"
zsh_cv_func_dlsym_needs_underscore=no
+ if test -n "$GCC"; then
+ DLLDFLAGS=${DLLDFLAGS=-shared}
+ else
+ DLLDFLAGS=${DLLDFLAGS=-bM:SRE}
+ fi
DLLDFLAGS=${DLLDFLAGS=}
EXTRA_LDFLAGS=${EXTRA_LDFLAGS=}
EXPOPT=${LDARG}-bE:
next prev parent reply other threads:[~2001-06-27 14:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <003c01c0ff0b$06c60de0$21c9ca95@mow.siemens.ru>
2001-06-27 14:05 ` Timo Aaltonen
2001-06-27 14:08 ` Andrej Borsenkow
2001-06-27 14:29 ` Timo Aaltonen
2001-06-27 14:37 ` Andrej Borsenkow [this message]
2001-06-27 15:05 ` Timo Aaltonen
2001-06-27 15:15 ` Andrej Borsenkow
2001-06-27 15:26 ` Timo Aaltonen
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='004b01c0ff16$b5a0c6b0$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=tjaalton@cc.hut.fi \
--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).