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

undeclared inclusion(s) in rule '//lingvo/core/ops:ascii_tokenizer' #49

Closed
Raviteja1996 opened this issue Mar 19, 2019 · 9 comments
Closed
Labels
stat:awaiting response Awaiting response from user

Comments

@Raviteja1996
Copy link

Raviteja1996 commented Mar 19, 2019

When i try to run the command : bazel build -c opt //lingvo:trainer, I am facing the following error. If I am doing anything wrong, please correct me. I am running the above command in the home directory. I am continuing the issue #48. Before running the main command which you specified there, by observing the other readme I ran the above command.

ERROR:
Starting local Bazel server and connecting to it...
INFO: Analysed target //lingvo:trainer (35 packages loaded, 4188 targets configured).
INFO: Found 1 target...
ERROR: /home/guest/lingvo/lingvo/core/ops/BUILD:67:1: undeclared inclusion(s) in rule '//lingvo/core/ops:ascii_tokenizer':
this rule is missing dependency declarations for the following files included by 'lingvo/core/ops/ascii_tokenizer.cc':
'/usr/include/x86_64-linux-gnu/gnu/stubs-64.h'
Target //lingvo:trainer failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 6.231s, Critical Path: 1.86s
INFO: 0 processes.
FAILED: Build did NOT complete successfully

@jonathanasdf
Copy link
Contributor

Can you post your platform and compiler version?

@Raviteja1996
Copy link
Author

I am using Ubuntu 18.04 and my gcc compiler version is 7.3.0

@drpngx
Copy link
Contributor

drpngx commented Mar 20, 2019 via email

@Raviteja1996
Copy link
Author

My bazel version is 0.23.2

@jonathanasdf
Copy link
Contributor

I was unable to reproduce it with those setup

# bazel version
Build label: 0.23.2
Build target: bazel-out/k8-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Mon Mar 11 16:47:03 2019 (1552322823)
Build timestamp: 1552322823
Build timestamp as int: 1552322823

# gcc --version
gcc (Ubuntu 7.3.0-30ubuntu1~18.04.york0) 7.3.0

We think this is likely a bazel issue, so we probably cannot help you with debugging this. Right now the supported configuration is Ubuntu 16.04, gcc 4.8, and bazel 0.17.2.

@Raviteja1996
Copy link
Author

If I do it with lower version of bazel can it work?

@drpngx
Copy link
Contributor

drpngx commented Mar 29, 2019

No, it's might be the gcc version that isn't supported yet. Did you try with an older version?

@drpngx drpngx added the stat:awaiting response Awaiting response from user label Apr 8, 2019
@jonathanasdf
Copy link
Contributor

Have you figured this out?

@Raviteja1996
Copy link
Author

I actually went back and did from the starting with the versions specified above. So this problem was resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stat:awaiting response Awaiting response from user
Projects
None yet
Development

No branches or pull requests

3 participants