Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

i've renamed to NailgunStreamStdinWriter, since it writes to the NailgunStream

this docker engine build failure is baffling

if I cd into the docker env and invoke the failing `cc` command directly it succeeds

have we not `cd`ed? i remember that was relevant in one case.

bootstrap `cd`s into the workspace before running cargo

there are two empty quotes in there... relevant?: ` "" "" `

at this point its failing on a `(cd $OS_PANTS_SRC &amp;&amp; ./pants)` tho

waiting on the rust build to fail and will retry w/ those

```$ cat ""
cat: : No such file or directory```

repros in a vanilla docker image too, so I think this is an upstream issue

```[omerta ~]$ docker run --rm -t -i centos:centos7 /bin/sh -i
sh-4.2# yum install -qy git gcc python python-devel openssl which
...
sh-4.2# git clone <http://github.com/pantsbuild/pants>
...
sh-4.2# ./pants
```

some environment variable getting splatted out ?

looks like the extra spaces exist in the cflags in the same position, so my guess is that the vanilla python used on centos7 has these in its build config

trying against EE Python in our docker image

prob a case of better handling needed in master tho