Literal ${wl} in build commands
Open
Nobody has claimed this yet.
Bug
Category: Build System
Status: Needs Triage
- Dominant language
- C
- Stars
- 40.4k
- Forks
- 8.1k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 96
Description
Description
When building a PHP extension using phpize (either a bundled extension or third-party extension) on macOS I see the literal string ${wl} in the build commands that are printed to the terminal, e.g.:
/usr/bin/clang ${wl}-undefined ${wl}dynamic_lookup -o .libs/soap.so -bundle .libs/soap.o .libs/php_encoding.o .libs/php_http.o .libs/php_packet_soap.o .libs/php_schema.o .libs/php_sdl.o .libs/php_xml.o -L/opt/local/lib -lxml2 -arch x86_64 -Wl,-headerpad_max_install_names -Wl,-syslibroot -Wl,/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64 -Wl,-rpath -Wl,/opt/local/lib
Shouldn't that ${wl} have been replaced with -Wl, somewhere beforehand?
PHP Version
8.2.1
Operating System
macOS 13.0.1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the build of a bundled or third-party PHP extension with phpize on macOS and inspect the printed build commands. Trace where the literal ${wl} is introduced and how linker flags are generated; done means the commands no longer print the unresolved placeholder.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100