Author: Robin Cosby Date: To: exim-users Subject: Re: [Exim] Problem installing exim-4.41
Philip Hazel wrote:
> On Thu, 19 Aug 2004, Robin Cosby wrote:
>
>> I should be grateful for any help in resolving the following problem,
>> which I've encountered when trying to install exim-4.41. I have been
>> using version 4.12 hitherto. I'm running Debian-3.0 with kernel-2.6.7
>> on a PC.
>>
>> On issuing the "make" command, the following messages appear:
>>
>> rfc2047.o(.text+0x3a9): In function `rfc2047_decode2':
>> : undefined reference to `libiconv_open'
>> rfc2047.o(.text+0x47f): In function `rfc2047_decode2':
>> : undefined reference to `libiconv'
>> rfc2047.o(text+0x574): In function `rfc2047_decode2':
>> : uundefined reference to `libiconv_close'
>> collect2: ld returned 1 exit status
>> make [1] ***[exim] Error 1
>> make [1] Leaving directory `/usr/local/exim-4.41/build-Linux-i386'
>> make *** [go] Error 1
>>
>> I have libiconv-1.9.1 and the line "HAVE_ICONV=yes" in
>> ~/Local/Makefile is uncommented.
>
>
> Sound like libiconv is not installed in a standard place and so Exim
> can't see it. As it says in the src/EDITME file:
>
> # If you are not using one of those systems, but have installed
> iconv(), you # need to uncomment that line above. In some cases, you
> may find that iconv()
> # and its header file are not in the default places. You might need to
> use # something like this: #
> # HAVE_ICONV=yes # CFLAGS=-O -I/usr/local/include #
> EXTRALIBS_EXIM=-L/usr/local/lib -liconv # # but of course there may
> need to be other things in CFLAGS and EXTRALIBS_EXIM
> # as well.
>
>
> Hello Philip,
Many thanks for your rapid response to my request for help.
I had assumed that iconv and its header file were in the default place,
so I'd ignored the lines following "HAVE-ICONV=yes". Uncommenting them
has solved the problem!
