-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linker error on Ubuntu 16.04 with conda-forge libraries (-fno-plt
)
#117
Comments
Is this something that would have to be fixed in conda-forge's toolchain flags or somewhere else? |
AFAICT it's the |
binutils and other toolchain related packages are created by the ctng-compilers-feedstock. The various compiler and linker flags are set in ctng-compilers-activation-feedstock. |
A similar issue was found when using system compilers to build python extensions, conda/conda#6030. The solution was to use the system compilers but link with newer version of |
It seems like using the conda-forge |
On a Travis-CI Xenial VM, building Apache Arrow and linking it with some conda-forge libraries (here
libprotobuf.a
) produces a linker error at some point:(full log at https://travis-ci.org/pitrou/arrow/jobs/480342375#L1220)
This is related to the conda-forge toolchain migration (previously things would work fine on the even older Trusty VMs).
The error may be due to a new
GNU ld
feature that is not recognized by Xenial'sGNU ld
version. According to one of the binutils maintainers, not using-fno-plt
when building libraries would solve the issue:https://sourceware.org/ml/binutils/2019-01/msg00115.html
https://sourceware.org/ml/binutils/2019-01/msg00131.html
The text was updated successfully, but these errors were encountered: