On Fri, Apr 04, 2008 at 10:08:28PM +0200, Mike Hommey wrote:
> On Fri, Apr 04, 2008 at 08:50:31PM +0100, Jon Dowland wrote:
> > On Fri, Apr 04, 2008 at 09:31:27PM +0200, Mike Hommey wrote:
> > > On Fri, Apr 04, 2008 at 07:22:07PM +0100, Jon Dowland wrote:
> > > > configure:17706: c++ -o conftest  -fno-strict-aliasing -fshort-wchar 
> > > > -pthread -pipe   -lpthread -Wl,--as-needed conftest.C -ldl -lm  1>&5
> > > > /usr/bin/ld: ERROR: /tmp/ccef8aU1.o: Conflicting definitions of wchar_t
> > > 
> > > WTF?!? There's not even wchar_t in the source
> > 
> > I know bugger all about c++ but I'm plodding on, since there's no
> > experimental buildd for armel yet.
> > 
> > 19:32 < suihkulokki> Jon: The problem is -fshort-wchar option, you would
> > need to hack the configure scripts to not enable it
> > 
> > I'm just trying to disable that chunk of stuff in configure.in and
> > regenerate the makefiles, then try again.
> 
> On the other hand, it builds this correctly:
> configure:8114: checking for compiler -fshort-wchar option
> configure:8128: c++ -c  -fno-strict-aliasing -fshort-wchar   conftest.C 1>&5
> 
> This being generated by the following configure.in snippet:
>         [AC_TRY_COMPILE([#include <stddef.h>
>                          $configure_static_assert_macros],
>                         [CONFIGURE_STATIC_ASSERT(sizeof(wchar_t) == 2);
>                          CONFIGURE_STATIC_ASSERT((wchar_t)-1 > (wchar_t) 0)],
>                         ac_cv_have_usable_wchar_option_v2="yes",
>                         ac_cv_have_usable_wchar_option_v2="no")])
> 
> This snippet is responsible for the addition of -fshort-wchar in the 
> CXX_FLAGS in
> what is failing for you.

And both tests have not changed for a while, and xulrunner build fine on
armel in unstable [1]

Could you try to use the same toolchain as when xulrunner was built ?
i.e. gcc-4.2_4.2.3-2 g++-4.2_4.2.3-2 binutils_2.18.1~cvs20080103-1

Mike

1.  
http://buildd.debian.org/fetch.cgi?pkg=xulrunner;ver=1.8.1.12-5;arch=armel;stamp=1206621388



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to