Re: Build of 4.1.0 in cross env

[FERANDELLE Pascal <pascal dot ferandelle at fr dot thalesgroup dot com>]

>  > - extraction of gcc-core-4.1.0.tar, gcc-g++-4.1.0.tar and gcc-java-4.1.0.tar
>  >
>  > - ./configure --with-sysroot=/VMPC/BlueCat --enable-langages=c,java --target=powerpc-linux
>  > (my Linux PowerPC environment is under /VMPC/BlueCat)
>
> Configuring gcc in the srcdir is truly scary, and I'm surprised it
> works at all, but I don't know that's the cause of your problem.
>
> "First, we highly recommend that GCC be built into a separate
> directory than the sources which does not reside within the source
> tree. This is how we generally build GCC; building where srcdir ==
> objdir should still work, but doesn't get extensive testing; building
> where objdir is a subdirectory of srcdir is unsupported.
>
> "To configure GCC:
>
>         % mkdir objdir
>         % cd objdir
>         % srcdir/configure [options] [target]"
>
>

I followed this way, and it works better now !!!
I still have to copy three libraries from my Linux/PowerPC environment to /usr/local/powerpc-linux/lib directory (libc.so.6, libc_nonshared.a, ld.so.1), because the specified path with the --with-sysroot option, is not taken into account everywhere during the build, but it is the only modifications I have to do (nothing in Makefile for example).

So now, I have a complete cross powerpc-linux gcc chain in 4.1.0, and I test on a simple HelloWorld Java program.
It does not link because there is an undefined reference to __tls_get_addr, needed by libgcj.so.
I did not have this problem in 3.4.4.

Any idea ?

Thanks
Pascal FERANDELLE