Hi All,
I ran into trouble cross-compiling wirshark/tshak for ARM. It looks
like the same issues from https://www.wireshark.org/lists/wireshark-users/200910/msg00121.html
and https://www.wireshark.org/lists/wireshark-dev/201104/msg00135.html :
Host-side tools (lemon) were being compiled with the cross-compiler, and
then didn't work later in the build process.
I believe the problem is that CC_FOR_BUILD was never being properly set
and ultimately got defaulted to $CC. The fix is basically a 2-line change
to configure.ac, and including the macro ax_prog_cc_for_build.m4 in
aclocal-fallback/. Should I submit a change for code review, or how is that
handled?
Thanks,
Eric
--
Eric W. Anderson Computer Science Department
andersoe@xxxxxxxxxx Carnegie Mellon University
phone: +1-412-268-1908 Gates-Hillmann Center 6005
PGP key fingerprint:
D3C5 D6FF EDED 9F1F C36D 53A3 74B7 53A6 3C74 5F12
diff --git a/configure.ac b/configure.ac
index d65ffc9..f9e4920 100644
--- a/configure.ac
+++ b/configure.ac
@@ -239,8 +239,12 @@ if test "x$GCC" = "xyes" -o "x$CC" = "xclang" ; then
ac_supports_W_linker_passthrough=yes
fi
+# EWA: Should this really be here? I'm guessing no, but this is the first use of CC_FOR_BUILD
+AX_PROG_CC_FOR_BUILD
+
if test "x$CC_FOR_BUILD" = x
then
+ AC_ERROR([CC_FOR_BUILD is undefined. That shouldn't happen!])
CC_FOR_BUILD=$CC
fi
AC_SUBST(CC_FOR_BUILD)
Attachment:
signature.asc
Description: Digital signature
