Re: MAKE and MinGW32 problems.

Re: MAKE and MinGW32 problems.

[Earnie Boyd]

--- Brendan Simon <brendan@dgs.monash.edu.au> wrote:
> "Lincoln, W. Terry" wrote:
> 
> > Did you set the MAKEMODE variable to DOS?
> >
> > AFAIK - make is using C:\bin\sh.exe as the shell because the variable is
> > set or defaults to UNIX.
> 
--8<--

I don't think this has anything to do with Brendan's problem.

--8<--
> Nope.  That didn't work either.
> It seems that all the GNU Makes that have been compiled for Mingw32 have some
> dependencies on the cygwin DLL.  I don't know why ?  Maybe it is actually
> just the cygwin make dressed up in a mingw32 archive ?
--8<--

If you're using the JanJaap's build of make then it is not cygwin dependent. 
If you want to be absolutely certain, use a binary editor and search for
cygwin.

--8<--
> Am I right in assuming that if GNU make was compiled with cygwin (or using a
> cross-compiler targeted for Mingw32) and the -mno-cygwin switch is supplied,
> then there should be absolutely no references to the cygwin DLL.
--8<--

This is mostly correct.  However I suppose one could force the use of the
cygwin dll even if the objects themselves are non-cygwin assuming that they
could get it properly initialized.

Brendan, did you try my suggestion of setting the SHELL variable in the
Makefile?  I.E.: SHELL = COMMAND.COM

You could also set the environment variable SHELL with a value of COMMAND.COM.
===
-                        \\||//
-------------------o0O0--Earnie--0O0o-------------------
--                earnie_boyd@yahoo.com               --
----------------------ooo0O--O0ooo----------------------

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: MAKE and MinGW32 problems.

[Brendan Simon]

The first thing I tried was to set the SHELL variable to c:/command.com.  For some
reason, Make would not let me overide this vairable (it was fixed at /bin/sh) so
I used MYSHELL and prefixed built in shell commands with this variable.


Earnie Boyd wrote:

> --- Brendan Simon <brendan@dgs.monash.edu.au> wrote:
>
>
> If you're using the JanJaap's build of make then it is not cygwin dependent.
> If you want to be absolutely certain, use a binary editor and search for
> cygwin.
>
> --8<--
> > Am I right in assuming that if GNU make was compiled with cygwin (or using a
> > cross-compiler targeted for Mingw32) and the -mno-cygwin switch is supplied,
> > then there should be absolutely no references to the cygwin DLL.
> --8<--
>
> This is mostly correct.  However I suppose one could force the use of the
> cygwin dll even if the objects themselves are non-cygwin assuming that they
> could get it properly initialized.
>
> Brendan, did you try my suggestion of setting the SHELL variable in the
> Makefile?  I.E.: SHELL = COMMAND.COM
>
> You could also set the environment variable SHELL with a value of COMMAND.COM.
> ===
> -                        \\||//
> -------------------o0O0--Earnie--0O0o-------------------
> --                earnie_boyd@yahoo.com               --
> ----------------------ooo0O--O0ooo----------------------
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: MAKE and MinGW32 problems.

[Jan-Jaap van der Heijden]

On Mon, 12 Apr 1999, Earnie Boyd wrote:

> > It seems that all the GNU Makes that have been compiled for Mingw32 have some
> > dependencies on the cygwin DLL.  I don't know why ?  Maybe it is actually
> > just the cygwin make dressed up in a mingw32 archive ?
> --8<--
> 
> If you're using the JanJaap's build of make then it is not cygwin dependent. 

I can confirm that 8-)

> If you want to be absolutely certain, use a binary editor and search for
> cygwin.

I think "objdump -p your.exe" is a more civilized way to do that.

I know "my" mingw32 make is based on somebody's work to build GNU make
with MSVC. I believe it creates .bat files under some circumstances and
that these don't always do what you might expect.

JanJaap

---
GNU mingw32: http://agnes.dida.physik.uni-essen.de/~janjaap/mingw32


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: MAKE and MinGW32 problems.

[DJ Delorie]

> I think "objdump -p your.exe" is a more civilized way to do that.

Or even "cygcheck your.exe" which does nothing but list dll
inter-dependencies (at least, without switches to cygcheck it does
that), including indirect dependencies.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: MAKE and MinGW32 problems.

[DJ Delorie]

> I think "objdump -p your.exe" is a more civilized way to do that.

Or even "cygcheck your.exe" which does nothing but list dll
inter-dependencies (at least, without switches to cygcheck it does
that), including indirect dependencies.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: MAKE and MinGW32 problems.

[Brendan Simon]

The first thing I tried was to set the SHELL variable to c:/command.com.  For some
reason, Make would not let me overide this vairable (it was fixed at /bin/sh) so
I used MYSHELL and prefixed built in shell commands with this variable.


Earnie Boyd wrote:

> --- Brendan Simon <brendan@dgs.monash.edu.au> wrote:
>
>
> If you're using the JanJaap's build of make then it is not cygwin dependent.
> If you want to be absolutely certain, use a binary editor and search for
> cygwin.
>
> --8<--
> > Am I right in assuming that if GNU make was compiled with cygwin (or using a
> > cross-compiler targeted for Mingw32) and the -mno-cygwin switch is supplied,
> > then there should be absolutely no references to the cygwin DLL.
> --8<--
>
> This is mostly correct.  However I suppose one could force the use of the
> cygwin dll even if the objects themselves are non-cygwin assuming that they
> could get it properly initialized.
>
> Brendan, did you try my suggestion of setting the SHELL variable in the
> Makefile?  I.E.: SHELL = COMMAND.COM
>
> You could also set the environment variable SHELL with a value of COMMAND.COM.
> ===
> -                        \\||//
> -------------------o0O0--Earnie--0O0o-------------------
> --                earnie_boyd@yahoo.com               --
> ----------------------ooo0O--O0ooo----------------------
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: MAKE and MinGW32 problems.

[Jan-Jaap van der Heijden]

On Mon, 12 Apr 1999, Earnie Boyd wrote:

> > It seems that all the GNU Makes that have been compiled for Mingw32 have some
> > dependencies on the cygwin DLL.  I don't know why ?  Maybe it is actually
> > just the cygwin make dressed up in a mingw32 archive ?
> --8<--
> 
> If you're using the JanJaap's build of make then it is not cygwin dependent. 

I can confirm that 8-)

> If you want to be absolutely certain, use a binary editor and search for
> cygwin.

I think "objdump -p your.exe" is a more civilized way to do that.

I know "my" mingw32 make is based on somebody's work to build GNU make
with MSVC. I believe it creates .bat files under some circumstances and
that these don't always do what you might expect.

JanJaap

---
GNU mingw32: http://agnes.dida.physik.uni-essen.de/~janjaap/mingw32


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: MAKE and MinGW32 problems.

[Earnie Boyd]

--- Brendan Simon <brendan@dgs.monash.edu.au> wrote:
> "Lincoln, W. Terry" wrote:
> 
> > Did you set the MAKEMODE variable to DOS?
> >
> > AFAIK - make is using C:\bin\sh.exe as the shell because the variable is
> > set or defaults to UNIX.
> 
--8<--

I don't think this has anything to do with Brendan's problem.

--8<--
> Nope.  That didn't work either.
> It seems that all the GNU Makes that have been compiled for Mingw32 have some
> dependencies on the cygwin DLL.  I don't know why ?  Maybe it is actually
> just the cygwin make dressed up in a mingw32 archive ?
--8<--

If you're using the JanJaap's build of make then it is not cygwin dependent. 
If you want to be absolutely certain, use a binary editor and search for
cygwin.

--8<--
> Am I right in assuming that if GNU make was compiled with cygwin (or using a
> cross-compiler targeted for Mingw32) and the -mno-cygwin switch is supplied,
> then there should be absolutely no references to the cygwin DLL.
--8<--

This is mostly correct.  However I suppose one could force the use of the
cygwin dll even if the objects themselves are non-cygwin assuming that they
could get it properly initialized.

Brendan, did you try my suggestion of setting the SHELL variable in the
Makefile?  I.E.: SHELL = COMMAND.COM

You could also set the environment variable SHELL with a value of COMMAND.COM.
===
-                        \\||//
-------------------o0O0--Earnie--0O0o-------------------
--                earnie_boyd@yahoo.com               --
----------------------ooo0O--O0ooo----------------------

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

MAKE and MinGW32 problems.

[Brendan Simon]

I had problems with MAKE compiled for the MinGW32 environment.  MAKE
wasn't exucuting SHELL commands such as "echo".  I solved this by
prefixing the command with "c:/command.com /c"

Now I have problems when trying to redirect output to files from within
make.

eg.
CFLAGS = -Wall -O2 -D_DEBUG_
MYSHELL = c:/command.com /c
ECHO = $(MYSHELL) echo

default :
    $(ECHO) $(CFLAGS) > cflags.txt


I get an error saying cygwin.dll could not be found.
process_begin: CreateProcess(C:\BIN\sh.exe, C:/BIN/sh.exe -c
"c:/command.com /c echo -Wall -O2 -D_DEBUG_ > cflags.txt", ...) failed.
make (e=1157): One of the library files needed to run this application
cannot be found.


I don't understand why any program compiled with/for MinGW32 should be
looking for cygwin.dll.
I'm pretty sure I have redirected output to files with an older version
of make (but I think that was compiled with DJGPP).  I might have to dig
that out or see if DJ has an updated one on his web site.  I'd prefer to
use a MinGW32 version though as I'm not sure what the future of DJGPP is
(and I'd rather keep to one distribution).

PS. I am using Win98, GNU MAKE 3.77 (from Mumit's site).

Thanks,
Brendan Simon.



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: MAKE and MinGW32 problems.

[Brendan Simon]

"Lincoln, W. Terry" wrote:

> Did you set the MAKEMODE variable to DOS?
>
> AFAIK - make is using C:\bin\sh.exe as the shell because the variable is
> set or defaults to UNIX.

Nope.  That didn't work either.
It seems that all the GNU Makes that have been compiled for Mingw32 have some
dependencies on the cygwin DLL.  I don't know why ?  Maybe it is actually
just the cygwin make dressed up in a mingw32 archive ?

Am I right in assuming that if GNU make was compiled with cygwin (or using a
cross-compiler targeted for Mingw32) and the -mno-cygwin switch is supplied,
then there should be absolutely no references to the cygwin DLL.

Brendan Simon.


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: MAKE and MinGW32 problems.

[Lincoln, W. Terry]

[-- Attachment #1: Type: text/plain, Size: 111 bytes --]

WINMAIL.DAT
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


[-- Attachment #2: WINMAIL.DAT --]
[-- Type: application/vnd.ms-tnef, Size: 3310 bytes --]

Re: MAKE and MinGW32 problems.

[Mumit Khan]

On Fri, 9 Apr 1999, Brendan Simon wrote:

> 
> I had problems with MAKE compiled for the MinGW32 environment.  MAKE
> wasn't exucuting SHELL commands such as "echo".  I solved this by
> prefixing the command with "c:/command.com /c"
> 
> Now I have problems when trying to redirect output to files from within
> make.
> 
> eg.
> CFLAGS = -Wall -O2 -D_DEBUG_
> MYSHELL = c:/command.com /c
> ECHO = $(MYSHELL) echo
> 
> default :
>     $(ECHO) $(CFLAGS) > cflags.txt
> 
> 
> I get an error saying cygwin.dll could not be found.
> process_begin: CreateProcess(C:\BIN\sh.exe, C:/BIN/sh.exe -c
> "c:/command.com /c echo -Wall -O2 -D_DEBUG_ > cflags.txt", ...) failed.
> make (e=1157): One of the library files needed to run this application
> cannot be found.

Make will try to find a /bin/sh, and use it if found in your PATH.

> 
> I don't understand why any program compiled with/for MinGW32 should be
> looking for cygwin.dll.
> I'm pretty sure I have redirected output to files with an older version
> of make (but I think that was compiled with DJGPP).  I might have to dig
> that out or see if DJ has an updated one on his web site.  I'd prefer to
> use a MinGW32 version though as I'm not sure what the future of DJGPP is
> (and I'd rather keep to one distribution).
> 
> PS. I am using Win98, GNU MAKE 3.77 (from Mumit's site).
> 

I didn't even know I had a make on my site. Just for kicks, could you try
out any mingw make, from say Jan-Jaaps (URL below) site, and see if it
still causes the problem? Also, you may want to remove /bin from your
PATH and see if that does anything.

     http://agnes.dida.physik.uni-essen.de/~janjaap/mingw32/index.html

fyi, I'm now more in favor of using Cygwin tools to build both Cygwin
and Mingw binaries/executables (using -mno-cygwin) to avoid these 
hassles. With b20.1 being quite stable on NT, and reasonably stable
on W9x using the 1999-01-16 snapshot on Cygnus site, it's looking
better and better.

My personal preference is to use a Linux box and cross-compile ...

Regards,
Mumit




--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: MAKE and MinGW32 problems.

[Brendan Simon]

Mumit Khan wrote:

> Make will try to find a /bin/sh, and use it if found in your PATH.

I have C:\BIN in my path but there is no sh or sh.exe

> I didn't even know I had a make on my site. Just for kicks, could you try
> out any mingw make, from say Jan-Jaaps (URL below) site, and see if it
> still causes the problem? Also, you may want to remove /bin from your
> PATH and see if that does anything.

ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/mingw32/ports/


> fyi, I'm now more in favor of using Cygwin tools to build both Cygwin
> and Mingw binaries/executables (using -mno-cygwin) to avoid these
> hassles. With b20.1 being quite stable on NT, and reasonably stable
> on W9x using the 1999-01-16 snapshot on Cygnus site, it's looking
> better and better.
>
> My personal preference is to use a Linux box and cross-compile ...

I too prefer Linux and GNU tools.  Most of my colleagues do not use UNIX (or
never have) and we are using cross-compilers & debuggers for embedded systems
that are hosted on MS-Windows platforms (ie. -mno-cygwin wont solve my
problems as we are not building MS-Windows executables).  I just wanted to
get an up to date version of Make (we were using an old MKS version for 16
bit DOS).  I don't really want to get the my co-workers to install Cygwin
just to get Make working.  I do think that the Cygwin environment is very
good.  It gives developers the power of the UNIX environment (well closer to
it).  I am introducing so many new things to them that come from the
UNIX/Linux/GNU world that I will only confuse them further.  In the long term
I think introducing Cygwin in our development environment will be a good
thing (introducing Linux would be even better).  I only hope that
Cygwincontinues to improve in the speed department as that is the main reason
I prefer using Mingw built tools.

Thanks,
Brendan Simon.



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: MAKE and MinGW32 problems.

[Brendan Simon]

"Lincoln, W. Terry" wrote:

> Did you set the MAKEMODE variable to DOS?
>
> AFAIK - make is using C:\bin\sh.exe as the shell because the variable is
> set or defaults to UNIX.

Nope.  That didn't work either.
It seems that all the GNU Makes that have been compiled for Mingw32 have some
dependencies on the cygwin DLL.  I don't know why ?  Maybe it is actually
just the cygwin make dressed up in a mingw32 archive ?

Am I right in assuming that if GNU make was compiled with cygwin (or using a
cross-compiler targeted for Mingw32) and the -mno-cygwin switch is supplied,
then there should be absolutely no references to the cygwin DLL.

Brendan Simon.


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: MAKE and MinGW32 problems.

[Brendan Simon]

Mumit Khan wrote:

> Make will try to find a /bin/sh, and use it if found in your PATH.

I have C:\BIN in my path but there is no sh or sh.exe

> I didn't even know I had a make on my site. Just for kicks, could you try
> out any mingw make, from say Jan-Jaaps (URL below) site, and see if it
> still causes the problem? Also, you may want to remove /bin from your
> PATH and see if that does anything.

ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/mingw32/ports/


> fyi, I'm now more in favor of using Cygwin tools to build both Cygwin
> and Mingw binaries/executables (using -mno-cygwin) to avoid these
> hassles. With b20.1 being quite stable on NT, and reasonably stable
> on W9x using the 1999-01-16 snapshot on Cygnus site, it's looking
> better and better.
>
> My personal preference is to use a Linux box and cross-compile ...

I too prefer Linux and GNU tools.  Most of my colleagues do not use UNIX (or
never have) and we are using cross-compilers & debuggers for embedded systems
that are hosted on MS-Windows platforms (ie. -mno-cygwin wont solve my
problems as we are not building MS-Windows executables).  I just wanted to
get an up to date version of Make (we were using an old MKS version for 16
bit DOS).  I don't really want to get the my co-workers to install Cygwin
just to get Make working.  I do think that the Cygwin environment is very
good.  It gives developers the power of the UNIX environment (well closer to
it).  I am introducing so many new things to them that come from the
UNIX/Linux/GNU world that I will only confuse them further.  In the long term
I think introducing Cygwin in our development environment will be a good
thing (introducing Linux would be even better).  I only hope that
Cygwincontinues to improve in the speed department as that is the main reason
I prefer using Mingw built tools.

Thanks,
Brendan Simon.



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: MAKE and MinGW32 problems.

[Lincoln, W. Terry]

WINMAIL.DAT
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: MAKE and MinGW32 problems.

[Mumit Khan]

On Fri, 9 Apr 1999, Brendan Simon wrote:

> 
> I had problems with MAKE compiled for the MinGW32 environment.  MAKE
> wasn't exucuting SHELL commands such as "echo".  I solved this by
> prefixing the command with "c:/command.com /c"
> 
> Now I have problems when trying to redirect output to files from within
> make.
> 
> eg.
> CFLAGS = -Wall -O2 -D_DEBUG_
> MYSHELL = c:/command.com /c
> ECHO = $(MYSHELL) echo
> 
> default :
>     $(ECHO) $(CFLAGS) > cflags.txt
> 
> 
> I get an error saying cygwin.dll could not be found.
> process_begin: CreateProcess(C:\BIN\sh.exe, C:/BIN/sh.exe -c
> "c:/command.com /c echo -Wall -O2 -D_DEBUG_ > cflags.txt", ...) failed.
> make (e=1157): One of the library files needed to run this application
> cannot be found.

Make will try to find a /bin/sh, and use it if found in your PATH.

> 
> I don't understand why any program compiled with/for MinGW32 should be
> looking for cygwin.dll.
> I'm pretty sure I have redirected output to files with an older version
> of make (but I think that was compiled with DJGPP).  I might have to dig
> that out or see if DJ has an updated one on his web site.  I'd prefer to
> use a MinGW32 version though as I'm not sure what the future of DJGPP is
> (and I'd rather keep to one distribution).
> 
> PS. I am using Win98, GNU MAKE 3.77 (from Mumit's site).
> 

I didn't even know I had a make on my site. Just for kicks, could you try
out any mingw make, from say Jan-Jaaps (URL below) site, and see if it
still causes the problem? Also, you may want to remove /bin from your
PATH and see if that does anything.

     http://agnes.dida.physik.uni-essen.de/~janjaap/mingw32/index.html

fyi, I'm now more in favor of using Cygwin tools to build both Cygwin
and Mingw binaries/executables (using -mno-cygwin) to avoid these 
hassles. With b20.1 being quite stable on NT, and reasonably stable
on W9x using the 1999-01-16 snapshot on Cygnus site, it's looking
better and better.

My personal preference is to use a Linux box and cross-compile ...

Regards,
Mumit




--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

MAKE and MinGW32 problems.

[Brendan Simon]

I had problems with MAKE compiled for the MinGW32 environment.  MAKE
wasn't exucuting SHELL commands such as "echo".  I solved this by
prefixing the command with "c:/command.com /c"

Now I have problems when trying to redirect output to files from within
make.

eg.
CFLAGS = -Wall -O2 -D_DEBUG_
MYSHELL = c:/command.com /c
ECHO = $(MYSHELL) echo

default :
    $(ECHO) $(CFLAGS) > cflags.txt


I get an error saying cygwin.dll could not be found.
process_begin: CreateProcess(C:\BIN\sh.exe, C:/BIN/sh.exe -c
"c:/command.com /c echo -Wall -O2 -D_DEBUG_ > cflags.txt", ...) failed.
make (e=1157): One of the library files needed to run this application
cannot be found.


I don't understand why any program compiled with/for MinGW32 should be
looking for cygwin.dll.
I'm pretty sure I have redirected output to files with an older version
of make (but I think that was compiled with DJGPP).  I might have to dig
that out or see if DJ has an updated one on his web site.  I'd prefer to
use a MinGW32 version though as I'm not sure what the future of DJGPP is
(and I'd rather keep to one distribution).

PS. I am using Win98, GNU MAKE 3.77 (from Mumit's site).

Thanks,
Brendan Simon.



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com