From:	dumser AT rits DOT ray DOT com (James Dumser)
Subject:	Re: LL.dll or is it ii.dll
2 Mar 1998 18:58:19 -0800 :
Message-ID:	<34FAC806.87596085.cygnus.gnu-win32@rits.ray.com>
References:	<199802272249 DOT OAA15963 AT skaro DOT cygnus DOT com>
Mime-Version:	1.0
To:	Geoffrey Noer <noer AT cygnus DOT com>
Cc:	zow AT mdbs DOT com, gnu-win32 AT cygnus DOT com

On Fri, 27 Feb 1998 14:49:35 -0800 (PST), Geoffrey Noer 
  <noer AT cygnus DOT com> wrote:
> \"Zow\" Terry Brugger wrote:
> [...]
>> conceivable). Now that file could be LL.dll or ii.dll. Heck, it could 
>> even be Li.dll or iL.dll for all I know (the font's not very 
>> descriptive). I mailed the XEmacs-NT list to see if maybe it was a 
>> XEmacs thing, but I'm also posting here in case it's a B19 thing. So 
>> does this dll mean anything to anyone here, especially those that put 
>> together B19?
> [...]
> 
> I haven't tested building XEmacs with b19.  I certainly have never
> heard of ll.dll or ii.dll.

I don't know what ll.dll ii.dll is either, but I've been getting the
same message.

After installing B19, vim (5.0h compiled for cygwin [B18], for which I
only got binaries from someone on this list) stopped working correctly
-- it still works, but it doesn't recognize that it's attached to a
terminal (exact error is "Vim: Warning: Output is not to a terminal /
Vim: Warning: Input is not from a terminal") so the display is
"uncooked."

I pulled down vim-5.0k and attempted to build it under B19. It builds
(tho with several warnings), but the executable aborts with the message
"The dynamic link library ll could not be found in the specified path"
The only libraries it uses are X11 and ncurses, neither of which have
been recompiled for B19. I don't need X11 support, but turning it off is
just a little difficult without a working vi.

-- 
James Dumser    972.462.5335    dumser AT rtis DOT ray DOT com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -