This is the mail archive of the
mailing list for the Cygwin project.
Re: make - rm bug
- From: Eric Blake <ebb9 at byu dot net>
- To: Hedley Lester <hedley dot lester at ntlworld dot com>, cygwin at cygwin dot com
- Date: Tue, 09 May 2006 07:09:32 -0600
- Subject: Re: make - rm bug
- References: <038601c67296$ed8f9a30$0401a8c0@hedley2> <446003DA.email@example.com> <007f01c67366$b21ea8d0$0401a8c0@hedley2>
- Reply-to: cygwin at cygwin dot com
-----BEGIN PGP SIGNED MESSAGE-----
Forwarding to the cygwin list (this thread started on bug-gnu-utils).
http://cygwin.com/acronyms/#PPIOSPE - by posting, your feedback reaches a
Also, http://cygwin.com/acronyms/#TOFU reformatted.
According to Hedley Lester on 5/9/2006 6:47 AM:
> According to Hedley Lester on 5/8/2006 5:59 AM:
>>>> There appears to be a bug in the interaction between make and rm, so
>>>> that it does not expand *.o when it is inside the makefile. It works
>>>> fine on the command line.
>>>> Running under Windows XP
>>>>> rm --version
>>>> rm (GNU fileutils) 3.16
>>>>> make --version
>>>> GNU Make version 3.75, by Richard Stallman and Roland McGrath.
>>>> I don't know if this bug is still extant in later versions
> Those are some very old versions. Consider using cygwin, which has
> already packaged coreutils 5.94 (the replacement to fileutils), and make
> 3.80, for use on windows. See cygwin.com for details.
> Hi Eric,
> I spent some time today struggling with the cygwin setup utility to make
> it give me just the files I needed - I did not find it very friendly to
> the task.
What feedback can you give that makes setup.exe easier to use? I
personally don't have too much difficulty with it, as long as you remember
that not all packages come by default -
> Eventually I managed to find and download the libraries I needed in
> order to run just the new make. I substituted the new make and it's
> libraries into the folder I had sent you yesterday.
> I was just about to write to you saying that it made no difference at
> all, when I realised that I had not downloaded the new rm.exe.
rm is part of coreutils, which is default, so you shouldn't have had to
download it separately - setup.exe should have done it for you. I suspect
that your cygwin installation may be rather strange from how you described
grabbing raw executables, and without using the proper tool for installing
it, you can expect to have problems.
> Sure enough, when I substituted the new rm.exe as well as the make.exe
> and its requisite libraries everything worked perfectly!
> Unable to resist the urge to experiment, I then substituted the old
> make.exe back into the mix - fully expecting that it would still work
> (and that it was all rm's fault) . . . and lo and behold it reproduced
> the same incorrect behaviour as before.
Here, not necessarily due to old versions. Your older versions probably
weren't part of cygwin; mixing a non-cygwin make with a cygwin rm, or
vice-versa, is not always going to work.
> So, it sounds like the words I wrote yesterday were more accurate than I
> expected,"a bug in the interaction between make and rm" - all fixed in
> the new versions.
> Thanks for the advice - it's all working nicely now.
Life is short - so eat dessert first!
Eric Blake firstname.lastname@example.org
volunteer cygwin coreutils maintainer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v126.96.36.199 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html