<phant0mas>you told me you used to write drivers right?
<phant0mas>do you have any good books in your mind that I could read?
<mark_weaver>phant0mas: what kernel do you need to write the drivers for? Linux?
<mark_weaver>I guess that Linux Device Drivers <https://lwn.net/Kernel/LDD3/> is probably a good resource, but it's quite out-of-date. Linux is evolving very quickly, and in practice driver authors just have to keep up on the changes to the internal APIs incrementally.
<mark_weaver>ggrant: one thing: I recommend passing --system to useradd. we fixed that in the manual in git master, but it's not in the manual of the most recent release (0.5)
<mark_weaver>(that makes it so that the build users won't show up in the graphical login window)
<ggrant>mark_weaver: Well now, I'm not even getting to that point. When running the bootstrap, I get "autoreconf: running: /usr/bin/autoconf --force configure.ac:51: error: possibly undefined macro: PKG_CHECK_MODULES If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation."
<zerwas>I think I had the same error recently. Unfortunately I can't remember the solution. Maybe it was running libtoolize
<mark_weaver>ggrant: it's easier if you initially build from a tarball instead of from git.
<mark_weaver>strange. that should be in the default path where the autotools look. well, for now, you could: export ACLOCAL_PATH=/usr/share/aclocal and try running bootstrap again.
*mark_weaver suspects that either the fedora autotools are configured to look in the wrong place, or that their pkg-config package is installing pkg.m4 in the wrong place. somehow, those two things are lining up.