Note: I agree with ptomato's answer, and leave this answer as Community Wiki.
It makes sense for source code distributions, but your project may not be one.
For development purpose, ptomato's answer makes more sense.
All the C projects generally come with a configure file able to generate the actual Makefile used for the compilation.
So when you consider the autotool chain, I would recommend versioning all files generated up to the configure file, as they are normally a one-time generation operation.

That means anyone with a checked out copy of your version project can immediately start:
./configure
make
make install
So, while it is generally true, you shouldn't version any generated files, you could store those, especially if the other reader from that project can:
What is
edin the above flow chart?!
The ed in the flow chart is likely a placeholder for the text editor used to modify or create the configure.ac and Makefile.am files.
In the context of Autotools, these files are written by a developer to specify the configuration and build instructions for the software. ed is actually one of the standard text editors in Unix and Unix-like systems and represents the concept of editing these files manually.