indygreg/PyOxidizer

Duplicate symbols compiling libpyembed on the starter config

Open

#278 opened on Aug 14, 2020

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Rust (4,488 stars) (194 forks)batch import
bughelp wanted

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

Tech stack
rustpythonc
Domain
tooling
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
needs maintainer response
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Rust toolchainPython embeddingC compilation basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the duplicate symbol error involving ffi type double. Examine the Rust build configuration in the pyembed crate, especially the linking with Python's libffi library. Review the full error output in the provided gist. Consider if the issue is due to a version mismatch or static linking conflict.