public
/
nixpkgs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
nixpkgs/pkgs/os-specific/linux/mcelog/default.nix

28 lines
670 B
Nix
Raw Normal View History

mcelog 1.0pre-7fa9981 -> 114
2015-04-16 15:42:45 -07:00
{ stdenv, fetchFromGitHub }:
mcelog: a tool to access the machine check exceptions logged by the kernel. The kernel indicated that machine check exceptions were logged, but did not tell what kind of exceptions. In my case, this is usually the processor being throttled because it gets too hot (laptop...), but it may also be more severe problems. Anyway, with this tool you can access these logs. svn path=/nixpkgs/trunk/; revision=32547
2012-02-24 12:20:59 -08:00
mcelog 1.0pre-7fa9981 -> 114
2015-04-16 15:42:45 -07:00
let version = "114"; in
stdenv.mkDerivation {
mcelog: a tool to access the machine check exceptions logged by the kernel. The kernel indicated that machine check exceptions were logged, but did not tell what kind of exceptions. In my case, this is usually the processor being throttled because it gets too hot (laptop...), but it may also be more severe problems. Anyway, with this tool you can access these logs. svn path=/nixpkgs/trunk/; revision=32547
2012-02-24 12:20:59 -08:00
name = "mcelog-${version}";
mcelog 1.0pre-7fa9981 -> 114
2015-04-16 15:42:45 -07:00
src = fetchFromGitHub {
sha256 = "1blxz5ilrlh2030gxmfqlhcb53qh2bxp5nxyc97m1z8a52idjh0v";
rev = "v${version}";
repo = "mcelog";
owner = "andikleen";
mcelog: a tool to access the machine check exceptions logged by the kernel. The kernel indicated that machine check exceptions were logged, but did not tell what kind of exceptions. In my case, this is usually the processor being throttled because it gets too hot (laptop...), but it may also be more severe problems. Anyway, with this tool you can access these logs. svn path=/nixpkgs/trunk/; revision=32547
2012-02-24 12:20:59 -08:00
};
makeFlags = "prefix=$(out) etcprefix=$(out) DOCDIR=$(out)/share/doc";
Fixing mcelog, so it puts the proper files in share/doc It was running "cp mce.pdf $out/share/doc", which created the file 'doc'. Then buildEnv complained that 'share/doc' exists.
2013-01-20 09:51:41 -08:00
preInstall = ''
mcelog 1.0pre-7fa9981 -> 114
2015-04-16 15:42:45 -07:00
mkdir -p $out/share/{doc,man/man{5,8}}
Fixing mcelog, so it puts the proper files in share/doc It was running "cp mce.pdf $out/share/doc", which created the file 'doc'. Then buildEnv complained that 'share/doc' exists.
2013-01-20 09:51:41 -08:00
'';
mcelog 1.0pre-7fa9981 -> 114
2015-04-16 15:42:45 -07:00
meta = with stdenv.lib; {
inherit version;
description = "Log machine checks (memory, IO, and CPU hardware errors)";
mcelog: a tool to access the machine check exceptions logged by the kernel. The kernel indicated that machine check exceptions were logged, but did not tell what kind of exceptions. In my case, this is usually the processor being throttled because it gets too hot (laptop...), but it may also be more severe problems. Anyway, with this tool you can access these logs. svn path=/nixpkgs/trunk/; revision=32547
2012-02-24 12:20:59 -08:00
homepage = http://mcelog.org/;
mcelog 1.0pre-7fa9981 -> 114
2015-04-16 15:42:45 -07:00
license = with licenses; gpl2;
maintainers = with maintainers; [ nckx ];
mcelog: a tool to access the machine check exceptions logged by the kernel. The kernel indicated that machine check exceptions were logged, but did not tell what kind of exceptions. In my case, this is usually the processor being throttled because it gets too hot (laptop...), but it may also be more severe problems. Anyway, with this tool you can access these logs. svn path=/nixpkgs/trunk/; revision=32547
2012-02-24 12:20:59 -08:00
};
Fixing mcelog, so it puts the proper files in share/doc It was running "cp mce.pdf $out/share/doc", which created the file 'doc'. Then buildEnv complained that 'share/doc' exists.
2013-01-20 09:51:41 -08:00
}