From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Mathieu Othacehe <othacehe@gnu.org>, 45020@debbugs.gnu.org
Subject: [bug#45020] [PATCH 0/2] image: Add system field.
Date: Tue, 15 Dec 2020 22:56:15 +0100 [thread overview]
Message-ID: <87eejqlon4.fsf@gnu.org> (raw)
In-Reply-To: <86r1nrma5m.fsf@gmail.com> (zimoun's message of "Tue, 15 Dec 2020 15:11:33 +0100")
Hi,
zimoun <zimon.toutoune@gmail.com> skribis:
>> --8<---------------cut here---------------start------------->8---
>> ;; Description of a platform supported by the GNU system.
>> (define-record-type* <platform> platform make-platform
>> platform?
>> (triplet platform-triplet) ;"x86_64-linux-gnu"
>> (system-type platform-system-type) ;"x86_64-linux"
>> (linux-architecture platform-linux-architecture) ;"amd64"
>> (kernel platform-kernel) ;<package>
>> (ld.so platform-ld.so) ;"ld-linux-x86-64.so.2"
>> (gcc platform-gcc) ;<package>
>> (binutils platform-binutils) ;<package>
>> (libc platform-transform-libc)) ;<package>
>> --8<---------------cut here---------------end--------------->8---
>
> Naively and what confuse me is the redundancy of the information. For
> example, is it possible to do something else than “gnu”? Or when one
> thing is fixed, other parameters are also fixed, for instance does it
> make sense
>
> "x86_64-linux-gnu"
> "i686-hurd"
> "arm"
> "ld-hurd-arm.so.2"
>
> ?
For a given platform, say “GNU/Hurd on i586”, all the parameters are
fixed, with some degrees of liberty on the toolchain, though.
However, currently that information is scattered across different
places, so the goal here would be to gather it all in one place, which
should facilitate porting to new platforms.
Ludo’.
next prev parent reply other threads:[~2020-12-15 21:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 10:53 [bug#45020] [PATCH 0/2] image: Add system field Mathieu Othacehe
2020-12-03 10:53 ` [bug#45021] [PATCH 1/2] " Mathieu Othacehe
2020-12-03 20:41 ` Danny Milosavljevic
2020-12-04 8:12 ` Mathieu Othacehe
2020-12-04 9:01 ` Danny Milosavljevic
2020-12-05 10:24 ` Mathieu Othacehe
2020-12-03 10:53 ` [bug#45022] [PATCH 2/2] image: Rename "raw" image-type to "efi-raw" Mathieu Othacehe
2020-12-03 13:11 ` [bug#45020] [PATCH 0/2] image: Add system field zimoun
2020-12-09 8:25 ` Efraim Flashner
2020-12-09 10:15 ` Mathieu Othacehe
2020-12-09 10:27 ` Efraim Flashner
2020-12-11 16:50 ` Ludovic Courtès
2020-12-12 8:30 ` Mathieu Othacehe
2020-12-12 12:34 ` zimoun
2020-12-13 14:15 ` Ludovic Courtès
2020-12-15 14:11 ` zimoun
2020-12-15 21:56 ` Ludovic Courtès [this message]
2020-12-12 17:51 ` Ludovic Courtès
2020-12-15 9:58 ` Mathieu Othacehe
2021-07-16 2:04 ` Maxim Cournoyer
2021-08-30 16:24 ` Mathieu Othacehe
2021-10-05 8:26 ` Mathieu Othacehe
2021-10-11 12:06 ` bug#45020: " Mathieu Othacehe
2020-12-13 14:59 ` [bug#45020] " Danny Milosavljevic
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=87eejqlon4.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=45020@debbugs.gnu.org \
--cc=othacehe@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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.