[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

lynx-dev Re: current_codepage error during linking

From: Webmaster Jim
Subject: lynx-dev Re: current_codepage error during linking
Date: Tue, 11 Jan 2000 06:48:45 -0500

On Mon, Jan 10, 2000 at 11:08:38PM +0200, Mike Bledig wrote:
> the error:
> Error: Unresolved external '_current_codepage' referenced from 
> module src/lycurses.c  
> Has been blocked out, but I feel that's not the answer. The code
> compiles ok, but during the linking faze, that error comes up unless
> it is blocked. Do you think that it might have something to do with
> the way I compiled the pdcurses.lib? I compiled "pdcurses.lib" and
> "zlib.lib" with the "-tWM" switch as was suggested to me. Though
> compiling the "zlib.lib" with the "-tWM" option, stops an error with
> errno, it doesn't fix the one with current_codepage. Perhaps if one
> compiles the "pdcurses.lib" as a large model, that error won't come up
> any more during the linking faze? or does using "-tWM" switch already
> compile the "pdcurses.lib" as a large model? Have any guess as to
> what's up?

A more general answer is that Win32 support has been added to Lynx and
we are still integrating this code into the main source, which has
historically been UNIX and then VMS compatible. Since not a lot of
people have the time and interest to debug Lynx Win32, you have found
some of the rough spots. The codepage issue is a result of changes by
the main Win32 contributor (Hiroyuki Senshu) to allow Japanese language
displays. As I mentioned in an earlier post, defines for SH_EX, CJK_EX
and WIN_EX may overlap in come of the code.

The version of Lynx you're working with is the development version,
and while we're trying to get to a code freeze, we certainly welcome
code changes that allow Lynx to compile on more platforms and use more
compilers (just think, we run on more systems than Netscape or IE -- I
just wish someone would volunteer to update our Mac port :-)

Marvin the Paranoid Android.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]