Date: Wed, 14 Nov 2012 09:01:55 +0200 From: Daniel Braniss <danny@cs.huji.ac.il> To: Mateusz Guzik <mjguzik@gmail.com>, freebsd-current@freebsd.org, avg@freebsd.org Subject: Re: compiler info in kernel identification string Message-ID: <E1TYWyx-0003b5-CF@kabab.cs.huji.ac.il> In-Reply-To: <20121113234303.GA15319@dft-labs.eu> References: <20121113234303.GA15319@dft-labs.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
> Hello, > > avg@ suggested to include compiler version in the kernel so that it's > present in uname (and one can easly tell what was used to compile it). > > Here is my attempt: > http://people.freebsd.org/~mjg/patches/newvers-compiler.diff > > Basically adds compiler name and version/revision after revision of > system sources. > > Sample output from dirty git sources: > gcc: > FreeBSD 10.0-CURRENT #7 r242962=264d569-dirty(gcc-4.2.1-20070831): Wed > Nov 14 00:11:51 CET 2012 > > clang: > FreeBSD 10.0-CURRENT #8 r242962=264d569-dirty(clang-r162107): Wed Nov 14 > 00:12:26 CET 2012 > > Sample output from svn with gcc: > FreeBSD 10.0-CURRENT #1 r243006:243007M(gcc-4.2.1-20070831): Wed Nov 14 > 00:41:23 CET 2012 > > I have no strong opinions on format, I just want this information easly > accessible. > > Comments? in the old days (I'm talking before C :-) I remmeber one compiler putting such info in the code it produced, I wonder if that's the case with gcc/clang, and if so it would be nice if file(1) could show it. my 3c, danny
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1TYWyx-0003b5-CF>