On Sun, Dec 23, 2012 at 03:18:14PM +0200, Andriy Gapon wrote:
> on 15/11/2012 22:43 Andriy Gapon said the following:
> > on 14/11/2012 01:43 Mateusz Guzik said the following:
> >> Hello,
> >>
> >> avg@ suggested to include compiler version in the kernel so that it's
> >> present in uname (and one c
on 15/11/2012 22:43 Andriy Gapon said the following:
> on 14/11/2012 01:43 Mateusz Guzik said the following:
>> 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:
>> h
On 16 Nov 2012, at 07:41, Dimitry Andric wrote:
> And regarding clang, I don't have the time to implement this very soon,
> and I doubt it is very high on the bug priority list with upstream
> either. They just branched for the 3.2 release, and they are much
> busier squashing bugs now. :)
Imple
On 2012-11-16 11:00, Daniel Braniss wrote:
on 16/11/2012 11:20 Erik Cederstrand said the following:
Den 16/11/2012 kl. 08.34 skrev Andriy Gapon :
...
hostname, username, timestamp, absolute path etc. are a nuisance if they
can't be turned off with -fno-ident, -frandom-seed, -DSTRIP_FBSDID, ar
BeBei
Sent from my HTC Velocity 4G on the Next G network
- Reply message -
From: "Erik Cederstrand"
To: "Andriy Gapon"
Cc: "Ian Lepore" , "Mateusz Guzik"
, "Dimitry Andric" ,
Subject: compiler info in kernel identification string
on 16/11/2012 12:54 Daniel Braniss said the following:
>>
>> This is starting to turn into a bikeshed, but anyway...
>>
>> 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
[cc list trimmed]
on 16/11/2012 12:43 Erik Cederstrand said the following:
> Den 16/11/2012 kl. 11.18 skrev Andriy Gapon :
>
>> This is starting to turn into a bikeshed, but anyway...
>>
>> on 16/11/2012 12:00 Daniel Braniss said the following:
>>> the question as to what compiler was used to c
>
> This is starting to turn into a bikeshed, but anyway...
>
> 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
> > compil
Den 16/11/2012 kl. 11.18 skrev Andriy Gapon :
> This is starting to turn into a bikeshed, but anyway...
>
> 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
This is starting to turn into a bikeshed, but anyway...
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
> compiled
> either by diff
> on 16/11/2012 11:20 Erik Cederstrand said the following:
> > Den 16/11/2012 kl. 08.34 skrev Andriy Gapon :
> >
> >> 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 informa
on 16/11/2012 11:20 Erik Cederstrand said the following:
> Den 16/11/2012 kl. 08.34 skrev Andriy Gapon :
>
>> 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 t
Den 16/11/2012 kl. 08.34 skrev Andriy Gapon :
> 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
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 con
on 16/11/2012 01:05 Dimitry Andric said the following:
> For starters, this hardcodes the compiler names "gcc" and "clang", and
> this will include incorrect information into the kernel version string,
> if you use another setting for ${CC}.
Oops, I agree. The script should definitely make use of
On Fri, Nov 16, 2012 at 12:05:33AM +0100, Dimitry Andric wrote:
> For starters, this hardcodes the compiler names "gcc" and "clang", and
> this will include incorrect information into the kernel version string,
> if you use another setting for ${CC}.
>
Yes, I blindly assumed that both gcc and cla
On 2012-11-14 16:38, Ian Lepore wrote:
On Wed, 2012-11-14 at 10:25 +0100, Dimitry Andric wrote:
...
That way, you are sure never to lose information. This also works for
gcc from ports (which is the reason for the space after 'version' in the
grep command):
$ gcc47 -v 2>&1 | grep 'version
On 2012-11-15 21:43, Andriy Gapon wrote:> on 14/11/2012 01:43 Mateusz Guzik
said the following:
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
on 14/11/2012 01:43 Mateusz Guzik said the following:
> 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
On Tue, Nov 13, 2012 at 03:57:55PM -0800, David Wolfskill wrote:
> I like the idea, but I have long found the idea of putting this type of
> logic (including VCS-awareness) in newvers.sh itself something that is
> prone to turn what should be a rather simple script into a ... mess.
I don't think n
On Wed, 2012-11-14 at 10:25 +0100, Dimitry Andric wrote:
> On 2012-11-14 00:43, Mateusz Guzik wrote:
> > 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.fre
On 2012-11-14 08:01, Daniel Braniss wrote:
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,
As far as I know, gcc has always includ
On 2012-11-14 00:43, Mateusz Guzik wrote:
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 an
> 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
good idea.
show version cmd in postgresql prints os version,compiler info etc. useful
for problem report.
jov
在 2012-11-14 上午7:43，"Mateusz Guzik" 写道：
> 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 comp
Hi,
On Wed, 14 Nov 2012 00:43:03 +0100
Mateusz Guzik wrote:
> 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-compi
On Wed, Nov 14, 2012 at 12:43:03AM +0100, Mateusz Guzik wrote:
> 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-compi
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
28 matches
Mail list logo
