In a rawhide mock chroot when trying to upgrade glibc I observed:
~~~
file /usr/libexec/getconf from install of glibc-2.23.90-15.fc25.i686 conflicts with file from package gcc-6.1.1-1.fc25.i686
~~~
The reason for this is that glibc had different directory permissions than gcc did for the directory (setgid on it for some weird reason, perhaps a bug in mock or the chroot).

No matter the cause it turns out the Fedora Packaging guidelines say gcc should not own /usr/libexec/getconf.

Per Fedora packaging guidelines:
https://fedoraproject.org/wiki/Packaging:Guidelines?rd=Packaging/Guidelines#File_and_Directory_Ownership
~~~
Directory ownership is a little more complex than file ownership. Packages must own all directories they put files in, except for:

* any directories owned by the filesystem, man, or other explicitly created -filesystem packages

* any directories owned by other packages in your package's natural dependency chain 
~~~

The second bullet applies. GCC should not own /usr/libexec/getconf because the directory is owned by GCC's natural dependency on glibc which installs the various getconf binaries in that location.

I expect the fix is as easy as this:

diff --git a/gcc.spec b/gcc.spec
index 741558c..5816172 100644
--- a/gcc.spec
+++ b/gcc.spec
@@ -2449,7 +2449,6 @@ fi
 %{_prefix}/lib/gcc/%{gcc_target_platform}/%{gcc_version}/liblsan.so
 %endif
 %endif
-%dir %{_prefix}/libexec/getconf
 %{_prefix}/libexec/getconf/default
 %doc gcc/README* rpm.doc/changelogs/gcc/ChangeLog* 
 %{!?_licensedir:%global license %%doc}
---