Does anyone read the installation instructions?
Yes, but not everyone. And even people that read the docs can miss the info if they can't figure out which part of the docs they are supposed to be looking at.
If you don't want people sending bug reports like this, then you idiot proof it by adding a configure test. Maybe even something like the attached.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
Index: config.gcc
===================================================================
RCS file: /cvs/gcc/gcc/gcc/config.gcc,v
retrieving revision 1.529
diff -p -r1.529 config.gcc
*** config.gcc 4 Apr 2005 17:18:49 -0000 1.529
--- config.gcc 22 Apr 2005 07:44:06 -0000
*************** case ${target} in
*** 366,371 ****
--- 366,377 ----
case ${enable_threads} in
"" | yes | posix) thread_file='posix' ;;
esac
+ # Verify the cctools version number.
+ cctools=`cat /dev/null | as -v 2>&1 | grep cctools-576`
+ if test x"$cctools" = x; then
+ echo "*** Please update cctools version from gcc.gnu.org ftp site." >&2
+ exit 1
+ fi
;;
*-*-freebsd[12] | *-*-freebsd[12].* | *-*-freebsd*aout*)
# This is the place-holder for the generic a.out configuration
