Self hosting issue: mlibc logging interferes with configure if mlibc is configured to log to stdout / stderr

We observed this while configuring gcc on linux mlibc in a chroot. The issue is that `sys_libc_log` on linux logs to fd 1, interfering with configure. We should log to a file and make that configurable with an environment variable.