public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: binutils@sourceware.org
Subject: Re: [Bug] DWARF-5 section names in PE/PEP and weak symbols
Date: Sun, 13 Feb 2022 21:17:38 +0100	[thread overview]
Message-ID: <87mtiumsgt.fsf@Rainer.invalid> (raw)
In-Reply-To: <b51431d6-eaf3-552c-3ceb-e8ee3fe1540f@redhat.com> (Nick Clifton via Binutils's message of "Wed, 15 Dec 2021 13:12:32 +0000")

Nick Clifton via Binutils writes:
> So you are saying that because the linker script now includes specific
> references to DWARF-5 debug sections, the fputs symbol is being pulled
> in to the link from the cygwin1.dll and hence it is no longer undefined ?
> That seems to be most strange.

Looking further into this I'm beginning to think that the previous
behaviour was a bug that has since been fixed (and that probably has
nothing to do with the DWARF5 sections other than this change for some
reason interacted with the pre-existing bug to trip up a poorly written
autoconf test in gnulib).

In fact it appears that with 2.38 weak symbols are in fact working
correctly for the handful examples that I've come up with.  I'll have to
go back to the original example that produced buggy behaviour (grep-3.7
w/o patched gnulib threadlib.m4) and see if that's now working as well
(it may not, since the libraries have all been produced by earlier ld,
but it seems worth trying).


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

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

  parent reply	other threads:[~2022-02-13 20:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08 18:27 Achim Gratz
2021-12-15 13:12 ` Nick Clifton
2021-12-20 19:45   ` Achim Gratz
2022-01-23  8:10     ` Achim Gratz
2022-01-29  7:57   ` Achim Gratz
2022-02-13 20:17   ` Achim Gratz [this message]
2022-02-14 11:02     ` ASSI
2022-02-15 17:58       ` Achim Gratz
2022-02-15 19:08         ` Achim Gratz
2022-02-15 20:19         ` 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=87mtiumsgt.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=binutils@sourceware.org \
    /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).