Unable to run apps that use navigation on x86_64

I have version 2019.1-17919 of the SDK. It looks as though I’m missing the shared object files needed for navigation. If I try to run //apps/kaya:gmapping_distributed_host, I’ll get this error:

2019-04-29 22:06:07.315 INFO    engine/gems/scheduler/scheduler.cpp@280: Scheduler execution groups are:
2019-04-29 22:06:07.315 INFO    engine/gems/scheduler/scheduler.cpp@289: __BlockerGroup__: Cores = [6, 7], Workers = No
2019-04-29 22:06:07.315 INFO    engine/gems/scheduler/scheduler.cpp@289: __WorkerGroup__: Cores = [0, 1, 2, 3, 4, 5], Workers = Yes
2019-04-29 22:06:07.315 ERROR   engine/alice/backend/modules.cpp@241: navigation: packages/navigation/libnavigation_module.so: cannot open shared object file: No such file or directory
2019-04-29 22:06:07.315 PANIC   engine/alice/backend/modules.cpp@243: Could not load all required modules for application

Similarly, for bazel run //apps/flatsim I get this:

heathkit@nuc:~/isaac$ bazel run --config x86_64 //apps/flatsim
INFO: Analysed target //apps/flatsim:flatsim (66 packages loaded, 2891 targets configured).
INFO: Found 1 target...
Target //apps/flatsim:flatsim up-to-date:
  bazel-bin/apps/flatsim/flatsim
INFO: Elapsed time: 208.018s, Critical Path: 32.10s, Remote (0.00% of the time): [queue: 0.00%, setup: 0.00%, process: 0.00%]
INFO: 929 processes: 900 linux-sandbox, 29 local.
INFO: Build completed successfully, 1425 total actions
INFO: Build completed successfully, 1425 total actions
2019-04-29 22:16:32.564 WARNING engine/alice/backend/backend.cpp@141: This application does not have an explicit scheduler configuration. One will be autogenerated to the best of the systems abilities if possible.
2019-04-29 22:16:32.564 WARNING engine/gems/scheduler/scheduler.cpp@327: No default execution groups specified. Attempting to create scheduler configuration for 8 remaining cores. This may be non optimal for the system and application.
2019-04-29 22:16:32.564 INFO    engine/gems/scheduler/scheduler.cpp@280: Scheduler execution groups are:
2019-04-29 22:16:32.564 INFO    engine/gems/scheduler/scheduler.cpp@289: __BlockerGroup__: Cores = [6, 7], Workers = No
2019-04-29 22:16:32.564 INFO    engine/gems/scheduler/scheduler.cpp@289: __WorkerGroup__: Cores = [0, 1, 2, 3, 4, 5], Workers = Yes
2019-04-29 22:16:32.565 ERROR   engine/alice/backend/modules.cpp@241: flatsim: packages/flatsim/libflatsim_module.so: cannot open shared object file: No such file or directory
2019-04-29 22:16:32.565 ERROR   engine/alice/backend/modules.cpp@241: map: packages/map/libmap_module.so: cannot open shared object file: No such file or directory
2019-04-29 22:16:32.565 ERROR   engine/alice/backend/modules.cpp@241: navigation: packages/navigation/libnavigation_module.so: cannot open shared object file: No such file or directory
2019-04-29 22:16:32.565 ERROR   engine/alice/backend/modules.cpp@241: planner: packages/planner/libplanner_module.so: cannot open shared object file: No such file or directory
2019-04-29 22:16:32.565 PANIC   engine/alice/backend/modules.cpp@243: Could not load all required modules for application

However, I can build these packages if I set --config jetpack42. I’m admittedly a little confused here - I definitely do have the shared objects in packages_x86_64, and I’m definitely using an x86_64 config, but for some reason bazel isn’t finding the shared object files.

Hi heathkit,

Can you please list your host configuration?