other #warning later down, but the first one seems to have caused an error (the answer is, of course (gah!), sysconf…)