all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Darrington <john@darrington.wattle.id.au>
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: sockets availability during build
Date: Thu, 22 Jan 2015 21:29:18 +0100	[thread overview]
Message-ID: <20150122202918.GA12207@intra> (raw)
In-Reply-To: <CAKrPhPPFJ02PvNx+NFoRNR2na550_bxhEJJCMTMc1P9Va1sX2Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 883 bytes --]

On Thu, Jan 22, 2015 at 08:54:11PM +0100, Federico Beffa wrote:
     Hi,
     
     I'm working on libupnp. The 'check phase gives the following error:
     
     Initializing UPnP ...
     ** ERROR UpnpInit(): -208 UPNP_E_SOCKET_ERROR
     FAIL: test_init
     
     In spite of this, if I "guix environment" and run the test binary it succeeds:
     
     Initializing UPnP ...
     UPnP Initialized OK ip=192.168.0.5, port=49152
     
     I suppose that sockets can't be accessed during the build phase. Is
     that correct?

local sockets (AF_UNIX) can be.  But the only Internet sockets accessible are those on the local (lo) interface.
All other interfaces are disabled.

J'

-- 
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2015-01-22 20:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-22 19:54 sockets availability during build Federico Beffa
2015-01-22 20:29 ` John Darrington [this message]
2015-01-23  8:38 ` Ludovic Courtès
2015-01-23 17:37   ` Federico Beffa
2015-01-23 21:31     ` Ludovic Courtès
2015-01-24 14:05       ` Federico Beffa

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=20150122202918.GA12207@intra \
    --to=john@darrington.wattle.id.au \
    --cc=beffa@ieee.org \
    --cc=guix-devel@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.