Peter Davis | 3 Jan 2003 17:26

Win2000, XEmacs 21.4.10, MH-E, cygwin 1.3.17-1

I've been trying to get MH-E to run within XEmacs on both my home (Win
NT4) and office (Win 2000) machines.  Both machines have XEmacs
(21.4.9 at home, 21.4.10 in office) and Cygwin (somewhere around
1.3.?)  installed.  Both XEmacs installations are of the Win32
version, as opposed to the Cygwin version.

On my home (Win NT) machine, I can run mh-rmail with no problem.  I
still have some issues with paths when I try to send mail, but I can
open folders and read mail.

On the office (Win 2000) machine, whenever I try to run mh-rmail, I
get pop-up windows that say:

> The procedure entry point _ctype_ could not be located in the
> dynamic link library cygwin1.dll

So why is XEmacs even *looking* in cygwin1.dll, since it's the win32
installation? 

Anyone know what might be causing this error?  I don't know if this is
a Cygwin issue or an XEmacs issue or both.

Thanks very much.

-pd

--

-- 
--------
                             Peter Davis
               Funny stuff at http://www.pfdstudio.com
(Continue reading)

Stephen J. Turnbull | 3 Jan 2003 18:14
Picon
Favicon

Re: Win2000, XEmacs 21.4.10, MH-E, cygwin 1.3.17-1

>>>>> "Peter" == Peter Davis <pdavis <at> pageflexinc.com> writes:

    >> The procedure entry point _ctype_ could not be located in the
    >> dynamic link library cygwin1.dll

    Peter> So why is XEmacs even *looking* in cygwin1.dll, since it's
    Peter> the win32 installation?

I doubt XEmacs is looking in cygwin1.dll.  Most likely it's the MH
binaries.

--

-- 
Institute of Policy and Planning Sciences     http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba                    Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
               Ask not how you can "do" free software business;
              ask what your business can "do for" free software.

Peter Davis | 3 Jan 2003 19:29

Re: Win2000, XEmacs 21.4.10, MH-E, cygwin 1.3.17-1

On Sat, Jan 04, 2003 at 02:14:04AM +0900, Stephen J. Turnbull wrote:
> >>>>> "Peter" == Peter Davis <pdavis <at> pageflexinc.com> writes:
> 
>     >> The procedure entry point _ctype_ could not be located in the
>     >> dynamic link library cygwin1.dll
> 
>     Peter> So why is XEmacs even *looking* in cygwin1.dll, since it's
>     Peter> the win32 installation?
> 
> I doubt XEmacs is looking in cygwin1.dll.  Most likely it's the MH
> binaries.

Hmmm.  That's even *more* puzzling, since I'm running the identical
binaries on both machines. I have not succeeded in building nmh on
Cygwin myself.

Thanks,

-pd

--

-- 
--------
                             Peter Davis
               Funny stuff at http://www.pfdstudio.com
                 The artwork formerly shown as prints
    List of resources for children's writers and illustrators at:
                  http://www.pfdstudio.com/cwrl.html

Kevin Layer | 3 Jan 2003 20:37
Picon
Favicon

Re: Win2000, XEmacs 21.4.10, MH-E, cygwin 1.3.17-1

Peter Davis <pdavis <at> pageflexinc.com> wrote:

>> On Sat, Jan 04, 2003 at 02:14:04AM +0900, Stephen J. Turnbull wrote:
>> > >>>>> "Peter" == Peter Davis <pdavis <at> pageflexinc.com> writes:
>> > 
>> >     >> The procedure entry point _ctype_ could not be located in the
>> >     >> dynamic link library cygwin1.dll
>> > 
>> >     Peter> So why is XEmacs even *looking* in cygwin1.dll, since it's
>> >     Peter> the win32 installation?
>> > 
>> > I doubt XEmacs is looking in cygwin1.dll.  Most likely it's the MH
>> > binaries.
>> 
>> Hmmm.  That's even *more* puzzling, since I'm running the identical
>> binaries on both machines. I have not succeeded in building nmh on
>> Cygwin myself.

If you have MSVC++, you can use `dumpbin /imports xemacs.exe' to see
what dlls xemacs.exe (or whatever it's called) depends on.

Peter Davis | 3 Jan 2003 20:54

Re: Win2000, XEmacs 21.4.10, MH-E, cygwin 1.3.17-1

On Fri, Jan 03, 2003 at 01:29:04PM -0500, Peter Davis wrote:
> On Sat, Jan 04, 2003 at 02:14:04AM +0900, Stephen J. Turnbull wrote:
> > >>>>> "Peter" == Peter Davis <pdavis <at> pageflexinc.com> writes:
> > 
> >     >> The procedure entry point _ctype_ could not be located in the
> >     >> dynamic link library cygwin1.dll
> > 
> >     Peter> So why is XEmacs even *looking* in cygwin1.dll, since it's
> >     Peter> the win32 installation?
> > 
> > I doubt XEmacs is looking in cygwin1.dll.  Most likely it's the MH
> > binaries.
> 
> Hmmm.  That's even *more* puzzling, since I'm running the identical
> binaries on both machines. I have not succeeded in building nmh on
> Cygwin myself.

Ok, my mistake.  It *is* the nmh binaries.  I just noticed that the
message windows that pop up have titles like 

folder.exe
folders.exe
inc.exe
mark.exe
scan.exe

However, the raw nmh commands run in the Cygwin bash shell with no
problems.  It's just running them from XEmacs that seems to cause the
problem.

(Continue reading)

Igor Pechtchanski | 3 Jan 2003 21:34
Picon

Re: Win2000, XEmacs 21.4.10, MH-E, cygwin 1.3.17-1

On Fri, 3 Jan 2003, Peter Davis wrote:

> On Fri, Jan 03, 2003 at 01:29:04PM -0500, Peter Davis wrote:
> > On Sat, Jan 04, 2003 at 02:14:04AM +0900, Stephen J. Turnbull wrote:
> > > >>>>> "Peter" == Peter Davis <pdavis <at> pageflexinc.com> writes:
> > >
> > >     >> The procedure entry point _ctype_ could not be located in the
> > >     >> dynamic link library cygwin1.dll
> > >
> > >     Peter> So why is XEmacs even *looking* in cygwin1.dll, since it's
> > >     Peter> the win32 installation?
> > >
> > > I doubt XEmacs is looking in cygwin1.dll.  Most likely it's the MH
> > > binaries.
> >
> > Hmmm.  That's even *more* puzzling, since I'm running the identical
> > binaries on both machines. I have not succeeded in building nmh on
> > Cygwin myself.
>
> Ok, my mistake.  It *is* the nmh binaries.  I just noticed that the
> message windows that pop up have titles like
>
> folder.exe
> folders.exe
> inc.exe
> mark.exe
> scan.exe
>
> However, the raw nmh commands run in the Cygwin bash shell with no
> problems.  It's just running them from XEmacs that seems to cause the
(Continue reading)

Bill Wohler | 3 Jan 2003 21:52
X-Face
Picon
Picon
Gravatar

Re: Win2000, XEmacs 21.4.10, MH-E, cygwin 1.3.17-1

Igor Pechtchanski <pechtcha <at> cs.nyu.edu> wrote:

> P.S. This is likely a cygwin problem, so you might wish to remove the
> other two lists from this discussion and only post the final solution
> there.

  Either way works for us (MH-E).

--
Bill Wohler <wohler <at> newt.com>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.

Peter Davis | 3 Jan 2003 22:38

Re: Win2000, XEmacs 21.4.10, MH-E, cygwin 1.3.17-1

On Fri, Jan 03, 2003 at 03:34:20PM -0500, Igor Pechtchanski wrote:
> On Fri, 3 Jan 2003, Peter Davis wrote:
> 
> > On Fri, Jan 03, 2003 at 01:29:04PM -0500, Peter Davis wrote:
> > > On Sat, Jan 04, 2003 at 02:14:04AM +0900, Stephen J. Turnbull wrote:
> > > > >>>>> "Peter" == Peter Davis <pdavis <at> pageflexinc.com> writes:
> > > >
> > > >     >> The procedure entry point _ctype_ could not be located in the
> > > >     >> dynamic link library cygwin1.dll
> > > >
> > > >     Peter> So why is XEmacs even *looking* in cygwin1.dll, since it's
> > > >     Peter> the win32 installation?
> > > >
> > > > I doubt XEmacs is looking in cygwin1.dll.  Most likely it's the MH
> > > > binaries.
> > >
> > > Hmmm.  That's even *more* puzzling, since I'm running the identical
> > > binaries on both machines. I have not succeeded in building nmh on
> > > Cygwin myself.
> >
> > Ok, my mistake.  It *is* the nmh binaries.  I just noticed that the
> > message windows that pop up have titles like
> >
> > folder.exe
> > folders.exe
> > inc.exe
> > mark.exe
> > scan.exe
> >
> > However, the raw nmh commands run in the Cygwin bash shell with no
(Continue reading)

Igor Pechtchanski | 3 Jan 2003 23:00
Picon

Re: Win2000, XEmacs 21.4.10, MH-E, cygwin 1.3.17-1

On Fri, 3 Jan 2003, Peter Davis wrote:

> On Fri, Jan 03, 2003 at 03:34:20PM -0500, Igor Pechtchanski wrote:
> > On Fri, 3 Jan 2003, Peter Davis wrote:
> >
> > > On Fri, Jan 03, 2003 at 01:29:04PM -0500, Peter Davis wrote:
> > > > On Sat, Jan 04, 2003 at 02:14:04AM +0900, Stephen J. Turnbull wrote:
> > > > > >>>>> "Peter" == Peter Davis <pdavis <at> pageflexinc.com> writes:
> > > > >
> > > > >     >> The procedure entry point _ctype_ could not be located in the
> > > > >     >> dynamic link library cygwin1.dll
> > > > >
> > > > >     Peter> So why is XEmacs even *looking* in cygwin1.dll, since it's
> > > > >     Peter> the win32 installation?
> > > > >
> > > > > I doubt XEmacs is looking in cygwin1.dll.  Most likely it's the MH
> > > > > binaries.
> > > >
> > > > Hmmm.  That's even *more* puzzling, since I'm running the identical
> > > > binaries on both machines. I have not succeeded in building nmh on
> > > > Cygwin myself.
> > >
> > > Ok, my mistake.  It *is* the nmh binaries.  I just noticed that the
> > > message windows that pop up have titles like
> > >
> > > folder.exe
> > > folders.exe
> > > inc.exe
> > > mark.exe
> > > scan.exe
(Continue reading)

Peter Davis | 3 Jan 2003 23:30

Re: Win2000, XEmacs 21.4.10, MH-E, cygwin 1.3.17-1

Aha!  The Windows PATH.  All I had to do was add "c:\cygwin\bin" to
the front of the Windows path, and that fixed the problem.

Thanks to *ALL* who responded!  I really appreciate it.

Now I just have to work out the path problems, like why, after editing
an outgoing message, MH-E reports that it can't find

   /cygdrive/d/temp/d:/temp/draftsex/

For some reason the Cygwin path is getting pre-pended to the Windows
path.

Thanks all!!!

-pd

--

-- 
--------
                             Peter Davis
               Funny stuff at http://www.pfdstudio.com
                 The artwork formerly shown as prints
    List of resources for children's writers and illustrators at:
                  http://www.pfdstudio.com/cwrl.html


Gmane