Re: compiler info in kernel identification string
Chris Hoy Poy
kryanth at staff.gopc.net
Fri Nov 16 10:00:42 UTC 2012
Sent from my HTC Velocity 4G on the Next G network
----- Reply message -----
From: "Erik Cederstrand" <erik at cederstrand.dk>
To: "Andriy Gapon" <avg at freebsd.org>
Cc: "Ian Lepore" <freebsd at damnhippie.dyndns.org>, "Mateusz Guzik" <mjguzik at gmail.com>, "Dimitry Andric" <dim at FreeBSD.org>, <freebsd-current at FreeBSD.org>
Subject: compiler info in kernel identification string
Date: Fri, Nov 16, 2012 5:21 pm
Den 16/11/2012 kl. 08.34 skrev Andriy Gapon <avg at freebsd.org>:
> on 16/11/2012 01:09 Dimitry Andric said the following:
>> And as I remarked in another reply, now that I have thought about it a
>> bit, I would much rather see this information moved to a sysctl or dmesg
>> line, than in uname. With the happy side effect that no existing uname
>> parsers would be confused!
> I would still like to have at least compiler's "base name" or type or something
> in uname.
This has been brought up before, but what about putting all this in a separate file, e.g. /etc/buildinfo?
At least I'd like this to be configurable. I'm trying to get FreeBSD code in a shape where it can optionally produce deterministic binaries from two different builds (i.e. comparable with md5) as long as the binaries are functionally equivalent, and "irrelevant" info like compiler version, hostname, username, timestamp, absolute path etc. are a nuisance if they can't be turned off with -fno-ident, -frandom-seed, -DSTRIP_FBSDID, ar -D and the like.
freebsd-current at freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
More information about the freebsd-current