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
Cross compile qnx, Bazel does not produce shared libraries. #15997
Comments
Hello @tongtongdi, Could you please provide complete steps to reproduce the above issue. Thanks! |
Hi @sgowroji , i cross compile qnx on x86_64 platform, my computer system is 20.04.1-Ubuntu, I follow the instruction at
my toolchain/BUILD is :
my .bazelrc file is :
you should set your qnx info in file cc_toolchain_config.bzl and .bazelrc. then i run |
when i enter /qnx710/host/linux/x86_64/usr/bin and create a ld soft connection |
Hi @sgowroji ,without creating a soft link, how can i fix this. Can I use a configuration to solve this problem ? |
@tongtongdi the missing ld error is not caused by Bazel but is coming from g++. Unfortunately, then another issue arises, which only happens under Bazel:
However, this can be solved by passing If you want to stick to calling gcc directly, then you still have to properly set ALL THREE env vars: |
Description of the bug:
When I cross compile QNX, no dynamic library is generated. At this time, after I add
feature( name = "supports_dynamic_linker", enabled = True, )
, it prompts me that ld cannot be found. then i create a ld soft connectionln aarch64-unknown-nto-qnx7.1.0-ld ld
, this problem is solved.i'm surprised that i specified ld in the tool_path like thistool_path( name = "ld", path = QNX_HOST + "/usr/bin/aarch64-unknown-nto-qnx7.1.0-ld",),
, but it doesn't seem to work,How can I solve this problem gracefully。Which operating system are you running Bazel on?
Linux.
What is the output of bazel info release?
5.2.0
Have you found anything relevant by searching the web?
When I cross compile the example , Bazel does not produce shared libraries
The text was updated successfully, but these errors were encountered: