bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Jeffrey Walton <noloader@gmail.com>
To: bug-gnulib@gnu.org
Subject: GetText 1.20.1 and libgettextlib.so: undefined reference to `libiconv' (and friends)
Date: Wed, 5 Feb 2020 04:02:30 -0500	[thread overview]
Message-ID: <CAH8yC8mKvSQUpsNWw=JzEoJB6kewvw=i5j6NNvM5DmOJ1MUFYg@mail.gmail.com> (raw)

Hi Everyone,

I'm building GetText 1.20.1 from sources on NetBSD. msgcmp is failing:

/bin/sh ../libtool  --tag=CC   --mode=link gcc  -g2 -O2 -fPIC -pthread
 -L/usr/local/lib -Wl,-R,'$ORIGIN/../lib' -Wl,-R,/usr/local/lib
-Wl,--enable-new-dtags -o msgcmp msgcmp-msgcmp.o msgcmp-msgl-fsearch.o
libgettextsrc.la  -lm  -lpthread
libtool: link: gcc -g2 -O2 -fPIC -pthread -Wl,-R -Wl,\$ORIGIN/../lib
-Wl,-R -Wl,/usr/local/lib -Wl,--enable-new-dtags -o .libs/msgcmp
msgcmp-msgcmp.o msgcmp-msgl-fsearch.o  -L/usr/local/lib
./.libs/libgettextsrc.so
/home/jwalton/gettext-0.20.1/gettext-tools/gnulib-lib/.libs/libgettextlib.so
/home/jwalton/gettext-0.20.1/libtextstyle/lib/.libs/libtextstyle.so
-lncurses /home/jwalton/gettext-0.20.1/gettext-tools/intl/.libs/libintl.so
-lc -lm -lpthread -pthread -Wl,-rpath -Wl,/usr/local/lib
/home/jwalton/gettext-0.20.1/gettext-tools/gnulib-lib/.libs/libgettextlib.so:
undefined reference to `libiconv'
/home/jwalton/gettext-0.20.1/gettext-tools/gnulib-lib/.libs/libgettextlib.so:
undefined reference to `libiconv_open'
/home/jwalton/gettext-0.20.1/gettext-tools/gnulib-lib/.libs/libgettextlib.so:
undefined reference to `libiconv_close'
gmake[5]: *** [Makefile:2909: msgcmp] Error 1

I configured GetText with --with-libiconv-prefix=[DIR], but it looks
like -liconv and did not make it into the recipe. Adding -liconv to
LIBS did not help.

Jeff


             reply	other threads:[~2020-02-05  9:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-05  9:02 Jeffrey Walton [this message]
2020-02-05 12:39 ` GetText 1.20.1 and libgettextlib.so: undefined reference to `libiconv' (and friends) Jeffrey Walton
2020-02-05 14:48   ` Bruno Haible
2020-02-05 14:53 ` Bruno Haible

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH8yC8mKvSQUpsNWw=JzEoJB6kewvw=i5j6NNvM5DmOJ1MUFYg@mail.gmail.com' \
    --to=noloader@gmail.com \
    --cc=bug-gnulib@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).