Should homebrew link binutils without the "g" prefix?

When I link binutils I expected all the binaries to be linked with the g prefix. Instead, homebrew links raw binaries along with prefixed ones:

~ $ brew link binutils --dry-run
Would link:
/usr/local/bin/addr2line
/usr/local/bin/ar
/usr/local/bin/c++filt
/usr/local/bin/coffdump
/usr/local/bin/dlltool
/usr/local/bin/dllwrap
/usr/local/bin/elfedit
/usr/local/bin/gaddr2line
/usr/local/bin/gar
/usr/local/bin/gc++filt
/usr/local/bin/gcoffdump
/usr/local/bin/gdlltool
/usr/local/bin/gdllwrap
/usr/local/bin/gelfedit
/usr/local/bin/gnm
/usr/local/bin/gobjcopy
/usr/local/bin/gobjdump
/usr/local/bin/granlib
/usr/local/bin/greadelf
/usr/local/bin/gsize
/usr/local/bin/gsrconv
/usr/local/bin/gstrings
/usr/local/bin/gstrip
/usr/local/bin/gsysdump
/usr/local/bin/gwindmc
/usr/local/bin/gwindres
/usr/local/bin/nm
/usr/local/bin/objcopy
/usr/local/bin/objdump
/usr/local/bin/ranlib
/usr/local/bin/readelf
/usr/local/bin/size
/usr/local/bin/srconv
/usr/local/bin/strings
/usr/local/bin/strip
/usr/local/bin/sysdump
/usr/local/bin/windmc
/usr/local/bin/windres

I’m curious is it expected behavior or a bug? Are there any valid use cases when someone needs binutils linked w/o prefix? Keep in mind that we have gcc only with postfix.

To give you more context, the colleague of mine experienced an error trying to compile ruby. After the debug session, we realized that binutils is installed and linked. So we use clang compiler with GNU ar which are not supposed to work together.

Hi, Dmitry. Your binutils is linked into your prefix. It shouldn’t be, because it’s marked as being keg-only. Try brew unlink binutils or brew reinstall binutils.

Cheers,
Shaun