From: Philip McGrath <philip@philipmcgrath.com>
To: 55998@debbugs.gnu.org, Maxime Devos <maximedevos@telenet.be>
Subject: [bug#55998] [PATCH] gnu: Add cctools.
Date: Fri, 17 Jun 2022 07:28:48 -0400 [thread overview]
Message-ID: <7392720.EvYhyI6sBW@avalon> (raw)
In-Reply-To: <3c56e51f000c345e5bf0736a7be9ade3c12a4c96.camel@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]
On Wednesday, June 15, 2022 4:07:47 PM EDT Maxime Devos wrote:
> Philip McGrath schreef op wo 15-06-2022 om 15:19 [-0400]:
> > 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.
>
> Ok, but the package description is implying a linker is available,
> which is not the case, due to the lack of a Darwin libc in Guix.
>
Concretely, there is an `ld`, and it runs at least enough to print out a usage
note.
I can't say for certain *why* it works, though the way LLVM doesn't need a
different binary for each target and the somewhat unusual way linking to libc
and other system libraries works on Darwin. Though does a linker really need a
libc? In principle, it could link things that don't link to libc, or even link
libc itself.
I haven't tried actually linking anything with this package's `ld`, but, even
if it turns out to not be fully functional yet, this is the package that
contains Darwin's `ld`.
I did tweak the description in v2 to replace the reference to `libtool`,
because Darwin's `libtool` is something completely unrelated than the program
in the Guix package called `libtool`.
-Philip
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-06-17 13: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
2022-06-15 20:07 ` Maxime Devos
2022-06-17 11:28 ` Philip McGrath [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7392720.EvYhyI6sBW@avalon \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.