On 05/15/2013 04:12 PM, Mauro Carvalho Chehab wrote:
> I am reading rasdaemon-0.2.0 sources right now.
> Indeed this answers my question about data capture.
> You have it there.
> The task of collecting and reporting EDAC errors
> naturally splits into collecting and reporting parts,
> and the collecting part is well covered by now
> (by you and other guys).
Yes. Btw, I just added there some code for getting PCIe AER
errors (still needs testing, so this feature needs to be
I'm also intending to add today some code to collect MCE
traces, as we want to be able to replace mcelog by this tool
in the long term.
I modified the source to try my idea of reporting helper.
Unfortunately, I can't build it, autoconf isn't happy:
$ autoconf -f
configure.ac:11: error: possibly undefined macro: X_AC_META
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
$ autoconf --version
autoconf (GNU Autoconf) 2.69
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+/Autoconf: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by David J. MacKenzie and Akim Demaille.
$ rpm -qf `which autoconf`
Please let me know how do you generate ./configure,
and what version of autoconf et.al. do you have on your system.