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.
--- src/modules/Mysql/configure 2009-09-22 22:38:35.000000000 +0200
+++ ../../pike1/Mysql_configure 2010-05-19 12:20:10.745552500 +0200
@@ -7018,13 +7018,7 @@
$as_echo "yes" >&6; }
if test "$cross_compiling" = yes; then
- { { $as_echo "$as_me:$LINENO: error: in \`$ac_pwd':" >&5
-$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
-{ { $as_echo "$as_me:$LINENO: error: cannot run test program while cross compiling
-See \`config.log' for more details." >&5
-$as_echo "$as_me: error: cannot run test program while cross compiling
-See \`config.log' for more details." >&2;}
- { (exit 1); exit 1; }; }; }
+:
else
cat >conftest.$ac_ext <<_ACEOF
/* confdefs.h. */
