From: Marius Bakke <mbakke@fastmail.com>
To: Raghav Gururajan <raghavgururajan@disroot.org>,
Danny Milosavljevic <dannym@scratchpost.org>
Cc: 40021@debbugs.gnu.org
Subject: [bug#40021] gnu: Add mm-common.
Date: Thu, 19 Mar 2020 10:27:04 +0100 [thread overview]
Message-ID: <877dzgbspj.fsf@devup.no> (raw)
In-Reply-To: <7be770ee7b6782620abc9bc721061a38@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 873 bytes --]
"Raghav Gururajan" <raghavgururajan@disroot.org> writes:
> Hi Danny!
>
> Thanks for the information. I will get back to you regarding the modules.
>
> I also noticed that I didn't enable a build option that downloads gcc tag files. Can you help me with how to provide network access inside build container/process? The wget is unable to resolve domain name.
>
> Resolving gcc.gnu.org (gcc.gnu.org)... failed: Name or service not known.
> wget: unable to resolve host address ?gcc.gnu.org?
It is not possible to enable network access inside the build container.
If it were, build processes would no longer be deterministic, and we
would lose a lot of reproducibility guarantees!
You'll need to supply whatever external resources the package needs as
"native-inputs", and then tell the build system how to access those
inputs instead of downloading them from the network.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-03-19 9:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 23:01 [bug#40021] gnu: Add mm-common Raghav Gururajan
2020-03-11 15:24 ` Danny Milosavljevic
2020-03-19 6:34 ` Raghav Gururajan
2020-03-19 9:27 ` Marius Bakke [this message]
2020-03-21 19:21 ` Danny Milosavljevic
2020-03-22 1:16 ` Raghav Gururajan
2020-03-22 11:42 ` Danny Milosavljevic
2020-04-05 4:05 ` Raghav Gururajan
2020-04-05 18:59 ` bug#40021: " 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=877dzgbspj.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=40021@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=raghavgururajan@disroot.org \
/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.