Rocco Rutte wrote: > > The iconv port is now at 2.0_3 and no longer installs a libiconv.so, > > instead it is called libbiconv.so. This library is a way not > > standard and did not work for mutt-1.3.x. > I know that this has recently changed. > > Please update both ports and try again. > No, I won't unless those 'old' ports completely break things > up.
i just installed GNU libiconv from source and then built mutt from source as well. thanks for everyone who wrote about this. i still had to set cc to "cc -I/usr/local/include" (i also set LDFLAGS to /usr/local/lib). so i guess the questions are: 1) why does configure no longer complain if libiconv isn't present? the noiconv patch never made it into 1.4, right?? so if mutt won't build without it, it seems like configure should fail as it used to. 2) do systems vary too much for configure to set compiler flags / environment variables correctly if "libiconv-prefix" is specified in the configure args? i'm certainly no expert on this stuff (and i do realize that if a system is properly configured, it's usually not necessary), but it is something i've seen a lot of people have problems with. i don't know if this is worth moving over to the dev list, but i will bring it up there if people don't think these questions are totally dumb. -- Will Yardley input: william < @ hq . newdream . net . >
