Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <3C39C745.10805@ece.gatech.edu> Date: Mon, 07 Jan 2002 11:05:25 -0500 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: Corinna Vinschen Subject: Re: compiling lynx-2.8.4.1 References: <20020107154700.D51080@ms.chinmin.edu.tw> <20020107103240.B1242@cygbert.vinschen.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Corinna Vinschen wrote: > On Mon, Jan 07, 2002 at 03:47:01PM +0800, Greg Matheson wrote: > >>LYStrings.o(.text+0x4261):LYStrings.c: undefined reference to `acs_map' >>LYStrings.o(.text+0x4290):LYStrings.c: undefined reference to `acs_map' >>LYStrings.o(.text+0x4ee2):LYStrings.c: undefined reference to `acs_map' >>LYStrings.o(.text+0x4f1f):LYStrings.c: undefined reference to `acs_map' >>collect2: ld returned 1 exit status >>make[1]: *** [lynx.exe] Error 1 >>make[1]: Leaving directory `/usr/src/lynx-2.8.4-1/src' >>make: *** [all] Error 2 >> >>So what do I do next? Has anyone succeeeded in compiling lynx? >> > > Use -DBROKEN_LINKER when compiling. That's a problem with current > ncurses and current binutils. "...and current binutils." -- I don't think binutils is actually at fault here, in the sense that there is some bug that needs fixing. Without BROKEN_LINKER, the ncurses code tries to do something that is just not possible with PE DLLs + the windows runtime loader. The bug is that ncurses treats BROKEN_LINKER as a private symbol; but in fact it should be part of the public headers because it changes the external library interface -- and clients need to know about that. I'm working on a fix to ncurses. Stay tuned. --Chuck > > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/