> As I said, it should be obvious. 11 out 11 hunks fail, and I can visually in > less than 1 minute find two syntax errors.
I get also an error message like "11 out 11 hunks fail" on my openSUSE system if the command "patch" is used for my update file. The command "git-apply" should be used instead. I mentioned the following issue in my bug report. http://bugs.bacula.org/view.php?id=1415 I guess that the file "configure.in" should be moved to the parent directory so that the command "autoreconf" will use it, shouldn't it? ⇒ git mv gui/autoconf/configure.in gui/ && git mv bacula/autoconf/configure.in bacula/ && git apply ../1415a.diff > The original "hack" is far more transparent. I have got the impression that it does not fit to the current autoconf release any more like the parameters are documented for the macro "AC_INIT". > will keep the original code rather than spend any more time on this. The command "autoscan" will show a couple of warnings for missing configuration checks. Would anybody like to fix them? Should the macro "AC_PREREQ" be called at the beginning? The parameter quoting can also be improved. > I give up. This might be too early. How do you think about to rename any file extensions from ".in" to ".ac" and ".am"? Regards, Markus ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
