Re:Tips for C libraries on GNU/Linux
by JoshTriplett on Wednesday November 14, 2012 @11:16AM
(#4783945)
> $ ./autogen.sh
> checking for build system type...
> ^C
>
> No damn, I wanted to generate configure, not run it! How do I clean up the mess it made just now?
I always run "./autogen.sh --help" for exactly that reason; then if I see --help output from configure, I know that autogen.sh "helpfully" ran configure for me.
You can also usually just run "autoreconf -v -f -i" directly, unless the package has done something unusual that it needs to take extra steps in autogen for.
Let's submit this fix upstream. No problem, use diff.
WTF IS ALL THIS MESS IN THE DIFF I NEVER TOUCHED?!!??!I know you're going to say I should be using the VCS checkout in the first place, which would hopefully be configured to ignore the autogenerated files. But as a user, or distribution maintainer, most of the time the bug you find is with a specific, packaged version of the software, and it may be quite an effort to figure out how to get the exact same version from the VCS server.