Re: [bug-gnu-libiconv] Including libiconv in another package

[Bruno Haible]

Reuben Thomas wrote:
> On Windows I get an error I don't understand:
> https://github.com/rrthomas/recode/actions/runs/8220550778/job/22479798106
> 
> Configuring in libcharset fails with "configure: WARNING: no configuration
> information is in libcharset". Configuration in libiconv appears to have
> been successful, so I'm not sure what's gone wrong.

I think I've already touched on this one in
<https://lists.gnu.org/archive/html/bug-gnu-libiconv/2023-05/msg00015.html>:

  Also, it is very unusual/strange that the *configuration* of recode
  triggers a *build* of libiconv. This is most likely the cause of the
  wrong dates of libiconv/config.status vs. libiconv/srclib/Makefile,
  and is also likely to cause other problems (think of "make clean",
  which is not meant to erase files created by 'configure' ...).
  I don't remember if it was me who suggested doing that. But it looks
  very wrong. The right approach is:
    - configure of recode should trigger a configure of libiconv, via
      AC_CONFIG_SUBDIRS,
    - "make" of recode should trigger a "make" of libiconv,
    - configure of recode cannot use AM_ICONV or other configure tests
      which assume that libiconv is already built and installed.

Bruno