Repository navigation
Conversation
Runs dumpbin on the currently installed gdal313.dll and _gdal.pyd right after OSGeo4W setup, to find which exported symbol is missing and causing "DLL load failed... The specified procedure could not be found" when importing osgeo.gdal, first seen in CI on 2026-09-25 after the gdal package moved from 3.13.3-1 to 3.13.3-2. Temporary, for CI investigation only. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
python3-gdal installs osgeo/_gdal.cp312-win_amd64.pyd (ABI-tagged), not _gdal.pyd, so the previous filter matched nothing. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Purpose
Companion to the gdal-3.13.3-1 pin test (see the sibling diagnostic PR).
The OSGeo4W CI job fails with
ImportError: DLL load failed while importing _gdal: The specified procedure could not be foundsince thegdalOSGeo4W package moved from3.13.3-1to3.13.3-2on2026-09-25 (jef-n/OSGeo4W@60c26bff backports OSGeo/gdal#15007, which
touches
gcore/gdaldllmain.cppand removes the exported symbolGDALIsInGlobalDestructorFromDLLMain).What this PR does
Adds one temporary step to
.github/workflows/osgeo4w.yml, right afterOSGeo4W setup (against the current, unmodified
3.13.3-2build), that:dumpbin.exeviavswhere(already on thewindows-2022runner).
gdal313.dll's exports filtered forGlobalDestructor._gdal.pyd's dependents and full import table.This should show directly whether
_gdal.pydis trying to import asymbol that no longer exists in the rebuilt
gdal313.dll, confirmingthe exact missing procedure behind the CI failure.
This PR is for CI investigation only and is not meant to be merged.
🤖 Generated with Claude Code