From: Peter Stephenson <pws@csr.com>
To: cygwin@cygwin.com, zsh-workers@sunsite.dk (Zsh hackers list)
Subject: dllwrap fails to find last exported symbol alphabetically
Date: Thu, 25 Mar 2004 13:05:23 +0000 [thread overview]
Message-ID: <11205.1080219923@csr.com> (raw)
A problem now seen by two of us with recent Cygwin installations:
mine was updated to `current' status last week. However, I don't think
this is new since I've been seeing it on my own setup for a while.
Zsh uses `dllwrap --export-all-symbols' to link against it's own DLL's.
On the systems in question, dllwrap failed to identify the last symbol
exported from the main dll (zsh.dll) against which all the other DLL's
are linked. The symbol in question is `zwarnnam'; we've verified it
really is the last symbol by adding a dummy one later in the alphabet,
and the problem goes away. (This is an easy workaround so consequently
finding a real fix isn't a high priority for us.)
It sounds like if this is fundamental lots of people would have fallen
over it, but I've no idea what else might be relevant.
Anyway, on systems where it does trigger, it will show up by downloading
zsh 4.2.0 from ftp://ftp.zsh.org/pub/ and trying to compile with default
options. You will see warnings about failures to find the symbol
zwarnnam when linking DLL's. (The failure seen by users is a crash on
an attempt to print warning messages form libraries. Running `vared
nonexistentvar' form the installed shell will do this.) We haven't
narrowed it down any further.
If you (the Cygwin people) need more information, it's probably best to
prod zsh@sunsite.org (this list runs qconfirm but you only need to
confirm once).
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK Tel: +44 (0)1223 692070
**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential
and/or privileged material.
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by
persons or entities other than the intended recipient is
prohibited.
If you received this in error, please contact the sender and
delete the material from any computer.
**********************************************************************
next reply other threads:[~2004-03-25 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 13:05 Peter Stephenson [this message]
2004-03-25 17:45 ` Peter A. Castro
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=11205.1080219923@csr.com \
--to=pws@csr.com \
--cc=cygwin@cygwin.com \
--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).