[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: /usr/lib/gcc/x86_64-alpine-linux-musl: libgettextlib.so: undefined r

From: Bruno Haible
Subject: Re: /usr/lib/gcc/x86_64-alpine-linux-musl: libgettextlib.so: undefined reference to `libiconv'
Date: Mon, 15 Jun 2020 22:02:47 +0200
User-agent: KMail/5.1.3 (Linux/4.4.0-179-generic; KDE/5.18.0; x86_64; ; )

Jeffrey Walton wrote:
> > Jeffrey Walton wrote:
> > > $ grep ICONV gettext-tools/config.status
> > > S["ICONV_H"]="iconv.h"
> > > S["LTLIBICONV"]=""
> > > S["LIBICONV"]=""
> >
> > This is the situation that is expected when you use the libc's built-in
> > iconv facility.
> >
> > The error, on the other hand, indicates that you're using libiconv's
> > <iconv.h>.
> >
> > Possibly you configured gettext before installing libiconv, and are now
> > compiling gettext after installing libiconv? This is not supported. If
> > the list of packages on your system changes significantly, you must
> > reconfigure gettext.
> I believe I'm doing what the manual says: (1) build libiconv, install
> it, (2) build gettext, install it, (3) build libiconv again, install
> it again.

And you are now in the step (2)?

We need to find out why gettext-tools/config.status contains an empty
LIBICONV and LTLIBICONV variable. The place to look is gettext-tools/config.log.

> I think the circular dependency is a very bad idea. But it is not my
> call to make.

It is not as bad as you think:
  - gettext depends on the iconv _library_.
  - The iconv _program_ depends on gettext and the iconv library.
So, it the iconv library and the iconv program were in separate packages,
there would not be a circular dependency.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]