gcc-config called ldconfig without any path, giving ability for a user to add an ldconfig that root might run when using gcc-config. grep ldconfig /usr/bin/gcc-config -n 325: # If we previously had stuff in /, make sure ldconfig gets re-run. 481: ldconfig It should called /sbin/ldconfig Reproducible: Always
no explanation as to how this could possibly be a problem. you could make the same argument for cp, mv, touch, sed, env-update, or any other program.
i assume if you make an ldconfig in a directory with +x the call for ldconfig might run that version instead of /sbin one. i was wrong, something i should have try before. sorry for the noise.