Re: Weird text-dependent bug in $(eval ...), simple test case

2010-02-28 Thread Philip Guenther 
On Sun, Feb 28, 2010 at 6:25 PM, Jamie Lokier  wrote:
> Both of you have confirmed the bug - because the correct behaviour has
> no error messages, and you both got messages.  Neither of you was able
> to reproduce getting a text-dependent number of messages, but both of
> you see buggy behaviour so it's easy to reproduce a problem to investigate.
>
> Nobody wants to investigate this bug further?

Not to make an insane suggestion, but have you considered filing a bug
in the GNU bug tracking system, Savannah?
http://savannah.gnu.org/projects/make/

As a side note, I don't understand why you call this a bug in
$(eval)...as it's completely reproducible without using $(eval)!  Did
you try testing it directly?  If not, why not?

We've seen this on the list now multiple times: it seems that if
someone first encounters a bug while working with $(eval), they report
the problem as being in $(eval) and make no attempt to reproduce it
directly.  Since this is a hinderance to getting good bug reports, it
would help if you could examine why this happened in this case so that
it might possible be avoided in the future with others.


Philip Guenther


___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make

Re: Weird text-dependent bug in $(eval ...), simple test case

2010-02-28 Thread Jamie Lokier 
Jamie Lokier wrote:
> Paul Smith wrote:
> > On Wed, 2010-02-10 at 13:04 -0800, Martin Dorey wrote:
> > > > (b) the messages are only produced for some words
> > > 
> > > That's not the case for me, with Debian Lenny's 3.81.
> > 
> > I agree: I'm running Ubuntu 9.10 64bit, with GNU make 3.81-6 installed
> > as well, and I don't see the OP's incorrect behavior.
> > 
> > I get messages produced for all the words, just like Martin.
> 
> Note that messages for all the words is also a bug.
> 
> There should be no error messages.

Both of you have confirmed the bug - because the correct behaviour has
no error messages, and you both got messages.  Neither of you was able
to reproduce getting a text-dependent number of messages, but both of
you see buggy behaviour so it's easy to reproduce a problem to investigate.

Nobody wants to investigate this bug further?

-- Jamie


___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make

Make manual update

2010-02-28 Thread Edward Welbourne 
Hi GNU make maintainers,

I began work on some additions and refinements to make.texi fourteen months ago 
but got
distracted.  The version I started from has
@set EDITION 0.70
@set RCSID $Id: make.texi,v 1.45 2006/04/01 06:36:40 psmith Exp $
What's the most recent edition; and where can I find an authoritative copy ?

I currently have my changes in a git repository, from which I can
extract patches as needed - but if submitting it in the form of (a link
to somewhere from which you can download) a tarred-up git repo is a
usable format for you, that would be easy to do - once I've re-based
onto a more up-to-date version.

Eddy.


___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make

[bug #29025] problem with odd directory names with spaces and/or parentheses

2010-02-28 Thread Ozkan Sezer 

Additional Item Attachment, bug #29025 (project make):

File name: SubDirSpaces.tar.gzSize:0 KB


___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/



___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make

[bug #29025] problem with odd directory names with spaces and/or parentheses

2010-02-28 Thread Ozkan Sezer 

URL:
  

 Summary: problem with odd directory names with spaces and/or
parentheses
 Project: make
Submitted by: sezero
Submitted on: Sun 28 Feb 2010 10:35:47 AM GMT
Severity: 3 - Normal
  Item Group: None
  Status: None
 Privacy: Public
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any
   Component Version: CVS
Operating System: Any
   Fixed Release: None
   Triage Status: None

___

Details:

I was notified of this bug by someone who was trying
to build cmake-2.8.0 for mingw-w64:
http://sourceforge.net/projects/mingw-w64/forums/forum/723798/topic/3551522
I reduced the testcase to this:

ls -R SubDirSpaces
SubDirSpaces:
err.txt  Makefile  Some(x86) Sources

SubDirSpaces/Some(x86) Sources:
CMakeFiles

SubDirSpaces/Some(x86) Sources/CMakeFiles:
testOddPath.dir

SubDirSpaces/Some(x86) Sources/CMakeFiles/testOddPath.dir:
build.make

$ cd SubDirSpaces && cat Makefile
all:
$(MAKE) -f "Some(x86) Sources\CMakeFiles\testOddPath.dir\build.make"
"Some(x86) Sources/CMakeFiles/testOddPath.dir/build"

$ cat Some\(x86\)\ Sources/CMakeFiles/testOddPath.dir/build.make
Some(x86)\ Sources/CMakeFiles/testOddPath.dir/build:
@echo Hey I am here!!!

With the CVS version of make (a binary for mingw-w64 is here
http://sourceforge.net/projects/mingw-w64/files/External%20binary%20packages%20%28Win64%20hosted%29/make/make_20100202_bin.zip/download
)
.. I get this error on windows:

C:\Users\ozzie\CODE\SubDirSpaces>make
make -f "Some(x86) Sources\CMakeFiles\testOddPath.dir\build.make" "Some(x86)
Sou
rces/CMakeFiles/testOddPath.dir/build"
make[1]: Entering directory `C:/Users/ozzie/CODE/SubDirSpaces'
make[1]: *** No rule to make target `Some(x86)
Sources/CMakeFiles/testOddPath.di
r/build'.  Stop.
make[1]: Leaving directory `C:/Users/ozzie/CODE/SubDirSpaces'
make: *** [all] Error 2

However, with an earlier version of make, specifically
make-3.81-20090914-mingw32 (patched further for mingw-w64:
http://sourceforge.net/projects/mingw-w64/files/External%20binary%20packages%20%28Win64%20hosted%29/make/make-3.81-20100227.zip/download
)
.. the process succeeds:

C:\Users\ozzie\CODE\SubDirSpaces>make
make -f "Some(x86) Sources\CMakeFiles\testOddPath.dir\build.make" "Some(x86)
Sou
rces/CMakeFiles/testOddPath.dir/build"
make[1]: Entering directory `C:/Users/ozzie/CODE/SubDirSpaces'
Hey I am here!!!
make[1]: Leaving directory `C:/Users/ozzie/CODE/SubDirSpaces'

The same error with the CVS version of make also happens
on linux if I replace the backslashes with forward slashes
in the relevant places in the makefiles. I was unable to
find when the breakage occured in the CVS.

Regards.





___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/



___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make