Re: [bug #712] GNU make can't handle spaces in pathnames

> I have always wondered why we did not pick another > character than ascii 32 to represent space in file names. That would involve the disk driver - or all software that creates files - mapping the space the user typed to the chosen codepoint. There are then a whole load of other places software

Re: [bug #712] GNU make can't handle spaces in pathnames

I have always wondered why we did not pick another character than ascii 32 to represent space in file names. There are a lot of codepoints in unicode that could be used. //Fredrik 2013/2/28 Eli Zaretskii : >> Date: Thu, 28 Feb 2013 10:32:32 +0100 >> From: Reinier Post >> >> I don't think make ca

Re: [bug #712] GNU make can't handle spaces in pathnames

> Date: Thu, 28 Feb 2013 10:32:32 +0100 > From: Reinier Post > > I don't think make can be expected to handle spaces in filenames > because by design it relies on many other tools and scripts that > cannot handle them or handle them in very idiosyncratic ways. > You're in for a lot of trouble reg

[bug #38442] Field 'name' not cached

Follow-up Comment #1, bug #38442 (project make): I want to add that the Make 3.81 doesn't have this warning. ___ Reply to this item at: ___ Message sent

[bug #38442] Field 'name' not cached

URL: Summary: Field 'name' not cached Project: make Submitted by: karaheart Submitted on: Thu 28 Feb 2013 01:46:55 PM GMT Severity: 3 - Normal Item Group: Bug

Re: [bug #38437] cannot find the include file

Thanks Philip. It works for me, and now I can distribute my makefiles into different path. However, I still hope it can be improved as the expreience of C/C++ tells us it shall be able to. When reading a makefile, the path of this file should be added into the search path automaticallly. 2013/2/

Re: [bug #712] GNU make can't handle spaces in pathnames

> I don't think make can be expected to handle spaces in filenames > because by design it relies on many other tools and scripts that > cannot handle them or handle them in very idiosyncratic ways. > You're in for a lot of trouble regardless of what make itself supports. > Most Unix scripters know

Re: [bug #38433] Example for "eval" in documentation contains error with "define"

On Wed Feb 27 17:02:03 2013, guent...@gmail.com (Philip Guenther) wrote: > IMO, the suggestion that was proposed would reduce the overall > usability of the manual and increase the confusion. I seen it tried > in multiple ways** in other open source projects (and at my day job) > and the results

Re: [bug #38433] Example for "eval" in documentation contains error with "define"

On Wed Feb 27 14:07:42 2013, guent...@gmail.com (Philip Guenther) wrote: > Meanwhile, other people complain that the docs are too long; adding > "this feature was added in 3.8x" throughout the guide just makes it > longer and harder to read. It's not a costless addition. I completely disagree. L

Re: [bug #712] GNU make can't handle spaces in pathnames

On Wed Feb 27 04:55:13 2013, invalid.nore...@gnu.org (Jian) wrote: > Follow-up Comment #12, bug #712 (project make): > > What's a pity the bug/limitation has lasted more than 10 years! I'd like to > share my workaround here. Thanks ... I don't think make can be expected to handle spaces in filen

[bug #38437] cannot find the include file

Follow-up Comment #2, bug #38437 (project make): (just paste the mail with solution here for your reference) Thanks Philip. It works for me, and now I can distribute my makefiles into different path. However, I still hope it can be improved as the expreience of C/C++ tells us it shall be able to