indygreg / indygreg/PyOxidizer
Duplicate symbols compiling libpyembed on the starter config
- Dominant language
- Rust
- Stars
- 6.2k
- Forks
- 256
- PR merge metrics
- No merged PRs in 30d
Description
From a new install of PyOxidizer, gcc v7.5 on a ubuntu host:
```
cargo install pyoxidizer
pyoxidizer init-config-file torch
cd torch
pyoxidizer run
```
Produces error messages like:
```
= note: ld: error: duplicate symbol: ffi_type_double
>>> defined at types.c
>>> types.o:(ffi_type_double) in archive /tmp/pyoxidizer.1OHhrEBicQgz/build/target/x86_64-unknown-linux-gnu/debug/deps/libpyembed-cd26feed010f04a2.rlib
>>> defined at cfield.c:1652 (./Modules/_ctypes/cfield.c:1652)
>>> cfield.o:(.data+0x750) in archive /tmp/pyoxidizer.1OHhrEBicQgz/build/target/x86_64-unknown-linux-gnu/debug/deps/libpyembed-cd26feed010f04a2.rlib
```
Full output: https://gist.github.com/c7ef834a12fb1205e9413bcca4d97d62
Please let me know if any additional info would be useful for debugging.
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the failure from a new PyOxidizer install with `cargo install pyoxidizer`, `pyoxidizer init-config-file torch`, and `pyoxidizer run` on Ubuntu. Start by tracing how the starter configuration builds and links `libpyembed`, using the duplicate-symbol output and linked full log; done means the starter configuration builds without duplicate-symbol linker errors.
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
- 25/100