Sitting at the campfire, [EMAIL PROTECTED] told:
I take your point about Solaris but it also required libiconv on a
RedHat 6.1 system.
Debian slink (2.1) also needs it.
Kai
--
x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x
Kai Blin(mailto:[EMAIL PROTECTED])
[EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote :
I have now built mutt 1.3.7 in four different places, two of the four
required that I get libiconv as the existing iconv wasn't good enough.
The two places that needed libiconv were Solaris 2.6 and Red Hat Linux
release 6.1.
I think this may
On Thu, Aug 17, 2000 at 10:13:37AM +0200, Martin [Keso] Keseg wrote:
[EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote :
I have now built mutt 1.3.7 in four different places, two of the four
required that I get libiconv as the existing iconv wasn't good enough.
The two places that needed
On 2000.08.17, in [EMAIL PROTECTED],
"Martin [Keso] Keseg" [EMAIL PROTECTED] wrote:
The two places that needed libiconv were Solaris 2.6 and Red Hat Linux
release 6.1.
no, it;s not a problem about development computers, that's a problem of solaris.
I was talking about iconv
I have now built mutt 1.3.7 in four different places, two of the four
required that I get libiconv as the existing iconv wasn't good enough.
The two places that needed libiconv were Solaris 2.6 and Red Hat Linux
release 6.1.
I think this may cause problems when this gets to a general release
