Subject: Re: libiconv 1.7 on Win32, QNX, etc.?
From: Tim LaDuca (tjl@141.com)
Date: Thu Aug 09 2001 - 15:23:50 CDT
OK, so maybe I see what Paul's talking about.
Paul, is this what you're getting?
libAbiUtil_s.lib(ut_Encoding.obj) : error LNK2001: unresolved external
symbol _libiconv_close
(x 10 or so)
For those in the know, would it be a big deal if I built a win32 binary with
libiconv 1.0?
Cheers,
tim
----- Original Message -----
From: "Paul Rohr" <paul@abisource.com>
To: "Hubert Figuiere" <hfiguiere@teaser.fr>
Cc: <abiword-dev@abisource.com>
Sent: Thursday, August 09, 2001 3:53 PM
Subject: Re: libiconv 1.7 on Win32, QNX, etc.?
> At 09:11 PM 8/9/01 +0200, Hubert Figuiere wrote:
> >According to Paul Rohr <paul@abisource.com>:
> >> Sorry for all the confusion. I'm trying to be as clear as I can. Are
you
> >> saying that:
> >>
> >> - You *have* successfully done a diving make, starting in the Abi
tree,
> >> which fires off a Makefile.abi build of libiconv 1.7?
> >
> >Yes.
>
> Cool. That's good news. :-) Now we just need to figure out why it's
> working for you and not for me.
>
> >> If so, I'd love some tips from you on how to make that same process
Just
> >> Work for me, too. From a quick glance at the errors I get, it's not at
> all
> >> obvious how to get this working.
> >
> >cvs update -PAd libiconv
> >(if you didn't or forgot).
>
> OK. I'm pretty confident I've done so already, but just to be sure I
didn't
> miss anything, I'll do another round of cvs updates and let you know what
> happens after a "make realclean". [ My tree does include the patches I
> mentioned yesterday, but none of those should affect this. ]
>
> Paul
>
>
This archive was generated by hypermail 2b25 : Thu Aug 09 2001 - 15:27:47 CDT