On Thu, Mar 10, 2016 at 3:13 PM, Marc Espie <es...@nerim.net> wrote: > On Thu, Mar 10, 2016 at 11:53:56AM +0100, Karel Gardas wrote: >> This is a sign of not so correct network configuration. MICO is really >> picky about it so it should be able to resolve your host name/IP >> address. What's failing precisely in the assert above is that it's not >> able to get IP for your hostname. Can you confirm that this is the >> case? > > Nope. This is the only port in the tree that doesn't like it when you cut > network access during build (which proper build machines have started doing > for a while now).
This would be strange since I commonly build MICO w/o any internet connection. > I've looked a bit further, and that stupid test is so deep embedded within > the mico code itself that it will be a pain to fix. Indeed, it is, but I guess this was done for a good reason in the past and I would rather keep it this way. What I can certainly do for 2.3.14 release is to add some clear error message pointing to the incorrect network configuration.
