On 06-06-10 18:15, Magnus Holmgren, Millnet/Lysator/Debian/Mensa @ Pike developers forum wrote:

...

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.

I don't exactly understand what you mean here? If configure.in in pike is patched, then for every new stable release configure will also be correct thereafter?

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

One could declare a build-dependecy in the control file. Otherwise the building process just fails, stating pike is not found.

...

4. Patch to src/modules/Mysql/configure

I think this patch was already included in src/modules/Mysql/configure.in.

That one looks reversed.

It is, sorry about that! Attached is the correct diff.