From: "Peter A. Castro" <doctor@fruitbat.org>
To: Peter Stephenson <pws@csr.com>
Cc: cygwin@cygwin.com, Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: dllwrap fails to find last exported symbol alphabetically
Date: Thu, 25 Mar 2004 09:45:34 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.53.0403250919390.5939@gremlin.fruitbat.org> (raw)
In-Reply-To: <11205.1080219923@csr.com>
On Thu, 25 Mar 2004, Peter Stephenson wrote:
> 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.
This should be corrected. I'd changed the Cygwin port to use
'gcc -shared -Wl,--export-all-symbols'
specifically to address export symbol and other loader related issues
under Cygwin. Apparently my changes never made it back into the source.
I'll have to see why.
> 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.
Don't know. I've only recently pulled it and started my porting. I'll
figure out what's happening and feed back.
> 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
4.2.0 has only been out for a few days. Gimme a little time!
I'll get to the bottom of this.
> 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 A. Castro <doctor@fruitbat.org> or <Peter.Castro@oracle.com>
"Cats are just autistic Dogs" -- Dr. Tony Attwood
prev parent reply other threads:[~2004-03-25 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 13:05 Peter Stephenson
2004-03-25 17:45 ` Peter A. Castro [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=Pine.LNX.4.53.0403250919390.5939@gremlin.fruitbat.org \
--to=doctor@fruitbat.org \
--cc=cygwin@cygwin.com \
--cc=pws@csr.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).