>2) Patch to src/configure.in
>This patch can be included as is into pike, I think this was is a bug in
>configure.in because it originally tries to use the newly build pike
>instead of the pike installed on the host.

If the diff is manageable I prefer to patch configure and avoid
depending on and running autoconf. I suppose that's the only reason
for the last hunk of rules.diff.

How do you ensure that pike is installed on the host system before
cross-compiling for other architectures?

>4) Patch to src/modules/Mysql/configure
>I think this patch was already included in src/modules/Mysql/configure.in.

That one looks reversed.
            • ... Martin Stjernholm, Roxen IS @ Pike developers forum
            • ... Magnus Holmgren, Millnet/Lysator/Debian/Mensa @ Pike developers forum
            • ... Magnus Holmgren, Millnet/Lysator/Debian/Mensa @ Pike developers forum
        • ... Martin Stjernholm, Roxen IS @ Pike developers forum
          • ... Magnus Holmgren, Millnet/Lysator/Debian/Mensa @ Pike developers forum
            • ... Martin Stjernholm, Roxen IS @ Pike developers forum
    • ... Magnus Holmgren, Millnet/Lysator/Debian/Mensa @ Pike developers forum
      • ... Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum
        • ... Magnus Holmgren, Millnet/Lysator/Debian/Mensa @ Pike developers forum
          • ... Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum
  • Re:... Magnus Holmgren, Millnet/Lysator/Debian/Mensa @ Pike developers forum
  • Re:... Marc Dirix
    • ... Magnus Holmgren, Millnet/Lysator/Debian/Mensa @ Pike developers forum
    • ... Marc Dirix
    • ... Marc Dirix

Reply via email to