gdb: fix expat search on some hosts #4222
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If /usr/lib/libexpat.so exists on host, it's picked instead of that from LE build system. From what I can tell, this issue was present before. However, in older configure logs only warning is issued but now error is returned.Give search path for expat explicitly. This solves issue on some hosts where expat is present in system. Previously expat was set on auto and gdb configure only printed a warning. But now that it's set to "yes" configure script fails if expat isn't found.