From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: gnulib m4/threadlib.m4 bug crashing package tests
Date: Sun, 28 Nov 2021 17:23:33 +0100 [thread overview]
Message-ID: <87mtlo45bu.fsf@Rainer.invalid> (raw)
In-Reply-To: <87r1b0477l.fsf@Rainer.invalid> (Achim Gratz's message of "Sun, 28 Nov 2021 16:42:54 +0100")
Achim Gratz writes:
> I'd rather know why the bleeping heck the test suddenly succeeds when it
> clearly doesn't actually work. In other words, I think the linker
> should complain, but since it obviously did that before Cygwin 3.2.0 and
> not after, something must have changed somewhere that prevent s it from
> doing that.
So the exact same problem was discussed in 2010 and the test that's
still there conceived that checks if the returned symbol for weakly
defined fputs is NULL (which would then disable weak symbols for
gnulib). That obviously still happens on 32bit, but no longer on 64bit.
I think the test is bogus in both cases since the executable will always
be linked again cygwin1.dll and so should be able to resolve the symbol
either way.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
next prev parent reply other threads:[~2021-11-28 16:23 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 [this message]
2021-11-28 18:34 ` Brian Inglis
2021-11-29 17:38 ` Achim Gratz
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=87mtlo45bu.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).