A better solution, I think, is to advise the people who release
patches to always patch the Makefile.in instead of the Makefile
itself. The Makefile is automatically generated by 'configure' and
should never be manually modified.
The Makefile.in is (almost) the same as the Makefile; just make your
changes there and then rerun the program 'config.status'. (This is
the Makefile-generator that is created when you run 'configure').
George writes:
>The most common failure when patching is Makefile and yes, you have to run
>configure first. Don't worry too much about Makefile rejecting, just add
>the rejects by hand. As for the not finding a patch, try adding a -u
>switch to see if they'll do unified diffs. If not go get a real patch
>program.
>
> --
>George Greer - Me@Null.net | Genius may have its limitations, but stupidity
>http://www.van.ml.org/~greerga | is not thus handicapped. -- Elbert Hubbard
>
>
> +------------------------------------------------------------+
> | Ensure that you have read the CircleMUD Mailing List FAQ: |
> | http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |
> +------------------------------------------------------------+
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/08/00 PST