[asterisk-bugs] [JIRA] (ASTERISK-28818) [patch] BuildSystem: Allow space in path.

[Asterisk Team (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-28818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Asterisk Team updated ASTERISK-28818:
-------------------------------------

    Target Release Version/s: 17.4.0

> [patch] BuildSystem: Allow space in path.
> -----------------------------------------
>
>                 Key: ASTERISK-28818
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28818
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/BuildSystem
>    Affects Versions: 13.32.0, 16.9.0, 17.3.0
>            Reporter: Alexander Traud
>            Assignee: Alexander Traud
>            Severity: Minor
>              Labels: patch
>      Target Release: 13.33.0, 16.10.0, 17.4.0
>
>         Attachments: build_path_space.patch
>
>
> When the user executes the script ./configure within a path which contains space(s), the sub-configure of project menuselect is not started automatically. The user sees this:{code}config.status: creating include/asterisk/autoconfig.h
> ./configure: line 36231: cd: too many arguments{code}The correct end of the script configure is:{code}config.status: creating autoconfig.h
> configure: Menuselect build configuration successfully completed{code}
> This issues [was introduced|https://github.com/asterisk/asterisk/commit/a00aa10f8cdfc1dab5bc4cca202755e88eee7035] in Oct. 2010, with Asterisk 10. A code review showed that the such a misuse of {{pwd}} [happened|https://github.com/asterisk/asterisk/commit/3be4c8d3eb4c2beb04ec3f0a557d9449147549fa] in Jul. 2006 with Asterisk 1.4, already. The attached patch fixes those three occurrences.



--
This message was sent by Atlassian JIRA
(v6.2#6252)