Re: [Doxygen-users] `make` fails (probably) because of libiconv
Brought to you by:
dimitri
From: Albert <alb...@gm...> - 2014-03-05 10:29:26
|
Hi Guiseppe, I assume you ran configure again. Your libiconv is not on a standard place (when I remember well) so you probably also have to add the -L to that path. Albert On Tue, Mar 4, 2014 at 9:03 PM, Giuseppe Crino' <gi...@gm...> wrote: > On 1 March 2014 19:02, Dimitri van Heesch <do...@gm...> wrote: > >> On most Linux systems libiconv is part of libc (see also >> http://en.wikipedia.org/wiki/Iconv), >> on other systems it has to be linked explicitly. >> >> Your system seems to require explicit linking despite being a Linux >> system. >> Assuming you use the linux-g++ configuration, you could try to modify >> TMAKE_LIBS in >> tmake/lib/linux-g++/tmake.conf as follows: >> >> TMAKE_LIBS = -liconv >> > > No, it does not work. But it is curious that though I've modified > tmake.conf as you advised me output remains the same when error occurs in > making, i.e. > > make[2]: Entering directory `/home/giuscri/doxygen-1.8.6/src' > g++ -o ../bin/doxygen ../objects/main.o -L../lib -ldoxygen -ldoxycfg > -lqtools -lmd5 -lpthread > ../lib/libdoxycfg.a(portable_c.o): In function `portable_iconv_open': > portable_c.c:(.text+0x1): undefined reference to `libiconv_open' > ../lib/libdoxycfg.a(portable_c.o): In function `portable_iconv': > portable_c.c:(.text+0x11): undefined reference to `libiconv' > ../lib/libdoxycfg.a(portable_c.o): In function `portable_iconv_close': > portable_c.c:(.text+0x21): undefined reference to `libiconv_close' > > while I would have expected > > g++ -o ../bin/doxygen ../objects/main.o -L../lib -ldoxygen -ldoxycfg > -lqtools \ > -lmd5 **-liconv** -lpthread > > Am I wrong? > > -- > **Guerilla Open Access Movement** > > > http://archive.org/stream/GuerillaOpenAccessManifesto/Goamjuly2008_djvu.txt > > > ------------------------------------------------------------------------------ > Subversion Kills Productivity. Get off Subversion & Make the Move to > Perforce. > With Perforce, you get hassle-free workflows. Merge that actually works. > Faster operations. Version large binaries. Built-in WAN optimization and > the > freedom to use Git, Perforce or both. Make the move to Perforce. > > http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk > _______________________________________________ > Doxygen-users mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-users > > |