Gene Smith wrote:
<snip>
Going back to beta-1.7 default install that ran fast I noticed that it
was actually using a mingw32 version of "make" from winavr project and
not the cygwin "make". The default cygwin install does not include
make. When I load the cygwin make package and the build uses it (since
cygwin puts its paths ahead of windows path) the build slows way down.
If I remove make from cygwin's /bin it speeds back up (since using the
mingw32 make).
The build referred to above uses a toolchain built for mingw32, not
cygwin's gcc. So as long as make is also built for mingw32 the build
is fast when run from cygwin terminal or dos window. With make being
the cygwin version, the build is slow in all cases.
What does this mean? Am I doing something illegal mixing cygwin and
mingw programs?
Interesting. I'm not sure why using Cygwin's 'make' would slow things
down dramatically when running from a Cygwin terminal or shell. I can
see there being some overhead if that's the only Cygwin process you're
running, since there would be a Cygwin initialization cost to start 'make'
if there were no other Cygwin processes running at the time. I very much
doubt that this would account for the dramatic slow-down you've reported.
So while certainly there's an issue here, it seems like the work-around
you've found is viable. And it does make more sense than mixing and
matching Cygwin and Mingw.
Are you able to reproduce this problem for any kind of package? It
might be helpful to know that building package or tarball 'foo'
demonstrates
the problem.