public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: gnulib m4/threadlib.m4 bug crashing package tests
Date: Mon, 29 Nov 2021 18:38:14 +0100	[thread overview]
Message-ID: <87zgpmuak9.fsf@Rainer.invalid> (raw)
In-Reply-To: <2ecfa9cc-046c-6113-28f0-62411778e0b7@SystematicSw.ab.ca> (Brian Inglis's message of "Sun, 28 Nov 2021 11:34:40 -0700")

Brian Inglis writes:
> The problem with Cygwin weak symbols is apparently that ld expects
> there to be a runtime dynamic loader to resolve NULL weak dynamic
> library references, but unlike ELF neither Cygwin nor Windows does so,
> and PE may not retain the information to do so, or this project would
> likely have done so.

No, that part is well understood since more than a decade when that
problem first hit, the actual problem is that such symbols no
longer resolve to 0x0 on 64bit.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

      reply	other threads:[~2021-11-29 17:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-29 23:46 Brian Inglis
2021-11-25 16:26 ` Ken Brown
2021-11-25 18:25   ` Yaakov Selkowitz
2021-11-26  4:48     ` Brian Inglis
2021-11-26 13:08     ` Ken Brown
2021-11-26 17:34       ` Brian Inglis
2021-11-26 18:17         ` Ken Brown
2021-11-28 15:42     ` Achim Gratz
2021-11-28 15:56       ` Ken Brown
2021-11-28 16:33         ` Achim Gratz
2021-11-28 18:21           ` Ken Brown
2021-11-29 16:39             ` Achim Gratz
2021-12-08 18:49               ` Achim Gratz
2021-12-09  4:41                 ` Brian Inglis
2021-11-28 16:23       ` Achim Gratz
2021-11-28 18:34         ` Brian Inglis
2021-11-29 17:38           ` Achim Gratz [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=87zgpmuak9.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin-apps@cygwin.com \
    /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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).