[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: LTLIBICONV / LIBICONV question
From: |
Mike Frysinger |
Subject: |
Re: LTLIBICONV / LIBICONV question |
Date: |
Tue, 14 Jun 2016 14:24:18 -0400 |
On 14 Jun 2016 17:02, Tim Ruehsen wrote:
> On Tuesday 14 June 2016 10:20:59 Mike Frysinger wrote:
> > On 14 Jun 2016 15:21, Tim Ruehsen wrote:
> > > for GNU Wget we don't (explicitely) use libtool, but on some systems
> > > LTLIBICONV is set while LIBICONV is not.
> > > See http://savannah.gnu.org/bugs/?48193 for details.
> > >
> > > But I also remember seeing LIBICONV set and LTLIBICONV unset in the past.
> > >
> > > At this point, we are looking for clarification about what to put into
> > > Makefile.am / LDADD. Currently (since a few days) we have
> > >
> > > LDADD = $(LIBOBJS) ../lib/libgnu.a $(GETADDRINFO_LIB) $(HOSTENT_LIB)
> > > $(INET_NTOP_LIB) $(LIBSOCKET)\
> > > $(LIB_CLOCK_GETTIME) $(LIB_CRYPTO) $(LIB_SELECT) $(LTLIBICONV)
> > > $(LTLIBINTL) $(LTLIBTHREAD)\
> > > $(SERVENT_LIB)
> > >
> > > In the past we used $(LIBICONV) and not $(LTLIBICONV).
> > >
> > > What is correct ?
> > > Should we perhaps add both $(LIBICONV) and $(LTLIBICONV) to LDADD ?
> >
> > the gettext manual describes both variables:
> > https://www.gnu.org/software/gettext/manual/html_node/AM_005fICONV.html
> >
> > you should follow those guidelines and not pay attention to the values
> > each one is set to.
>
> I am aware of this part of the docs. I doesn't answer my questions above,
> thus
> leaves me a bit clueless.
if you're using libtool, then use $(LTLIBICONV). if you aren't using
libtool, then use $(LIBICONV).
maybe i'm missing something obvious in your question though ?
-mike
signature.asc
Description: Digital signature