Skip to content
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

Linking Issues with GCC in Bazel 0.27 #8656

Closed
henryqinshield opened this issue Jun 17, 2019 · 2 comments
Closed

Linking Issues with GCC in Bazel 0.27 #8656

henryqinshield opened this issue Jun 17, 2019 · 2 comments
Assignees
Labels
P3 We're not considering working on this, but happy to review a PR. (No assignee) team-Rules-CPP Issues for C++ rules type: support / not a bug (process)

Comments

@henryqinshield
Copy link

Description of the problem / feature request:

We have just upgraded to bazel 0.27. When we go to build, we are seeing a problem with build outputs in that they are not linking properly. We are using GCC to compile and link. We are also using our own custom crosstool as seen in the attached file.

When we set --incompatible_do_not_split_linking_cmdline=false, everything seems to link and run properly.

What operating system are you running Bazel on?

Ubuntu 16.04

Have you found anything relevant by searching the web?

When I looked at #7687 it seems to suggest that this only affects CROSSTOOLS with a param file. We don't use a param file but are still seeing these issues...

crosstool_config.bzl.txt

@scentini
Copy link
Contributor

cc/ @oquenchil

@irengrig irengrig added P1 I'll work on this now. (Assignee required) team-Rules-CPP Issues for C++ rules untriaged labels Jun 19, 2019
@hlopko hlopko assigned oquenchil and unassigned hlopko Jun 19, 2019
@hlopko hlopko added P2 We'll consider working on this in future. (Assignee optional) type: support / not a bug (process) P3 We're not considering working on this, but happy to review a PR. (No assignee) and removed P1 I'll work on this now. (Assignee required) P2 We'll consider working on this in future. (Assignee optional) labels Jun 19, 2019
@hlopko
Copy link
Member

hlopko commented Jun 19, 2019

You can run your build with --subcommands to see full gcc invocations and you can diff the command line before and after the --incompatible_do_not_split_linking_cmdline flip. That will help you isolate the problem. Maybe a simple reordering of features in your crosstool_config.bzl will be enough afterwards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 We're not considering working on this, but happy to review a PR. (No assignee) team-Rules-CPP Issues for C++ rules type: support / not a bug (process)
Projects
None yet
Development

No branches or pull requests

6 participants