[bug #65273] Potential bug in the info function?

2024-02-08 Thread Eli Zaretskii
Follow-up Comment #5, bug#65273 (group make): FWIW, I think it is very unfortunate that GNU Make started warning about this trick, especially if there is no reasonable way of getting the same effect by other means. ___ Reply to this item

[bug #65273] Potential bug in the info function?

2024-02-08 Thread Collin Funk
Follow-up Comment #4, bug#65273 (group make): [comment #3 comment #3:] > It's usually a good idea to check the NEWS file for things that might cause differences in behavior Thanks. I'll do that next time first. :) I grep'd for the error message and found it through git blame so it didn't take too

[bug #65276] SECONDEXPANSION doesn't work correctly with escaped spaces

2024-02-08 Thread Geza Herman
Follow-up Comment #2, bug#65276 (group make): Thanks! Yes, make doesn't support filenames with spaces. But (almost) everywhere, this shortcoming can be circumvented by escaping the space. And I've just checked, this problem is not just about spaces, but supposedly all escaped characters pose a pro

[bug #65276] SECONDEXPANSION doesn't work correctly with escaped spaces

2024-02-08 Thread Paul D. Smith
Follow-up Comment #1, bug#65276 (group make): I will take a look at this, but up-front I will say that GNU Make, like all POSIX make instances, does not intend to support pathnames containing spaces as either targets or prerequisites. It may be possible to get them to work in some limited situati

[bug #65276] SECONDEXPANSION doesn't work correctly with escaped spaces

2024-02-08 Thread anonymous
URL: Summary: SECONDEXPANSION doesn't work correctly with escaped spaces Group: make Submitter: None Submitted: Thu 08 Feb 2024 06:44:26 PM UTC Severity: 3 - Normal

[bug #65273] Potential bug in the info function?

2024-02-08 Thread Paul D. Smith
Update of bug#65273 (group make): Component Version: 4.4.1 => SCM ___ Follow-up Comment #3: It's usually a good idea to check the NEWS file for things that might cause differences in behavior; i

[bug #65273] Potential bug in the info function?

2024-02-08 Thread Collin Funk
Follow-up Comment #2, bug#65273 (group make): Finally got around to looking into this. From what I can tell it was an intentional change from commit 03ecd94488b85adc38746ec3e7c2a297a522598e. The previous commit doesn't warn and one referenced onward can be controlled with --warn=(ignore|warn|error