Comment 11 for bug 933045

@Andy,

note that the bug is not about AT_EMPTY_PATH being undefined, but about build failure when both <fcntl.h> and <linux/fcntl.h> are included. Unless there is some guidance (beyond "it causes this bug") why that shouldn't be done, in which case I need to justify the reason why I need to do that...

Otherwise I can go back and figure out why ther were no problems before the new glibc... My guess would be that <bits/fcntl.h> existed before (which is included by <fcntl.h>) and it #included <linux/fcntl.h>. But I haven't spooled up an image to verify that.