zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Sven Wischnowsky" <wischnow@informatik.hu-berlin.de>,
	<zsh-workers@sunsite.auc.dk>
Cc: <gene@bear.com>
Subject: Found RE: dev-14: ld.so: Src/zsh: relocation error: symbol not found: nbrbeg
Date: Sat, 8 Jan 2000 15:14:49 +0300	[thread overview]
Message-ID: <000601bf59d1$f5f6eaa0$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <200001061409.PAA18367@beta.informatik.hu-berlin.de>

>
> > .zshrc:9: failed to load module: zsh/complete
> >
> > I tried this with two different OS/compiler versions.
> >
> > The message in subject is from dlerror() that I added to try_load_module()
>
> System type? Didn't we have this kind of problem (a dynamically loaded
> module could not get at the symbols of another dynamically loaded
> module) on SunOS4.x?
>


This is due to 9200 + somewhat unusual behaviour of our compiler. 9200 makes
module.c prefer dl.h to dlfcn.h. We do not have /use/include/dl.h but we do have
/usr/include/sys/dl.h (that has nothing to do with dynamic loading at all). Our
compiler does search in both /usr/include and /use/include/sys by default -
hence, AC_CHECK_HEADER finds /usr/include/sys/dl.h. This makes RTLD_*
(RTLD_GLOBAL is important here) be missed. Hence, no symbol from other modules
is ever exported.

In any case, I do not understand the logic here. If dlfcn.h is missing on hpux
11.0, the branch should go under #ifdef HAVE_DL_H and not under #ifdef
HAVE_DLFCN_H.

Could anybody finally suggest reasonable order of include checking here? I
totally fail to understand how patch in 9200 fixed the problem in text.

/andrej


      parent reply	other threads:[~2000-01-08 12:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-06 14:09 Sven Wischnowsky
2000-01-06 15:15 ` Andrej Borsenkow
2000-01-08 12:14 ` Andrej Borsenkow [this message]

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='000601bf59d1$f5f6eaa0$21c9ca95@mow.siemens.ru' \
    --to=andrej.borsenkow@mow.siemens.ru \
    --cc=gene@bear.com \
    --cc=wischnow@informatik.hu-berlin.de \
    --cc=zsh-workers@sunsite.auc.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).