Hey Benny!

In the case of whether or not 32 or 64 bit, try 'file /lib/libc-2.23.so'
instead.  It will tell the tale such as the output below on my newest
experimental system;

----- ':read !file /lib/libc-2.26.90.so' starts
/lib/libc-2.26.90.so: ELF 64-bit LSB shared object, x86-64, version 1
(GNU/Linux), dynamically linked, interpreter /lib/ld-linux-x86-64.so.2, for
GNU/Linux 4.9.0, not stripped
----- ':read !file /lib/libc-2.26.90.so' ends

Note the 'ELF 64-bit LSB shared object' part but also 'interpreter
/lib/ld-linux-x86-64.so.2'.

Note the location is in /lib and not /lib64 which is the usual location in most
if not all linux distributions.  Another reason why I prefer growing my own. 
For 32 bit glibc the location will be /lib and the interpreter will be
/lib/ld-linux.so.2 which is a dead giveaway for 32 bit libs.  Multilib will
have both a /lib/libc-version.so and a /lib64/libc-version.so but each one will
have a different interpreter, /lib/ld-linux.so.2 and
/lib64/ld-linux-x86-64.so.2 on the same system.

Life is good,
Maurice

... Don't cry for me I have vi.
--- GNU bash, version 4.4.12(1)-release (x86_64-silvermont-linux-gnu)