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
Notice the error happens at linking time
> 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
...and 'c++ -c' specifically does _not_ link.
$ cat test.c
#include <stddef.h>
#include <wchar.h>
int main() {
; return 0; }
all6500-2:~/icew
$ c++ -c -fno-strict-aliasing -fshort-wchar test.c
$ echo $?
0
$ c++ -fno-strict-aliasing -fshort-wchar test.c
/usr/bin/ld: ERROR: /tmp/ccKVwN1s.o: Conflicting definitions of wchar_t
/usr/bin/ld: failed to merge target specific data of file
/tmp/ccKVwN1s.o
collect2: ld returned 1 exit status
> And both tests have not changed for a while, and xulrunner build fine on
> armel in unstable [1]
FWIW xulrunner/iceweasel based on FF 2.0 does not work (even if it
compiles) on armel. That's why we are looking at getting FF3.0
compiled. The nokia internet tablets are based on armel and and
have browser based on FF3.0 alpha, so it would seem more feasible
to get FF3.0 working than backporting the support to 2.0..
> 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
A quick test confirms, test.c compiles fine with g++-4.2, but fails with
g++-4.3.
