Re: build failure

[c.]

On 14 Sep 2012, at 14:58, John W. Eaton wrote:

> On 14-Sep-2012, c. wrote:
> 
> | I have
> | 
> | $ hg id
> | d8d7596fc68d tip
> | 
> | cloned from scratch.
> | 
> | building on my OSX system fails with the attached long set of link errors.
> | any idea how I can try and fix this?
> 
> Does the attached change help?
> 
> jwe
> 
> diff --git a/libgui/Makefile.am b/libgui/Makefile.am
> --- a/libgui/Makefile.am
> +++ b/libgui/Makefile.am
> @@ -49,6 +49,9 @@
> 
> include link-deps.mk
> 
> +# Dummy C++ source to cause C++ linking.
> +nodist_EXTRA_libgui_la_SOURCES = dummy.cc
> +
> liboctgui_la_LIBADD = \
>   qterminal/libqterminal.la \
>   src/libgui-src.la \
> diff --git a/liboctave/Makefile.am b/liboctave/Makefile.am
> --- a/liboctave/Makefile.am
> +++ b/liboctave/Makefile.am
> @@ -96,6 +96,9 @@
> 
> include link-deps.mk
> 
> +# Dummy C++ source to cause C++ linking.
> +nodist_EXTRA_liboctave_la_SOURCES = dummy.cc
> +
> liboctave_la_LIBADD = \
>   array/libarray.la \
>   cruft/libcruft.la \

John,
not much, I seem to be getting the same errors, in particular gcc is still used 
for linking rather than g++:
/bin/sh ../libtool --tag=CC   --mode=link ccache gcc-4.2
I'm not sending the whole verbose output again unless you need it.
Thanks for your help, any other suggestions I could try, maybe configuring with 
LD=g++?
c.