------- Comment #14 from iains at gcc dot gnu dot org 2010-07-12 15:00 -------
(In reply to comment #13)
> I'll have to check the config.log more carefully.
OK. possible a can of wiggly things here...
case "${host}" in
*-*-darwin*)
export_sym_check="$gcc_cv_nm -g" <=== maybe these need to be $NM ....
;;
*)
export_sym_check="$gcc_cv_objdump -T" <==== ... and $OBJDUMP in any
event, the correct host tool
;;
esac
looks fine - until you find that gcc_cv_nm is being set to
../binutils/nm == nm-for-target
when host==build (and we've built the tool).
AS_VAR_SET_IF(gcc_cv_nm,, [
if test -f $gcc_cv_binutils_srcdir/configure.in \
&& test -f ../binutils/Makefile \
&& test x$build = x$host; then
gcc_cv_nm=../binutils/nm-new$build_exeext
elif test -x nm$build_exeext; then
gcc_cv_nm=./nm$build_exeext
elif test -x $NM_FOR_TARGET; then
gcc_cv_nm="$NM_FOR_TARGET"
else
AC_PATH_PROG(gcc_cv_nm, $NM_FOR_TARGET)
fi])
I'm not sure what the right version of nm/objdump is - but clearly, one for
the host not the target ...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42843
