https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64094
--- Comment #4 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- My preference would be a gnulib/glibc/libiberty function that all GNU utilities could use to give more precise error messages (open_strerror(int errnum, int flags)?). Then, perhaps update the Coding Standards to recommend the use of the function. Then, use it in GCC and binutils for consistency (and to avoid translating the same string for each project). The benefit may seem minor to many people (and I guess all existing GCC devs have things to work on that they consider much more crucial). However, somebody went through all the trouble to report a bug, so I would not want to discourage anyone from going ahead and do whatever is needed. Maybe then they will decide to tackle other problems with GCC/binutils (there are plenty to choose from, and help is always welcome). I would like to encourage people to work on GCC, even if, to me, the benefit does not compensate the effort, they may have other priorities. A good example of this is: https://gcc.gnu.org/ml/gcc/2014-10/msg00104.html where someone proposed a controversial change, but a path forward to a solution was offered. That person followed up and a patch is almost ready to be merged: https://gcc.gnu.org/ml/gcc-patches/2014-11/msg00845.html
