From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 27894-done@debbugs.gnu.org
Subject: bug#27894: Building Guix fails without '/etc/services'
Date: Tue, 1 Aug 2017 15:39:19 -0400 [thread overview]
Message-ID: <20170801193919.GA31569@jasmine.lan> (raw)
In-Reply-To: <87mv7jr453.fsf@gnu.org>
On Tue, Aug 01, 2017 at 12:09:12PM +0200, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
>
> > On a system that lacks '/etc/services' (CoreOS), building Guix from
> > source fails because getaddrinfo() doesn't know how to proceed:
> >
> > ERROR: In procedure getaddrinfo: Servname not supported for ai_socktype
> >
> > I worked around this issue by downloading the binaries by hand with
> > curl.
>
> You get the error above when running “make”, which in turn runs
> build-aux/download.scm, right?
>
> If so, I think this can be worked around with:
>
> diff --git a/build-aux/download.scm b/build-aux/download.scm
> index 8dfa91460..5cb2491dc 100644
> --- a/build-aux/download.scm
> +++ b/build-aux/download.scm
> @@ -31,7 +31,7 @@
> (guix hash))
>
> (define %url-base
> - "http://alpha.gnu.org/gnu/guix/bootstrap"
> + "http://alpha.gnu.org:80/gnu/guix/bootstrap"
>
> ;; Alternately:
> ;;"http://www.fdn.fr/~lcourtes/software/guix/packages"
>
> However, the whole point of /etc/services is so that application writers
> don’t have to hard-code port number everywhere. So I’d be tempted to
> say this is not a bug.
>
> WDYT?
I think it's fair to say it's not a bug. Perhaps if we get more reports
from users of this system we can reconsider.
next prev parent reply other threads:[~2017-08-01 19:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 0:23 bug#27894: Building Guix fails without '/etc/services' Leo Famulari
2017-08-01 10:09 ` Ludovic Courtès
2017-08-01 19:39 ` Leo Famulari [this message]
2020-02-11 20:10 ` Jonathan Brielmaier
2020-02-11 20:40 ` Julien Lepiller
2020-02-11 20:50 ` Jonathan Brielmaier
2020-02-24 16:51 ` 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=20170801193919.GA31569@jasmine.lan \
--to=leo@famulari.name \
--cc=27894-done@debbugs.gnu.org \
--cc=ludo@gnu.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.