[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gcc
Subject:    Re: ld: document static libraries when performing static linking
From:       Jonathan Wakely via Gcc <gcc () gcc ! gnu ! org>
Date:       2024-02-21 17:48:49
Message-ID: CAH6eHdR2KnnTaZbY4SrKnRKE2n4qOgj_uo+srMR_nmn_JVQPgA () mail ! gmail ! com
[Download RAW message or body]

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 in list] [next in list] [prev in thread] [next in thread]