From: Philip McGrath <philip@philipmcgrath.com>
To: Maxime Devos <maximedevos@telenet.be>, 55998@debbugs.gnu.org
Subject: [bug#55998] [PATCH] gnu: Add cctools.
Date: Wed, 15 Jun 2022 15:19:06 -0400 [thread overview]
Message-ID: <b4e4c72d-de2d-4df3-f3f0-54bf0cbf9b46@philipmcgrath.com> (raw)
In-Reply-To: <149964d020ce967474ce946eda5031fa7ed99245.camel@telenet.be>
On 6/15/22 14:53, Maxime Devos wrote:
> Philip McGrath schreef op wo 15-06-2022 om 13:15 [-0400]:
>> + (synopsis "Darwin's @code{cctools} and @code{ld64}")
>> + ;; Confusingly enough, the program is called ld64, but the command is
>> + ;; just ld (with no symlink), so @command{ld64} would be wrong.
>> + (description
>> + "Darwin's @code{cctools} are a set of tools somewhat similar in purpose
>> +to GNU Binutils, but for Mach-O files targeting Darwin. The suite includes
>> +@command{install_name_tool}, @command{libtool}, and other specialized tools in
>> +addition to standard utilities like @command{ld} and @command{as}. This
>> +package provides portable versions of the tools.")
>> + (license license:apsl2))))
>
> How can this work? We don't have any (cross-compiled) Darwin libc
> libraries to let it link against. Is this a draft patch?
>
Fortunately, we don't need a Darwin libc: tools like `install_name_tool`
run on GNU/Linux, but work with Darwin binaries, somewhat like
`patchelf` can work on a cross-compiled binary. From another point of
view, it's a bit like some parts of MinGW.
This patch is not enough for a Darwin cross-compilation toolchain,
though I believe it would play a role analogous to GNU Binutils in such
a toolchain.
Still, several of the tools are useful (albeit niche) on their own,
which is why I sent this patch now. A whole group of tools supports
inspecting Mach-O binaries, for example.
-Philip
next prev parent reply other threads:[~2022-06-15 19:20 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 17:15 [bug#55998] [PATCH] gnu: Add cctools Philip McGrath
2022-06-15 18:32 ` Maxime Devos
2022-06-15 18:45 ` Maxime Devos
2022-06-15 19:06 ` Philip McGrath
2022-06-15 19:35 ` Maxime Devos
2022-06-15 21:00 ` Philip McGrath
2022-06-15 21:11 ` Maxime Devos
2022-06-15 21:20 ` ( via Guix-patches via
2022-06-15 18:53 ` Maxime Devos
2022-06-15 19:19 ` Philip McGrath [this message]
2022-06-15 20:07 ` Maxime Devos
2022-06-17 11:28 ` Philip McGrath
2022-06-15 18:55 ` Maxime Devos
2022-06-15 19:34 ` Philip McGrath
2022-06-15 18:56 ` Maxime Devos
2022-06-15 19:21 ` Philip McGrath
2022-06-15 19:23 ` Maxime Devos
2022-06-17 11:19 ` Philip McGrath
2022-06-15 20:04 ` Maxime Devos
2022-06-17 11:09 ` Philip McGrath
2022-06-19 21:01 ` Ludovic Courtès
2022-06-15 20:17 ` Maxime Devos
2022-06-16 22:29 ` Philip McGrath
2022-06-17 6:14 ` Maxime Devos
2022-06-15 20:18 ` Maxime Devos
2022-06-15 20:23 ` Maxime Devos
2022-06-16 23:29 ` Philip McGrath
2022-06-17 11:51 ` [bug#55998] [PATCH v2] " Philip McGrath
2022-06-19 21:02 ` bug#55998: [PATCH] " Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b4e4c72d-de2d-4df3-f3f0-54bf0cbf9b46@philipmcgrath.com \
--to=philip@philipmcgrath.com \
--cc=55998@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).