Guys, I've installed 5.8 chroot on 5.9-beta as of January 2016. I've removed /etc/resolve.conf after installing few packages and give MICO build a try. I've duplicated issue of assert in address.cc:555 since hostname is not resolvable. I've been able to solve this assert by putting:
-ORBIIOPAddr inet:127.0.0.1:0 -ORBNoResolve into some file and then: export MICORC=<this file from above> E.g. $ echo "-ORBIIOPAddr inet:127.0.0.1:0 -ORBNoResolve" > /tmp/mico-build.rc $ export MICORC=/tmp/mico-build.rc this instructs MICO to load configuration options for its initialization from the file, so basically -ORBIIOPAddr inet:127.0.0.1:0 -ORBNoResolve are used for all IDL compiler invocations. Those two options means: bind to 127.0.0.1, system selected port and do not attempt to resolve name for this address to get some meaningful name. I think this should be enough even for Marc's builder but if you put even more limits on your builders like for example can't create tcp socket, then I should be able to instruct MICO to use unix pipes instead -- hopefully those will be allowed at the end. :-) Please let me know if this solves the issue for you. Thanks! Karel On Fri, Mar 11, 2016 at 12:26 PM, Stuart Henderson <[email protected]> wrote: > On 2016/03/11 11:22, Karel Gardas wrote: >> On Thu, Mar 10, 2016 at 10:28 PM, Marc Espie <[email protected]> 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... > > I think we could reasonably expect "localhost" to be resolvable > forwards and backwards, but the hostname is system-wide and returned > by a system call, you can't have a different one inside chroot. >
