Skip to content

libtool: Allow spaces in program paths#3376

Open
zlaski wants to merge 2 commits intomsys2:masterfrom
zlaski:akisystems-msys
Open

libtool: Allow spaces in program paths#3376
zlaski wants to merge 2 commits intomsys2:masterfrom
zlaski:akisystems-msys

Conversation

@zlaski
Copy link
Copy Markdown

@zlaski zlaski commented Dec 7, 2022

This makes libtool more Windows-friendly. Sometimes, libtool will find tools like C:\Program Files (x86)\Git\bin\ld that it subsequently cannot handle.

@lazka
Copy link
Copy Markdown
Member

lazka commented Dec 9, 2022

thanks, we should take the opportunity and try to report this upstream at least.

case `"$_G_path_prog" --version 2>&1` in
- *GNU*) func_path_progs_result=$_G_path_prog _G_path_prog_found=: ;;
- *) $_G_check_func $_G_path_prog
+ *GNU*) func_path_progs_result="$_G_path_prog" _G_path_prog_found=: ;;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assignments like a=$b do not need any quotation, since bash does respect any white spaces when expanding the variable in assignments.

This reduces the patch to quoted arguments which is required, of course.

I am wondering how backslashes in a directory are avoided or treated. This additional issue should be dealt with if reported upstream I believe.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants