indygreg / indygreg/PyOxidizer
Could not find src\libcore\result.rs:999:5 on windows 10
- Dominant language
- Rust
- Stars
- 6.2k
- Forks
- 256
- PR merge metrics
- No merged PRs in 30d
Description
Following the [https://pyoxidizer.readthedocs.io/en/latest/getting_started.html#your-first-pyoxidizer-project](url) example, the build fails with "src\libcore\result.rs:999:5" not being found. here is the output with backtrace enabled:
> processing packaging rule: Stdlib(PackagingStdlib { optimize_level: 0, exclude_test_modules: true, include_source: false, include_resources: false, install_location: Embedded })
> thread 'main' panicked at 'error reading source file: Os { code: 3, kind: NotFound, message: "The system cannot find the path specified." }', src\libcore\result.rs:999:5
> stack backtrace:
> 0: git_packbuilder_object_count
> 1: git_packbuilder_object_count
> 2: git_packbuilder_object_count
> 3: git_packbuilder_object_count
> 4: git_packbuilder_object_count
> 5: git_packbuilder_object_count
> 6: git_packbuilder_object_count
> 7:
> 8:
> 9:
> 10:
> 11:
> 12:
> 13:
> 14:
> 15:
> 16:
> 17: git_packbuilder_object_count
> 18: git_packbuilder_object_count
> 19: git_packbuilder_object_count
> 20:
> 21: git_libgit2_version
> 22: BaseThreadInitThunk
> 23: RtlUserThreadStart
I don't know what I'm looking at here, so I can't be more help than that.
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the getting-started example on Windows 10, using the reported Stdlib packaging rule and backtrace. Start by checking why the build tries to read src\libcore\result.rs:999:5; done means the example completes without the missing-path panic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100