From owner-freebsd-current@FreeBSD.ORG Fri Nov 16 10:43:28 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 60EA5679; Fri, 16 Nov 2012 10:43:28 +0000 (UTC) (envelope-from erik@cederstrand.dk) Received: from csmtp3.one.com (csmtp3.one.com [91.198.169.23]) by mx1.freebsd.org (Postfix) with ESMTP id E837B8FC16; Fri, 16 Nov 2012 10:43:27 +0000 (UTC) Received: from [192.168.187.69] (unknown [87.54.33.251]) by csmtp3.one.com (Postfix) with ESMTPA id 4788D2406AE7; Fri, 16 Nov 2012 10:43:21 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: compiler info in kernel identification string From: Erik Cederstrand In-Reply-To: <50A612F9.30509@FreeBSD.org> Date: Fri, 16 Nov 2012 11:43:22 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <0D736126-2E72-4C6E-BDF4-094E0C744D25@cederstrand.dk> References: <20121113234303.GA15319@dft-labs.eu> <50A3639C.9050200@FreeBSD.org> <1352907497.1217.147.camel@revolution.hippie.lan> <50A57623.4020108@FreeBSD.org> <50A5EC7C.5050303@FreeBSD.org> <5B4DE1FD-5DD3-49A5-B8DB-6D4C03ABD742@cederstrand.dk> <50A606E7.5000302@FreeBSD.org> <50A612F9.30509@FreeBSD.org> To: Andriy Gapon X-Mailer: Apple Mail (2.1499) Cc: Ian Lepore , Mateusz Guzik , Dimitry Andric , freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Nov 2012 10:43:28 -0000 Den 16/11/2012 kl. 11.18 skrev Andriy Gapon : > This is starting to turn into a bikeshed, but anyway... >=20 > on 16/11/2012 12:00 Daniel Braniss said the following: >> the question as to what compiler was used to compile the kernel is a = bit of an >> oxymoron, since the kernel is made up of many different modules, = which get=20 >> compiled >> either by different compilers, or different compiler flags. >=20 > The canonical way to compile a kernel is to use buildkernel and = compile modules > along with the kernel. Other configurations are supported too, of = course. >=20 >> since the compiler does 'sign' the modules it compiles (and clang = will/should >> do it soon: http://llvm.org/bugs/show_bug.cgi?id=3D7292) some tool = like >> file(1) could be modified to provide it, or config -x (8) ... >=20 > The key word in your note about clang is 'soon' as in 'not yet'. >=20 > Besides, when I see a bug report with a dmesg *I* want to immediately = know what > compiler was used there. But wouldn't you want to know the compiler flags, too? And the kernel = config file? src.conf? Local patches? To solve a bug, in general you = would want sufficient information to recreate the environment locally. = Compiler version is not enough. So either you have all information in every binary, because they might = have been built outside a buildworld, or you have the general buildworld = / buildkernel configuration in a central place and expect users to = supply information about whatever non-standard setup they did. Erik=