I recently ran into a problem where I had trouble determining why the setgid bit was set in my rootfs. It turns out that debian has this bit set on /usr/local (where I was building from), and thus inherited this bit from that directory tree.
Fixed in master with http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=3134ae11270dae9d8dddc5a16e2321b675b5d522
Verified on master commit: 8ac8eca2e3bd8c78e2b31ea974930ed0243258a3 Host : Debian 3.14.13-2, x86_64
Verified on master commit: 8ac8eca2e3bd8c78e2b31ea974930ed0243258a3 Host : Debian 3.14.13-2, x86_64 Reproducing steps (method 1): 1. in poky folder : source oe-init-build-env newbuild 2. ls -ld . 3. chmode g+s . 4. ls -ls ( now now you can see the sticky note (s): drwxr -sr -x ....) 5. bitbake core-image-minimal You will get an error message: "TMPDIR is setgid, please don't build in a setgid directory" (method 2) 1. cd /usr/local 2. sudo mkdir test 3. sudo chown user test 1. in poky folder : source oe-init-build-env /usr/local/test 2. ls -ld . 3. chmode g+s . 4. ls -ls ( now now you can see the sticky note (s): drwxr -sr -x ....) 5. bitbake core-image-minimal You will get an error message: "TMPDIR is setgid, please don't build in a setgid directory"