Closed nachokb closed 11 years ago
That patch doesn't make any sense to me, sorry. Can you describe what exactly does not work in your case? Why do you call autogen.sh if you already configured the project? The instructions are for people building from tar-balls, not for people building from git.
If you build from a tar-ball, but the tar-ball was created from git, then "configure" will not be present and you should call ./autogen.sh. However, if it is a release-tar-ball, I will have created these via "make dist" and, thus, "./configure" will already be generated and there is no reason to call ./autogen.sh.
People building from git, that is, updating the sources regularly should call ./autogen.sh whenever the build-files get updated (as usual with autotools). There is no proper way to automate this (that I am aware of).
I can add a note that this is only for tar-ball builds, if that's what confused you?
Cheers David
ok, I just pulled a newer version and the install instructions didn't work...
as I was updating from a months older version, I didn't know (or did not care to find out) if there were changes in the build (in fact, it was rather probable) so it made sense to run it... the first line just didn't work.
Probably, build files had changed and the first line detected the file existed so it didn't run configure. Just realized how stupid it was to leave that first line (didn't even read it).
Thanks for everything!!
installation instructions were not working, at least if you already configured the project previously...