Skip to content

Sorting xdebug problems#178

Closed
SirLouen wants to merge 2 commits intoWordPress:trunkfrom
SirLouen:patch/177
Closed

Sorting xdebug problems#178
SirLouen wants to merge 2 commits intoWordPress:trunkfrom
SirLouen:patch/177

Conversation

@SirLouen
Copy link
Copy Markdown
Member

Related to this issue: #177

The problem is that it seems that currently is outputting the directory twice and for this reason, xdebug is not being detected as available, hence not enabling it.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Aug 30, 2025

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: SirLouen <sirlouen@git.wordpress.org>
Co-authored-by: desrosj <desrosj@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@SirLouen
Copy link
Copy Markdown
Member Author

Before:

# ls /usr/local/lib/php/extensions/no-debug-non-zts-$(php -r 'echo PHP_EXTENSION_DIR;' | xargs basename)/xdebug.so
ls: cannot access '/usr/local/lib/php/extensions/no-debug-non-zts-no-debug-non-zts-20190902/xdebug.so': No such file or directory

After:

# ls /usr/local/lib/php/extensions/$(php -r 'echo PHP_EXTENSION_DIR;' | xargs basename)/xdebug.so
/usr/local/lib/php/extensions/no-debug-non-zts-20190902/xdebug.so

Copy link
Copy Markdown
Member

@desrosj desrosj left a comment

Choose a reason for hiding this comment

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

@SirLouen could you please run php update.php locally and include any changes to the built image files.

@SirLouen
Copy link
Copy Markdown
Member Author

@desrosj done 👌

@desrosj
Copy link
Copy Markdown
Member

desrosj commented Sep 2, 2025

@SirLouen I've gone and pushed the contents of your branch directly to this repository to get around #179.

Going to close this out and use #181 instead.

@desrosj desrosj closed this Sep 2, 2025
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.

2 participants