bug-gnulib
[Top][All Lists]
Advanced

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

Re: LTLIBICONV / LIBICONV question


From: Tim Ruehsen
Subject: Re: LTLIBICONV / LIBICONV question
Date: Tue, 14 Jun 2016 17:02:14 +0200
User-agent: KMail/4.14.10 (Linux/4.6.0-1-amd64; KDE/4.14.20; x86_64; ; )

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.

Thanks Mike.

I am aware of this part of the docs. I doesn't answer my questions above, thus 
leaves me a bit clueless.

Regards, Tim

Attachment: signature.asc
Description: This is a digitally signed message part.


reply via email to

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