You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have any of you encountered a similar issue? First off, I’m in a network-disconnected user environment (without root privileges). After compiling and installing Python 3.10.2 from source in this user environment, I tried to use this Python version to cross-compile third-party libraries like coverage (because they contain .SO files). After specifying the cross-compilation toolchain, during the compilation phase, cross-compiled gcc was indeed used to compile .c files into .o files. However, during the linking phase, the default gcc was automatically used instead of the cross-compiled gcc, resulting in linking errors. Has anyone encountered this situation? Any solutions?
Compile status and error messages, along with attached images.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Have any of you encountered a similar issue? First off, I’m in a network-disconnected user environment (without root privileges). After compiling and installing Python 3.10.2 from source in this user environment, I tried to use this Python version to cross-compile third-party libraries like coverage (because they contain .SO files). After specifying the cross-compilation toolchain, during the compilation phase, cross-compiled gcc was indeed used to compile .c files into .o files. However, during the linking phase, the default gcc was automatically used instead of the cross-compiled gcc, resulting in linking errors. Has anyone encountered this situation? Any solutions?
Compile status and error messages, along with attached images.
Beta Was this translation helpful? Give feedback.
All reactions