On Thu, Mar 10, 2016 at 10:28 PM, Marc Espie <es...@nerim.net> wrote:
>> 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.
>
> It's not an incorrect network configuration, actually. It's just no
> resolving
> some things on localhost.
>
> mico is the only port that wants this. Everything else works peachy.
>
> I've got a very paranoid setup on my build machines.
> I just have:
> block out quick proto {tcp,udp} from self user pbuild0
>
> oh, and the build is chroot'd to a place that only knows about localhost.
>
> No other port in the trees ever tries to resolve `hostname` during build.
is it a big problem to set hostname to localhost in such chroot and
have localhost resolvable to 127.0.0.1 and 127.0.0.1 back to
localhost?
Just asking. The possibility is that -ORBNoResolve works in such case
and if so we may add it into IDL compiler main.cc as a parameter
specifically for OpenBSD. If this works well I may even relax this
condition for IDL compiler on all platforms or specifically test if
the issue is present and then switch NoResolve on...
