From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Christian Tramnitz <christian+gcc-gnu@tramnitz.com>
Cc: gcc@gcc.gnu.org
Subject: Re: ld: document static libraries when performing static linking
Date: Wed, 21 Feb 2024 17:48:49 +0000 [thread overview]
Message-ID: <CAH6eHdR2KnnTaZbY4SrKnRKE2n4qOgj_uo+srMR_nmn_JVQPgA@mail.gmail.com> (raw)
In-Reply-To: <CADddEsCm7OpQ51GE+hfix2OntdnGmcWTppK8-g_2O175qS5VjA@mail.gmail.com>
On Wed, 21 Feb 2024 at 17:29, Christian Tramnitz via Gcc
<gcc@gcc.gnu.org> wrote:
>
> Hello,
>
> For statically linked binaries one wants to keep track of external
> libraries that were pulled in at link time. I haven't found any
> initiatives or standards trying to achieve this yet, so I would like
> to make a proposal.
>
> ld already supports the `--depedency-file=` option to create a
> depfile, to some degree, documenting dependencies in Makefile format.
> While it's a good starting point, it's not sufficient.
The linker is part of Binutils not GCC:
https://www.gnu.org/software/binutils/
You probably want to use the binutils mailing list, not the GCC one.
prev parent reply other threads:[~2024-02-21 17:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 17:28 Christian Tramnitz
2024-02-21 17:48 ` Jonathan Wakely [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=CAH6eHdR2KnnTaZbY4SrKnRKE2n4qOgj_uo+srMR_nmn_JVQPgA@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=christian+gcc-gnu@tramnitz.com \
--cc=gcc@gcc.gnu.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).