From: Tommy Murphy <tommy_murphy@hotmail.com>
To: Jason Carrete <jasoncarrete5@gmail.com>,
"crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: Re: Config portability
Date: Fri, 2 Feb 2024 23:43:43 +0000 [thread overview]
Message-ID: <CWXP123MB49360A7B260A08BB97292549F9422@CWXP123MB4936.GBRP123.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <5df2449f-916a-4023-94a4-18d17a82f2f6@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 311 bytes --]
Won't the results on different machines (with the same `.config`) depend on the specifics (e.g. versions) of the dependencies installed?
* https://crosstool-ng.github.io/docs/os-setup/
Which is why some sort of "constrained" environment (e.g. VM/container based) may be useful for predictable results?
next prev parent reply other threads:[~2024-02-02 23:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 23:13 Jason Carrete
2024-02-02 23:43 ` Tommy Murphy [this message]
2024-02-02 23:43 ` Chris Packham
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=CWXP123MB49360A7B260A08BB97292549F9422@CWXP123MB4936.GBRP123.PROD.OUTLOOK.COM \
--to=tommy_murphy@hotmail.com \
--cc=crossgcc@sourceware.org \
--cc=jasoncarrete5@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.
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).