New: Most Make targets missing when path to man-pages has spaces

https://bugzilla.kernel.org/show_bug.cgi?id=219646

Bug ID: 219646
Summary: Most Make targets missing when path to man-pages has
spaces
Product: Documentation
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: man-pages
Assignee: [email protected]
Reporter: [email protected]
Regression: No

The path to my clone of the Linux man-pages repo contains a space. This causes Make to fail to find most targets.

Steps to Reproduce
==================

1. Create a directory who’s name contains spaces by running this command:

mkdir 'Name that contains spaces'

2. Change directory into that directory by running this command:

cd 'Name that contains spaces'

3. Clone the man-pages Git repo by running this command:

git clone https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git

4. Change directory into the repo by running this command:

cd man-pages

5. Get help by running this command:

make help

6. That previous command will have printed a new command that you can run to get a list of available Make targets. Run that command.

Actual Results
==============

This list is printed:

Expected Results
================

A list with over 100 Make targets is printed.

Additional Information
======================

I encountered this bug while using the tip of the man-pages’s master branch (b199d102db5be24e0ac88eb6879e3e3b6e0ea722 at the moment).

You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

Hi Jason,

POSIX says:

<https://pubs.opengroup.org/onlinepubs/9799919799/basedefs/V1_chap03.html#tag_03_265>

3.265 Portable Filename Character Set

The set of characters from which portable filenames are constructed.

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z a b c d e f g h i j k l m n o p q r s t u v w x y z 0 1 2 3 4 5 6 7 8 9 . _ -

The last three characters are the <period>, <underscore>, and <hyphen-minus> characters, respectively. See also 3.254 Pathname.

Your path is thus non-portable, and this is just one of its consequences. Software tends to not support such paths, especially paths containing whitespace, control characters, quotes, dollars, and other special characters.

115 at the moment. :)

	$ make nothing -p \
		| grep '^\.PHONY:' \
		| tr ' ' '\n' \
		| grep -v '^\.PHONY:' \
		| sort \
		| wc -l;
	115

I would close this as WONTFIX. Sorry. If the fix was easy, I might fix it, but I suspect there are so many break points that it's impossible to fix. Just don't do that. :)

Have a lovely new year!
Alex

<https://www.alejandro-colomar.es/>

https://bugzilla.kernel.org/show_bug.cgi?id=219646

--- Comment #1 from Alejandro Colomar ([email protected]) --- Hi Jason,

POSIX says:

<https://pubs.opengroup.org/onlinepubs/9799919799/basedefs/V1_chap03.html#tag_03_265>

3.265 Portable Filename Character Set

The set of characters from which portable filenames are constructed.

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z a b c d e f g h i j k l m n o p q r s t u v w x y z 0 1 2 3 4 5 6 7 8 9 . _ -

The last three characters are the <period>, <underscore>, and <hyphen-minus> characters, respectively. See also 3.254 Pathname.

Your path is thus non-portable, and this is just one of its consequences. Software tends to not support such paths, especially paths containing whitespace, control characters, quotes, dollars, and other special characters.

115 at the moment. :)

        $ make nothing -p \
                | grep '^\.PHONY:' \
                | tr ' ' '\n' \
                | grep -v '^\.PHONY:' \
                | sort \
                | wc -l;
        115

I would close this as WONTFIX. Sorry. If the fix was easy, I might fix it, but I suspect there are so many break points that it's impossible to fix. Just don't do that. :)

Have a lovely new year!
Alex

You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.