Re: gcc BZ 112671

[Bruno Haible]

Hi Arsen,

Arsen Arsenović wrote:
> Naturally, that unmodified
> iconv.m4 has no idea about the sibling libiconv that can be built in the
> toolchain tree.  I'm wondering about what the appropriate method of
> informing gettext (and other iconv.m4 users) about where to find the
> sibling libiconv.
> 
> If I can tell AM_ICONV where to find the sibling libiconv, I could
> possibly leave an unmodified iconv.m4 in the toolchain tree.

I think I already hinted at this when I wrote, a couple of days ago:
  "the user can just as well
   add -I$DIR1 to the CPPFLAGS and "-L$DIR2 -Wl,-rpath,$DIR2" to the
   LDFLAGS before running 'configure'.
  "

Namely, if you have a GNU libiconv unpacked in a sibling directory:
Since that package does not have an 'uninstalled-config.sh' script,
you need to set CPPFLAGS and LDFLAGS before running 'configure'.
Assuming it's a build done with --disable-shared (like the gettext-runtime
sibling build), you will need to set
  CPPFLAGS="$CPPFLAGS -I`cd .. && pwd`/libiconv/include"
  LDFLAGS="$LDFLAGS `cd .. && pwd`/libiconv/lib/.libs/libiconv.a"

Or you make use of libiconv's 'install-lib' target and do
  cd ../libiconv && $(MAKE) install-lib 
and then set
  CPPFLAGS="$CPPFLAGS -I$PREFIX/include"
  LDFLAGS="$LDFLAGS $PREFIX/lib/libiconv.a"

You'll need this both before configuring gettext-runtime and before
configuring gcc, because they both need iconv().

Bruno