Re: commit: Re: commit: Re: commit: i18n megapatch to AW

Subject: Re: commit: Re: commit: Re: commit: i18n megapatch to AW
From: Vlad Harchev (
Date: Tue Oct 10 2000 - 02:52:19 CDT

On Tue, 10 Oct 2000, sam th wrote:


> Hash: SHA1
> On Tue, 10 Oct 2000, Martin Sevior wrote:
> >
> > Bother. FreeBSD on tinderbox is complainning about iconv not being present
> > in lots of places as result of the megapatch. Can a freebsd developer have
> > a look at this?
> >
> I don't actually know what the problem is here. I have an account on that
> FreeBSD box (thanks sourcegear) and the build fails for me too. Even
> manually changing the linking command (in src/wp/main/unix/Makefile) to
> add -liconv fails. This is strange, since there is a libiconv.a file in
> in /usr/local/lib/ on this machine.
> If someone with more linking/makefile knowledge than I have is interested
> in taking a look at this, please let me know. Also, if other FreeBSD
> people are willing to try this, that would be a big help.

 I think that this can be due to the #inclusion of the wrong <iconv.h> that
doesn't declare functions as 'extren "C"' - thus C++ compiler tries to find
mangled names and doesn't find them correctly.
 The sympthoms are:
If linker says
"undefined reference to 'iconv'" than 'extren "C"' was aroun the declaration
        of that function.
If linker says
"undefined reference to 'iconv(iconv_t, const char**, int*, char**, int*)'"
        than 'extren "C"' was not aroun the declaration of that function.
 It should be traced which one <iconv.h> is included. Though wv's and
libinconv's iconv.h wrap everything inside 'extern "C" {' - so that wrong
header file can be only FreeBSD's one.

> Thanks
> sam th
> GnuPG Key:
> Version: GnuPG v1.0.1 (GNU/Linux)
> Comment: For info see
> iD8DBQE54r68t+kM0Mq9M/wRAmu4AJ9gPgN/fffXoaE0WMaJzIf3uFNWTACbBf2/
> eO6al7m+Zq36jkx1yyjfuRA=
> =bkvC

 Best regards,

This archive was generated by hypermail 2b25 : Tue Oct 10 2000 - 03:06:49 CDT