On Tue, 29 Apr 2003 15:32:00 +1000, Steve Youngs <youngs(a)xemacs.org> said:
|--==> "VK" == Valdis Kletnieks
VK> So far, it does:
VK> For gcc, report version and specfile.
OK, what does knowing where the spec file is at tell us?
On systems where gcc is not the native compiler, the spec file path
encodes the system state at the time gcc was built.
XEmacs 21.5-b12 "carrot" configured for `sparc-sun-solaris2.8'.
Compiler specs file: /usr/local/lib/gcc-lib/sparc-sun-solaris2.6/2.8.1/specs
Yep. this one almost certainly has at *least* a 'fixincludes' problem...
I've thwapped the guy in the next cubicle already.
*THAT* was why I included the specfile path.. ;)
Excellent! But why make the distinction of Linux distribution? I
don't know of any distro that doesn't use GNU libc. So surely if you
can get the libc version in RedCrap/Mandunny, you can get it for any
Well.. for RedHat/Mandrake, I just cheat and do 'rpm -q glibc' to get
something a *bit* more specific than 'libc.so.6' (for starters, it's still
called libc.so.6 even under glibc 2.3.2 which has all the TLS stuff).
A co-worker is going to feed me the Debian and Suse checks, and if it's
none of those, I'll probably resort to 'ldd /bin/ls | grep' of some sort.