git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: James Mills <prologic@shortcircuit.net.au>
Cc: git@vger.kernel.org
Subject: Re: Git v2.46.0 and --allow-multiple-definition linker flag
Date: Sat, 21 Dec 2024 18:30:33 -0800	[thread overview]
Message-ID: <xmqqbjx4bgae.fsf@gitster.g> (raw)
In-Reply-To: <CALGqR9+bH3nMrGqPQ18aqs-epSHRFQOtnd6Da55=KrtSu+Jrkg@mail.gmail.com> (James Mills's message of "Sun, 22 Dec 2024 09:23:19 +1000")

James Mills <prologic@shortcircuit.net.au> writes:

> tcc: error: unsupported linker option '--allow-multiple-definition'
>
> I bisected the Git releases and traced the introduction of this new
> flag to v2.46.0
>
> I can't find any details of this flag really or when this was
> introduced in the GNU binutils and so far I haven't asked if the Tiny
> C devs intend to support this option (yet).

Would

    $ make LINK_FUZZ_PROGRAMS=""

help?

The platform-specific tweak defined in config.mak.uname file assumes
that you have glibc plus gcc or clang with usual binutils niceties
once you claim that you are Linux.  It lumps all different variants
of Linux into a single ball of wax and defines LINK_FUZZ_PROGRAMS
Makefile macro, which is a bit unfortunate.



  reply	other threads:[~2024-12-22  2:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-21 23:23 Git v2.46.0 and --allow-multiple-definition linker flag James Mills
2024-12-22  2:30 ` Junio C Hamano [this message]
2024-12-22  2:47   ` Junio C Hamano
2025-01-13 17:54     ` Josh Steadmon
2025-01-14 11:03       ` Jeff King

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=xmqqbjx4bgae.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=prologic@shortcircuit.net.au \
    /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 NNTP newsgroup(s).