zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <borsenkow.msk@sni.de>
To: "Zefram" <zefram@tao.co.uk>, <zsh-announce@math.gatech.edu>
Subject: URGENT: Please, backout change (Re: zsh-3.1.4 released)
Date: Mon, 1 Jun 1998 14:44:11 +0400	[thread overview]
Message-ID: <000d01bd8d4a$379e4ee0$21c9ca95@ao13.mow.sni.de> (raw)


Because I am responsible for this change, I request to backout it:

Mon May 25 21:13:41 1998  Andrew Main  <zefram@zsh.org>

 * Src/mkmakemod.sh, configure.in, aczsh.m4: Link modules against
   $(LIBS), and include -lc in $(LIBS), in case a module requires
   a function that only exists in static libraries.


It breaks environment in ZSH. It happens as following:

as said, our systems have two libc - dynamic libc.so.1 and static libc.so
(yes, it *is* ar lib, but called so :) Unfortunately, _environ is located in
static libc. If I try to link shared libray, which is using _environ, with
libc, the following happens:

  the code in libzsh gets its own static copy of _environ
  startup code in zsh is linked with it's own static copy of _environ
  which results in every copy of ZSH starting with blank (at the best)
environment pointer.

This problem is not specific to ZSH - every now and then it comes up e.g.
with Perl, or any software, which is using shared libs.

Unfortunately, there is no clean way to autoconf it. Dynamic loading runs on
MIPS line (Reliant UNIX) without this change; it is possible to make it
running on Intel line (SINIX-L/SINIX-M) but with many eforts (actually, only
one module has to be linked with -lc) ... I personally would simply disallow
dynamic loading on i386-sni-sysv4 - or at least to put it in NEWS or FAQ.

Thank you

A. Borsenkow


             reply	other threads:[~1998-06-01 11:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-06-01 10:44 Andrej Borsenkow [this message]
1998-06-01 11:03 ` 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='000d01bd8d4a$379e4ee0$21c9ca95@ao13.mow.sni.de' \
    --to=borsenkow.msk@sni.de \
    --cc=zefram@tao.co.uk \
    --cc=zsh-announce@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).