From 29a63921d9e05ea2932861ce6c1154f3ce9bbfe0 Mon Sep 17 00:00:00 2001 From: Alexandre Oliva Date: Mon, 31 Jan 2011 05:20:17 +0000 Subject: re PR libgcj/44341 (libjava cross build fails when configured with --with-gmp=) ChangeLog: PR libgcj/44341 * configure.ac: Discard --with-* flags for host when configuring target libraries for cross build. * configure: Rebuilt. gcc/ChangeLog: PR libgcj/44341 * doc/install.texi: Document host options discarded when cross configuring target libraries. From-SVN: r169430 --- gcc/doc/install.texi | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'gcc/doc') diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi index d00f831..b953d72 100644 --- a/gcc/doc/install.texi +++ b/gcc/doc/install.texi @@ -1584,6 +1584,9 @@ shared libraries can be found by the dynamic linker when building and using GCC, for example by setting the runtime shared library path variable (@env{LD_LIBRARY_PATH} on GNU/Linux and Solaris systems). +These flags are applicable to the host platform only. When building +a cross compiler, they will not be used to configure target libraries. + @item --with-ppl=@var{pathname} @itemx --with-ppl-include=@var{pathname} @itemx --with-ppl-lib=@var{pathname} @@ -1604,6 +1607,9 @@ you can explicitly specify the directory where they are installed shorthand assumptions are not correct, you can use the explicit include and lib options directly. +These flags are applicable to the host platform only. When building +a cross compiler, they will not be used to configure target libraries. + @item --with-host-libstdcxx=@var{linker-args} If you are linking with a static copy of PPL, you can use this option to specify how the linker should find the standard C++ library used -- cgit v1.1